CVE-2022-26135 Server-side request forgery in Jira Core Server
Remote authenticated users can perform server-side request forgery via a batch endpoint in the Jira Mobile Plugin, allowing full read access to internal resources.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2022-26135?
CVE-2022-26135 is a medium-severity server-side request forgery vulnerability in Atlassian Jira Data Center, published on 30 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
A vulnerability in Mobile Plugin for Jira Data Center and Server allows a remote, authenticated user (including a user who joined via the sign-up feature) to perform a full read server-side request forgery via a batch endpoint. This affects Atlassian Jira Server and Data Center from version 8.0.0 before version 8.13.22, from version 8.14.0 before 8.20.10, from version 8.21.0 before 8.22.4. This also affects Jira Management Server and Data Center versions from version 4.0.0 before 4.13.22, from version 4.14.0 before 4.20.10 and from version 4.21.0 before 4.22.4.
Weakness: CWE-918
Which versions are affected by CVE-2022-26135?
It affects 4 products.
Products include Atlassian Jira Data Center, Atlassian Jira Server, Atlassian Jira Service Desk, Atlassian Jira Service Management.
How do I fix CVE-2022-26135?
No fix has been published for CVE-2022-26135 yet. Limit exposure of the affected software until one is available.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2022-26135 being exploited?
There is no known exploitation of CVE-2022-26135 in the wild and no public exploit code.
Public exploit code: 2 proofs of concept on GitHub.
Other vulnerabilities in Atlassian Jira Data Center
Sources
Also known as GHSA-wfhv-4qh5-c632.