dbcve.org
FoundryApplication · Palantir

CVE-2023-22833

MEDIUM · 6.5 CVSS v3.1 Published 2023-06-06
Fix available
A fix is available. Upgrade to after 2.531.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Palantir Foundry deployments running Lime2 versions between 2.519.0 and 2.532.0 were vulnerable a bug that allowed authenticated users within a Foundry organization to bypass discretionary or mandatory access controls under certain circumstances.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Palantir Foundry Lime2 versions 2.519.0 through 2.532.0 contain an access control bypass vulnerability where authenticated users within a Foundry organization could bypass discretionary (DAC) or mandatory (MAC) access controls under certain conditions, potentially allowing unauthorized data access or actions.

MitigationOrganizations should upgrade Lime2 to a version beyond 2.532.0 following Palantir's official upgrade guidance, and conduct access control audits to verify no unauthorized access occurred during the vulnerable period.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FoundryApplication
Affected:>= 2.519.0, <= 2.531.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Lime2 version
    Query the Palantir Foundry administration console or use the Foundry API to retrieve the Lime2 subsystem version number. This is typically found under System Administration > Components or via the /api/components endpoint.
    Affected if The installed Lime2 version is 2.519.0, 2.520.0, 2.521.0, 2.522.0, 2.523.0, 2.524.0, 2.525.0, 2.526.0, 2.527.0, 2.528.0, 2.529.0, 2.530.0, or 2.531.0 (or any version between 2.519.0 and 2.531.0 inclusive).
  2. Confirm DAC or MAC access controls are configured
    Navigate to Foundry Governance > Access Policies or Administration > Security > Access Control. Verify whether Discretionary Access Control (DAC) or Mandatory Access Control (MAC) policies have been defined for datasets or resources.
    Affected if DAC or MAC access control policies are actively enforced on any datasets or resources in the environment.
  3. Review access control audit logs for anomalies
    Access the Foundry Audit Log system (typically under Governance > Audit Logs or /api/audit). Search for access events around the time period when the vulnerable versions were in use, focusing on permission escalation events or unexpected resource access.
    Affected if Audit logs show access events that bypassed configured DAC or MAC policies, or indicate that users accessed resources outside their assigned permission scope.

Your environment is affected if Lime2 version is 2.519.0 through 2.531.0 and you have DAC or MAC access controls in use, warranting an audit of access logs for unauthorized access patterns.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.531.0
Interim mitigation

Organizations should upgrade Lime2 to a version beyond 2.532.0 following Palantir's official upgrade guidance, and conduct access control audits to verify no unauthorized access occurred during the vulnerable period.

Recommended fix High confidence

Upgrade to Foundry Lime2 version 2.532.0 or later

  1. Identify the current Foundry Lime2 version by checking the Foundry administration console or deployment metadata
  2. Schedule a maintenance window for the upgrade process
  3. Upgrade Foundry to version 2.532.0 or later to remediate the access control bypass vulnerability
  4. After upgrade, verify that the access control bypass is no longer present by testing discretionary and mandatory access controls
  5. Confirm the upgraded version in the administration console
Caveat Review Palantir release notes for any breaking changes between your current version and 2.532.0+; test critical workflows in a staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Foundry Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-22833 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-22833 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data