Project-title disclosure via missing API authorization
Published Feb 6, 2020 · Updated Sep 16, 2024
Improper authorization in Atlassian Jira Server before 8.6.0 allows remote authenticated users to read inaccessible project titles. The REST API returns a project's title without enforcing the requester's project-view permission. Any authenticated account able to reach the affected API can enumerate titles for projects otherwise hidden from that account.
Summary
What happened
Improper authorization in Atlassian Jira Server before 8.6.0 allows remote authenticated users to read inaccessible project titles. The REST API returns a project's title without enforcing the requester's project-view permission. Any authenticated account able to reach the affected API can enumerate titles for projects otherwise hidden from that account.
The record
- CVE
- CVE-2019-20404
- Published
- Feb 6, 2020
- Updated
- Sep 16, 2024
- Vendor
- Atlassian
- Product
- Jira Server
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 6, 2020CVE publishedPublication date reported by the CVE source.
- Sep 16, 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.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