Cross-resource disclosure and storage changes via PATCH
Published Sep 30, 2024 · Updated Sep 30, 2024
Incorrect authorization in CVAT 2.0.0 through 2.19.0 allows remote authenticated users to read or alter other users' resources via PATCH requests. The project, task, job, and membership update paths omitted the view permission scope, while storage fields lacked their dedicated authorization scope. Any account can target guessed resource identifiers to obtain the corresponding GET response, and project or task storage changes modify persistent configuration.
Summary
What happened
Incorrect authorization in CVAT 2.0.0 through 2.19.0 allows remote authenticated users to read or alter other users' resources via PATCH requests. The project, task, job, and membership update paths omitted the view permission scope, while storage fields lacked their dedicated authorization scope. Any account can target guessed resource identifiers to obtain the corresponding GET response, and project or task storage changes modify persistent configuration.
The record
- CVE
- CVE-2024-47172
- Published
- Sep 30, 2024
- Updated
- Sep 30, 2024
- Vendor
- CVAT.ai
- Product
- CVAT
- Classifications
- CWE-863, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 30, 2024CVE publishedPublication date reported by the CVE source.
- Sep 30, 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=>= 2.0.0, < 2.19.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- PATCH endpoint authorization-bypass proof of conceptproof 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