Whitelist rule disclosure via missing endpoint authorization
Published Sep 14, 2021 · Updated Oct 9, 2024
Improper authorization in Atlassian Jira Server and Data Center before 8.13.3 and 8.14.0 allows remote attackers to view whitelist rules. The /rest/whitelist//check endpoint returns configured whitelist-rule data without enforcing authentication or authorization. No account or user interaction is required; exposure is limited to reading whitelist configuration, with no reported modification or service interruption.
Summary
What happened
Improper authorization in Atlassian Jira Server and Data Center before 8.13.3 and 8.14.0 allows remote attackers to view whitelist rules. The /rest/whitelist//check endpoint returns configured whitelist-rule data without enforcing authentication or authorization. No account or user interaction is required; exposure is limited to reading whitelist configuration, with no reported modification or service interruption.
The record
- CVE
- CVE-2019-20101
- Published
- Sep 14, 2021
- Updated
- Oct 9, 2024
- Vendor
- Atlassian
- Product
- Jira Server
- Classifications
- T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 14, 2021CVE publishedPublication date reported by the CVE source.
- Oct 9, 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=0 <8.13.3
- Affected versionversion=8.14.0 <8.14.1
- Affected versionversion=8.14.0 <unspecified
- Affected versionversion=unspecified <8.13.3
- Affected versionversion=unspecified <8.14.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.
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