Attachment disclosure via UUID authorization bypass
Published Jul 10, 2023 · Updated Oct 23, 2024
Authorization bypass in Palantir Technologies Foundry Comments before 2.267.0 allows remote authenticated users to read other comments' attachments. The attachment-retrieval path accepts an internal attachment UUID and returns its contents without confirming access to the comment that owns it. An authenticated Foundry account and prior knowledge of the target UUID are required; the disclosed impact is attachment confidentiality only.
Summary
What happened
Authorization bypass in Palantir Technologies Foundry Comments before 2.267.0 allows remote authenticated users to read other comments' attachments. The attachment-retrieval path accepts an internal attachment UUID and returns its contents without confirming access to the comment that owns it. An authenticated Foundry account and prior knowledge of the target UUID are required; the disclosed impact is attachment confidentiality only.
The record
- CVE
- CVE-2023-30956
- Published
- Jul 10, 2023
- Updated
- Oct 23, 2024
- Vendor
- Palantir Technologies
- Product
- Foundry Comments
- Classifications
- CWE-639, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 10, 2023CVE publishedPublication date reported by the CVE source.
- Oct 23, 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.267.0
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.
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