Jira Core Server: Improper Authentication
CVE-2022-0540 is a critical-severity improper authentication vulnerability in Jira Core Server from Atlassian, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 8.13.18, 8.20.6, 8.22.0 as the first without the flaw, so updating Jira Core Server to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 88.1% chance of exploitation within 30 days, which is in the top 0.23% of all scored CVEs.
Exploitation in the next 30 days is more likely than not, according to EPSS.
What to do
- Update Jira Core Server to 8.13.18 or 8.20.6 or 8.22.0, whichever matches your release line, or a later version.
- Update Jira Software Server to 8.13.18 or 8.20.6 or 8.22.0, whichever matches your release line, or a later version.
- Update Jira Software Data Center to 8.13.18 or 8.20.6 or 8.22.0, whichever matches your release line, or a later version.
- Read the advisory on confluence.atlassian.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Atlassian | Jira Core Server | before 8.13.18; 8.14.0; before 8.20.6; 8.21.0; before 8.22.0 | 8.13.18, 8.20.6, 8.22.0 |
| Atlassian | Jira Software Server | before 8.13.18; 8.14.0; before 8.20.6; 8.21.0; before 8.22.0 | 8.13.18, 8.20.6, 8.22.0 |
| Atlassian | Jira Software Data Center | before 8.13.18; 8.14.0; before 8.20.6; 8.21.0; before 8.22.0 | 8.13.18, 8.20.6, 8.22.0 |
| Atlassian | Jira Service Management Server | before 4.13.18; 4.14.0; before 4.20.6; 4.21.0; before 4.22.0 | 4.13.18, 4.20.6, 4.22.0 |
| Atlassian | Jira Service Management Data Center | before 4.13.18; 4.14.0; before 4.20.6; 4.21.0; before 4.22.0 | 4.13.18, 4.20.6, 4.22.0 |
| Atlassian | jira_data_center | before 8.13.18; 8.14.0 up to, but not including, 8.20.6; 8.21.0 up to, but not including, 8.22.0 | 8.13.18, 8.20.6, 8.22.0 |
| Atlassian | jira_server | before 8.13.18; 8.14.0 up to, but not including, 8.20.6; 8.21.0 up to, but not including, 8.22.0 | 8.13.18, 8.20.6, 8.22.0 |
| Atlassian | jira_service_management | before 4.13.18; 4.14.0 up to, but not including, 4.20.6; 4.21.0 up to, but not including, 4.22.0 | 4.13.18, 4.20.6, 4.22.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.8 | Critical | NVD |
| CVSS 3.1 | 9.8 | Critical | CISA (ADP) |
| CVSS 2.0 | 6.8 | Medium | NVD |
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Authentication
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
How developers prevent this class of flaw
- Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- confluence.atlassian.com/display/JIRA/Jira+Security+Advisory+2022-04-20Issue Tracking
- jira.atlassian.com/browse/JRASERVER-73650Issue Tracking
- jira.atlassian.com/browse/JSDSERVER-11224Issue Tracking
Other vulnerabilities in Jira Core Server
- 8.8 High severity
- 8.8 High severity
- 9.8 Critical severity
Recent Improper Authentication vulnerabilities
- 7.5 High severity
- 8.8 High severity
- 8.8 High severity
- 10.0 Critical severity
- 9.1 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.