Vulnerability record · CVE-2022-0540 · published 20 April 2022
CVE-2022-0540: Atlassian Jira Seraph authentication bypass via crafted HTTP request
Atlassian · Jira Data Center
Jira Server, Data Center and Jira Service Management contain an authentication bypass in the Seraph component, reachable by sending a specially crafted HTTP request. Because the flaw defeats authentication entirely and the affected products are widely deployed, it exposes both confidentiality and integrity of the instance.
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Automated analysis
critical priorityCVSS 9.8 with network reachability, no authentication or user interaction, and very high EPSS make this an urgent patch target despite no KEV listing.
What it is
Jira Server, Data Center and Jira Service Management contain an authentication bypass in the Seraph component, reachable by sending a specially crafted HTTP request. Because the flaw defeats authentication entirely and the affected products are widely deployed, it exposes both confidentiality and integrity of the instance.
Impact
An unauthenticated attacker can bypass authentication and act with the privileges the bypass grants, gaining access to data and functionality that should require login.
Attack surface
Reachable over the network via HTTP with no authentication and no user interaction, per the CVSS vector AV:N/AC:L/PR:N/UI:N. Any internet- or network-exposed Jira instance in the affected version ranges is a candidate target.
Exploitation
Not listed in CISA KEV and no ransomware association is recorded, but EPSS is very high (0.88057, 99.757th percentile), indicating strong likelihood of attempted exploitation. All references are vendor advisories and patch links, with no public exploit tag supplied.
What to do
- Upgrade Jira Server/Data Center to 8.13.18, 8.20.6 or 8.22.0 and later, and Jira Service Management Server/Data Center to 4.13.18, 4.20.6 or 4.22.0 and later, per the Atlassian advisory.
- If immediate patching is not possible, restrict network access to Jira instances to trusted networks and place them behind authentication-aware proxies.
- Review Jira access logs for anomalous unauthenticated requests and unexpected administrative or data-access activity.
- Confirm no unauthorized accounts, permission changes or configuration modifications were made during any exposure window.
Detection
- Hunt web/proxy logs for crafted or malformed HTTP requests to Jira endpoints that return success without a valid session.
- Alert on authenticated-looking activity from sessions with no preceding login event.
- Monitor for unexpected administrative actions, permission grants or bulk data access in Jira audit logs.
- Baseline normal Jira request patterns and flag deviations from unauthenticated source IPs.
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Affected products
3 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| https://confluence.atlassian.com/display/JIRA/Jira+Security+Advisory+2022-04-20 | Issue TrackingPatchVendor Advisory |
| https://jira.atlassian.com/browse/JRASERVER-73650 | Issue TrackingPatchVendor Advisory |
| https://jira.atlassian.com/browse/JSDSERVER-11224 | Issue TrackingPatchVendor Advisory |
| https://confluence.atlassian.com/display/JIRA/Jira+Security+Advisory+2022-04-20 | Issue TrackingPatchVendor Advisory |
| https://jira.atlassian.com/browse/JRASERVER-73650 | Issue TrackingPatchVendor Advisory |
| https://jira.atlassian.com/browse/JSDSERVER-11224 | Issue TrackingPatchVendor Advisory |
Track CVE-2022-0540 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2022-0540), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.