Resource modification via referrer-leaked CSRF token
Published Oct 21, 2021 · Updated Oct 10, 2024
CSRF in Atlassian Jira Server and Data Center before 8.5.10 and 8.6.0 through 8.13.0 allows remote attackers to modify resources. A referrer header discloses a user's CSRF token, which Jira then accepts to authorize forged state-changing requests. Exploitation requires user interaction and possession of the leaked token; the public record does not identify the resources that can be changed.
Summary
What happened
CSRF in Atlassian Jira Server and Data Center before 8.5.10 and 8.6.0 through 8.13.0 allows remote attackers to modify resources. A referrer header discloses a user's CSRF token, which Jira then accepts to authorize forged state-changing requests. Exploitation requires user interaction and possession of the leaked token; the public record does not identify the resources that can be changed.
The record
- CVE
- CVE-2021-39126
- Published
- Oct 21, 2021
- Updated
- Oct 10, 2024
- Vendor
- Atlassian
- Product
- Jira Server
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 21, 2021CVE publishedPublication date reported by the CVE source.
- Oct 10, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=8.6.0 <unspecified
- Affected versionversion=unspecified <8.13.1
- Affected versionversion=unspecified <8.5.10
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo