Authenticated discretionary and mandatory access-control bypass
Published Jun 6, 2023 · Updated Jan 7, 2025
Access-control bypass in Lime2 before 2.532.0 allows remote authenticated users to bypass discretionary or mandatory access controls. Palantir states that Lime2 skips a required authentication step, but it has not disclosed the affected interface or the triggering input or state. Exploitation requires a Foundry organization account and an affected release starting at 2.519.0; unauthorized access can expose data and permit limited changes or service interruption.
Summary
What happened
Access-control bypass in Lime2 before 2.532.0 allows remote authenticated users to bypass discretionary or mandatory access controls. Palantir states that Lime2 skips a required authentication step, but it has not disclosed the affected interface or the triggering input or state. Exploitation requires a Foundry organization account and an affected release starting at 2.519.0; unauthorized access can expose data and permit limited changes or service interruption.
The record
- CVE
- CVE-2023-22833
- Published
- Jun 6, 2023
- Updated
- Jan 7, 2025
- Vendor
- Palantir Technologies
- Product
- Lime2
- Classifications
- CWE-863, CWE-304, CAPEC-36
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 6, 2023CVE publishedPublication date reported by the CVE source.
- Jan 7, 2025Record 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.519.0 <2.532.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