Authenticated release-information disclosure via missing authorization
Published Mar 17, 2020 · Updated Sep 17, 2024
Missing authorization in Jira Software before 8.6.1 allows remote authenticated users to view release data from inaccessible projects. The ConfigureBambooRelease resource returns release-version information without verifying that the requesting account can access the associated project. Any authenticated account that can reach the resource can read otherwise restricted release metadata, but no modification or service interruption is reported.
Summary
What happened
Missing authorization in Jira Software before 8.6.1 allows remote authenticated users to view release data from inaccessible projects. The ConfigureBambooRelease resource returns release-version information without verifying that the requesting account can access the associated project. Any authenticated account that can reach the resource can read otherwise restricted release metadata, but no modification or service interruption is reported.
The record
- CVE
- CVE-2019-20407
- Published
- Mar 17, 2020
- Updated
- Sep 17, 2024
- Vendor
- Atlassian
- Product
- Jira Software
- Classifications
- CWE-862, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 17, 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=unspecified <8.6.1
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.
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