Authenticated project disclosure via unchecked project identifier
Published Mar 16, 2020 · Updated Aug 5, 2024
Broken access control in Dradis Pro 3.4.1 allows remote authenticated users to read project content through the issues API. The /pro/api/issues/ endpoint accepts a Dradis-Project-Id header without verifying that the token holder belongs to the referenced project's team. Any authenticated author can substitute another project's identifier and retrieve sensitive client vulnerability descriptions.
Summary
What happened
Broken access control in Dradis Pro 3.4.1 allows remote authenticated users to read project content through the issues API. The /pro/api/issues/ endpoint accepts a Dradis-Project-Id header without verifying that the token holder belongs to the referenced project's team. Any authenticated author can substitute another project's identifier and retrieve sensitive client vulnerability descriptions.
The record
- CVE
- CVE-2019-19946
- Published
- Mar 16, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-639, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 16, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Bishop Fox Dradis Pro IDOR HTTP requestproof of concept · demonstrated
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