Cyber Resilience

CVE-2022-0540

Auth Bypass in Atlassian Jira Service Management ≤ 4.13.8

High EPSSAuth Bypass
Published
20 April 2022
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.88 99.8th percentile
Risk Priority 97 floored blend · peak EPSS

Summary

CVE-2022-0540 is a critical-severity Improper Authentication (CWE-287) vulnerability in Atlassian Jira Service Management. Its CVSS base score is 9.8 (Critical).

Operationally, ranked in the top 0.2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

A vulnerability in the Jira Seraph authentication component permits remote attackers to bypass login checks by submitting a crafted HTTP request. The flaw affects Atlassian Jira Server and Data Center releases prior to 8.13.18, from 8.14.0 through 8.20.5, and from 8.21.0 through 8.21.x, as well as Jira Service Management Server and Data Center releases prior to 4.13.18, from 4.14.0 through 4.20.5, and from 4.21.0 through 4.21.x. The issue carries a CVSS 3.1 base score of 9.8 and is tracked under CWE-287.

An unauthenticated attacker with network access can exploit the flaw to obtain full administrative control of the affected Jira instance, including the ability to read, modify, or delete any data and to execute arbitrary actions within the application. No user interaction or credentials are required, and the attack can be performed over the network with low complexity.

Atlassian’s security advisory and the linked Jira tickets JRASERVER-73650 and JSDSERVER-11224 direct administrators to upgrade to the fixed releases listed in the advisory (8.13.18, 8.20.6, 8.22.0 or later for Jira; 4.13.18, 4.20.6, 4.22.0 or later for Jira Service Management). The EPSS score remains elevated near its recorded peak of 0.9278.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

Likely ATT&CK TechniquesAI

Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.

T1190 Exploit Public-Facing Application Initial Accessconfidence: HIGH
The vulnerability allows unauthenticated remote attackers to bypass authentication on a public-facing Jira application, directly enabling exploitation of a public-facing web application.
T1078 Valid Accounts Stealthconfidence: HIGH
Successful exploitation grants full administrative control, effectively providing valid high-privileged accounts without credentials.
T1133 External Remote Services Persistenceconfidence: MEDIUM
The flaw permits remote attackers to access the Jira instance via its exposed web interface without authentication, consistent with external remote services abuse.
inferred from description + CWE · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2023-22501Same product: Atlassian Jira Service Management
CVE-2021-26086Same product: Atlassian Jira Data Center
CVE-2024-21685Same product: Atlassian Jira Data Center
CVE-2025-22157Same product: Atlassian Jira Data Center
CVE-2025-22167Same product: Atlassian Jira Data Center
CVE-2024-21683Same product: Atlassian Jira Data Center
CVE-2019-11581Same product: Atlassian Jira Server
CVE-2024-21697Same vendor: Atlassian
CVE-2025-35113Same vendor: Atlassian
CVE-2023-22505Same vendor: Atlassian

Affected Assets

atlassian
jira data center
≤ 8.13.8 · 8.14.0 — 8.20.6 · 8.21.0 — 8.22.0
atlassian
jira server
≤ 8.13.8 · 8.14.0 — 8.20.6 · 8.21.0 — 8.22.0
atlassian
jira service management
≤ 4.13.8 · ≤ 4.13.18 · 4.14.0 — 4.20.6

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-2 Flaw Remediation
  • AC-3 Access Enforcement
  • IA-2 Identification and Authentication (Organizational Users)
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 8 hardening rules · 5 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V6.4.4
  • V6.5.4
  • V6.5.5
  • V6.5.7

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires timely application of vendor patches that close the Seraph authentication-bypass flaw.

prevent

Enforces that every request must be authenticated and authorized before any Jira resource is accessed, blocking the crafted-request bypass.

prevent

Mandates identification and authentication of organizational users prior to granting access, directly countering the missing or bypassed authentication check.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-03 mostly match
prevents

PR.AA-03 directly enforces authentication mechanisms that eliminate most improper-authentication defects, yet CWE-287 spans additional vectors (missing checks, flawed protocols, session handling) that one control does not fully close.

PR.AA-04 mostly match
prevents

PR.AA-04 directly enables verification of identity assertions (mostly preventing CWE-287 in that scope) yet leaves many other authentication failure modes unaddressed (only partial prevention overall).

PR.AA-01 partial match
prevents

PR.AA-01 supplies and governs credentials/tokens that authentication relies on, removing some weak-credential cases, yet leaves verification logic, missing checks, and protocol flaws untouched.

PR.AA-02 partial match
prevents

PR.AA-02 ensures valid enrollment and unique credential binding, which reduces some improper-auth risks at issuance time but leaves runtime claim verification untouched, so each direction only partially addresses the other.

PR.PS-01 partial match
prevents

PR.PS-01 can enforce auth-related settings via hardened baselines and default reviews, blocking some config-based instances of CWE-287, yet leaves code-level auth flaws untouched so neither direction reaches mostly.

PR.PS-02 partial match
prevents

Patching/maintenance can remediate some known auth vulnerabilities after deployment (partial forward) but does not address the design or implementation of authentication logic itself (none reverse).

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Requiring authentication methods whose strength matches the sensitivity of the data and mandating multi-factor authentication directly blocks attempts to access resources without proving identity.

prevents

Verifying user identity before issuing replacement credentials and forcing changes after compromise reduces the likelihood that authentication bypass can be achieved through stolen or weak credentials.

prevents

Mandating segregated approval and oversight for non-human identities reduces the chance that weak or orphaned credentials can be exploited for unauthorized authentication.

mitigates

Requiring authentication mechanisms and technical parameters for secure connections ensures that network services verify user identity before granting access, preventing exploitation of missing or weak authentication.

prevents

Security requirements specified early and verified through testing drive the consistent implementation of authentication mechanisms, decreasing the likelihood that authentication steps are omitted or incorrectly applied.

prevents

Defining the required level of trust in entity identity and the authentication mechanisms to achieve it ensures that authentication is explicitly addressed rather than omitted.

References