-
Public Security Vulnerability
-
Resolution: Fixed
-
Low (View bug fix roadmap)
-
8.13.21, 8.20.9, 8.22.3
-
9.4
-
Critical
-
CVE-2022-26136
Multiple Servlet Filter vulnerabilities have been fixed in Jira Server and Data Center. These vulnerabilities also affect other Atlassian products. For more information, refer to Atlassian's security advisory.
Arbitrary Servlet Filter Bypass (CVE-2022-26136)
A remote, unauthenticated attacker can bypass Servlet Filters used by first and third party apps. The impact depends on which filters are used by each app, and how the filters are used. Atlassian has released updates that fix the root cause of this vulnerability, but has not exhaustively enumerated all potential consequences of this vulnerability. Only the following attacks have been confirmed:
Authentication bypass. Sending a specially crafted HTTP request can bypass custom Servlet Filters used by third party apps to enforce authentication. A remote, unauthenticated attacker can exploit this to bypass authentication used by third party apps. Please note Atlassian has confirmed this attack is possible, but has not determined a list of all affected apps.
Cross-site scripting (XSS). Sending a specially crafted HTTP request can bypass the Servlet Filter used to validate legitimate Atlassian Gadgets, which can result in XSS. An attacker that can trick a user into requesting a malicious URL can execute arbitrary Javascript in the user’s browser.
Additional Servlet Filter Invocation (CVE-2022-26137)
A remote, unauthenticated attacker can cause additional Servlet Filters to be invoked when the application processes requests or responses. Atlassian has confirmed and fixed the only known security issue associated with this vulnerability:
Cross-origin resource sharing (CORS) bypass. Sending a specially crafted HTTP request can invoke the Servlet Filter used to respond to CORS requests, resulting in a CORS bypass. An attacker that can trick a user into requesting a malicious URL can access the vulnerable application with the victim’s permissions.
Affected versions:
- Versions < 8.13.22
- All versions 8.14.x through 8.19.x
- 8.20.x < 8.20.10
- All versions 8.21.x
- 8.22.x < 8.22.4
Fixed versions:
- 8.13.x >= 8.13.22 (LTS)
- 8.20.x >= 8.20.10 (LTS)
- 8.22.x >= 8.22.4
8.22.4 contains a high impact non-security bug. Atlassian recommends updating to latest version (currently 8.22.6). - Versions >= 9.0.0
References
[JRASERVER-73897] Jira: Multiple Servlet Filter Vulnerabilities
Thank you @Gonchik, for the suggestion, If we change our expired license to evaluation license, and upgrade the version, would our installed add-ons work ?
Because, all our purchased add-on licenses are of 2000 users & instance license are of tier 2000 users.
The page at https://confluence.atlassian.com/security/multiple-products-security-advisory-cve-2022-26136-cve-2022-26137-1141493031.html has links to downloads that fix this
Hi Team,
where we can find this CVE-2022-26136 and CVE-2022-26137
updates that fix the root cause of this vulnerability.
af0beb484f0d just enroll evaluation license during purchase process.
Matt, because every month I see CVE for Atlassian , that's why I typed unfortunately
How about the instances which are processing their license purchase for Server/DC ?
Our instance license is expired, and we are processing a license purchase and it would take another 2 weeks, what should we do in this case to fix this vulnerability?
Severity != Priority
See https://www.atlassian.com/trust/security/bug-fix-policy
Please can you help me understand why the CVE score "Critical" but the Atlassian issue priority for this issue is "Low"?
Does this vulnerability also affect HTTPS request?