Authenticated import configuration disclosure via broken access control
Published Feb 15, 2022 · Updated Oct 8, 2024
Broken access control in Atlassian Jira Service Management before 4.21.0 allows remote authenticated users to view import source configuration. The Insight Import Source feature returns configuration details without enforcing the required authorization, although Atlassian has not published the flawed check or request path. A low-privileged authenticated account is required, and published evidence limits the consequence to reading configuration information rather than altering data or interrupting service.
Summary
What happened
Broken access control in Atlassian Jira Service Management before 4.21.0 allows remote authenticated users to view import source configuration. The Insight Import Source feature returns configuration details without enforcing the required authorization, although Atlassian has not published the flawed check or request path. A low-privileged authenticated account is required, and published evidence limits the consequence to reading configuration information rather than altering data or interrupting service.
The record
- CVE
- CVE-2021-43950
- Published
- Feb 15, 2022
- Updated
- Oct 8, 2024
- Vendor
- Atlassian
- Product
- Jira Service Management Server
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 15, 2022CVE publishedPublication date reported by the CVE source.
- Oct 8, 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 <4.21.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