Unauthenticated logging changes via forged administrator requests
Published Jun 30, 2020 · Updated Sep 17, 2024
Cross-site request forgery in Atlassian Jira Server before 7.13.3 and from 8.0.0 before 8.1.0 allows remote attackers to alter runtime settings. Atlassian identifies the Logging and Profiling administration feature but has not published the affected request handler or missing anti-CSRF validation. The forged request requires interaction by a logged-in system administrator and changes logging or profiling state rather than Jira data.
Summary
What happened
Cross-site request forgery in Atlassian Jira Server before 7.13.3 and from 8.0.0 before 8.1.0 allows remote attackers to alter runtime settings. Atlassian identifies the Logging and Profiling administration feature but has not published the affected request handler or missing anti-CSRF validation. The forged request requires interaction by a logged-in system administrator and changes logging or profiling state rather than Jira data.
The record
- CVE
- CVE-2019-20415
- Published
- Jun 30, 2020
- Updated
- Sep 17, 2024
- Vendor
- Atlassian
- Product
- Jira Server
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 30, 2020CVE publishedPublication date reported by the CVE source.
- Sep 17, 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.0.0 <unspecified
- Affected versionversion=unspecified <7.13.3
- Affected versionversion=unspecified <8.1.0
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
No sourced classifications are available.
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