NVD / CVE Program· CNA atlassian

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

CriticalCVSS 9.8 · v3.1—Proof of concept No fix recorded

Noroxi assessment

Priority: This week (action score 65/100)

A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 88% (FIRST EPSS); higher than 99.7% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
According to the record, no fixed version is available yet.

Don’t wait for the next maintenance window. Until a fix is released, restrict access to the affected component and follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

BDU:2022-02565

Published: Apr 20, 2022
Updated: Jun 17, 2026
EPSS: 88.0% · 99th percentile
CWE: CWE-287

Report tools

JSON

Action score

This week

Don’t wait for the next maintenance window.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 26 / 30 · 88.0%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
atlassian	jira data center	cpe:2.3:a:atlassian:jira_data_center
atlassian	jira server	cpe:2.3:a:atlassian:jira_server
atlassian	jira service management	cpe:2.3:a:atlassian:jira_service_management

Versions reported by the vendor

Affected version ranges reported by the assigning authority (atlassian). Independent of NVD's CPE analysis and usually ahead of it.

Atlassian Jira Core Server
- unspecified and later · before 8.13.18affected
- 8.14.0 and later · before unspecifiedaffected
- unspecified and later · before 8.20.6affected
- 8.21.0 and later · before unspecifiedaffected
- unspecified and later · before 8.22.0affected
Atlassian Jira Service Management Data Center
- unspecified and later · before 4.13.18affected
- 4.14.0 and later · before unspecifiedaffected
- unspecified and later · before 4.20.6affected
- 4.21.0 and later · before unspecifiedaffected
- unspecified and later · before 4.22.0affected
Atlassian Jira Service Management Server
- unspecified and later · before 4.13.18affected
- 4.14.0 and later · before unspecifiedaffected
- unspecified and later · before 4.20.6affected
- 4.21.0 and later · before unspecifiedaffected
- unspecified and later · before 4.22.0affected
Atlassian Jira Software Data Center
- unspecified and later · before 8.13.18affected
- 8.14.0 and later · before unspecifiedaffected
- unspecified and later · before 8.20.6affected
- 8.21.0 and later · before unspecifiedaffected
- unspecified and later · before 8.22.0affected
Atlassian Jira Software Server
- unspecified and later · before 8.13.18affected
- 8.14.0 and later · before unspecifiedaffected
- unspecified and later · before 8.20.6affected
- 8.21.0 and later · before unspecifiedaffected
- unspecified and later · before 8.22.0affected

Affected versions · NVD (10)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

atlassian jira data centerbefore 8.13.8
atlassian jira data center8.14.0 and later · before 8.20.6
atlassian jira data center8.21.0 and later · before 8.22.0
atlassian jira serverbefore 8.13.8
atlassian jira server8.14.0 and later · before 8.20.6
atlassian jira server8.21.0 and later · before 8.22.0
atlassian jira service managementbefore 4.13.8
atlassian jira service managementbefore 4.13.18
atlassian jira service management4.14.0 and later · before 4.20.6
atlassian jira service management4.21.0 and later · before 4.22.0

Same product

atlassian: all records

Other highest-scoring records for the same primary product.

CVE-2021-26086Affected versions of Atlassian Jira Server and Data Center allow remote attackers to read particular files via a path traversal…KEV
81Now
CVE-2020-36239Jira Data Center, Jira Core Data Center, Jira Software Data Center from version 6.3.0 before 8.5.16, from 8.6.0 before 8.13.8, from 8.14.0…
54Plan
CVE-2022-26135A vulnerability in Mobile Plugin for Jira Data Center and Server allows a remote, authenticated user (including a user who joined via the…
47Plan

Published before and after this one in the same product

← EarlierCVE-2021-43941Feb 15, 2022 · Affected versions of Atlassian Jira Server and Data Center allow remote attackers to modify several resources (including…
26Monitor
← EarlierCVE-2021-43944Mar 7, 2022 · This issue exists to document that a security improvement in the way that Jira Server and Data Center use templates has been implemented.
29Monitor
Later →CVE-2022-36799Aug 1, 2022 · This issue exists to document that a security improvement in the way that Jira Server and Data Center use templates has been implemented.
42Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Nuclei detection template ×1
Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Nuclei detection template	Nuclei template CVE-2022-0540	—
Proof-of-concept repository on GitHub	stars:71	2022-05-25

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedApr 20, 2022
First PoCMay 25, 2022+34 d
TodayNov 14, 2026+1669 d

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2022-2613571 days apartA vulnerability in Mobile Plugin for Jira Data Center and Server allows a remote, authenticated user (including a user who joined via the…
47Plan
CVE-2022-36799103 days apartThis issue exists to document that a security improvement in the way that Jira Server and Data Center use templates has been implemented.
42Plan
CVE-2021-4394444 days apartThis issue exists to document that a security improvement in the way that Jira Server and Data Center use templates has been implemented.
29Monitor

Bug bounty scope

AtlassianBugcrowd · paid · up to $12,000

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-287 · Improper Authentication

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1app.use("/admin", requireSession, adminRouter);
2

3// Route added later skips the middleware
4app.post("/admin-api/config", updateConfig);

Fixed

1const admin = express.Router();
2admin.use(requireSession, requireRole("admin"));
3

4admin.post("/config", updateConfig);
5app.use("/admin", admin);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log (0)

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

confluence.atlassian.com/display/JIRA/Jira+Security+Advisory+2022-04-20

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records