dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-49581

MEDIUM · 6.5 CVSS v3.1 Published 2024-12-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Restricted Views backed objects (OSV1) could be bypassed under specific circumstances due to a software bug, this could have allowed users that didn't have permission to see such objects to view them via Object Explorer directly. This software bug did not impact or otherwise make data available across organizational boundaries nor did it allow for data to be viewed or accessed by unauthenticated users. The affected service have been patched and automatically deployed to all Apollo-managed Foundry instances.

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

A software bug in Palantir Foundry allowed Restricted Views backed objects (OSV1) to be bypassed, potentially permitting users without proper permissions to view restricted objects through Object Explorer. The vulnerability did not allow cross-organizational data access or unauthenticated access.

MitigationThe affected service has been automatically patched and deployed to all Apollo-managed Foundry instances; verify the patch status in the Apollo console and confirm authorization controls are functioning as expected.

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

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. Check Apollo console patch status
    Log in to the Apollo console for your Foundry instance and locate the service related to Object Explorer or OSV1 (Object Security Version 1) Restricted Views. Verify that the patch for CVE-2024-49581 has been applied and the deployment status shows as active.
    Affected if The patch status is not applied, shows as failed, or the deployment is not active in the Apollo console.
  2. Verify Object Explorer authorization controls
    Using an account without permissions to view a specific restricted object, attempt to access that object through Object Explorer. Then confirm with an authorized account that the same object is accessible to them. Compare the results.
    Affected if The unauthorized account can view the restricted object while the authorized account can also view it, indicating the bypass may still be present or authorization controls are not functioning correctly.
  3. Confirm Restricted Views enforcement on OSV1 objects
    Identify an object in Foundry that is backed by OSV1 (Restricted Views). Using an account that should NOT have access to this restricted object, attempt to view it through Object Explorer or any Foundry interface. Check the access logs or audit trails if available.
    Affected if The restricted object is visible or accessible to a user who should not have permission, indicating the vulnerability may still be exploitable.
  4. Review audit logs for unauthorized access attempts
    Access Foundry's audit logs or security event logs and search for instances where users accessed objects outside their authorized scope, particularly around Object Explorer usage and OSV1-backed objects. Look for any anomalous access patterns.
    Affected if Audit logs show unauthorized access to restricted objects that should not have been accessible to those users.

If the Apollo patch is applied and active, authorization controls are functioning correctly, and no unauthorized access to restricted OSV1 objects is found in logs, the environment is likely not affected by this CVE.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

The affected service has been automatically patched and deployed to all Apollo-managed Foundry instances; verify the patch status in the Apollo console and confirm authorization controls are functioning as expected.

Recommended fix Moderate confidence
  1. No action required for Apollo-managed Foundry instances as the patch was automatically deployed.
  2. For self-managed or non-Apollo deployments, verify with Palantir support that the latest patch has been applied.
  3. If you suspect unauthorized access may have occurred, review Object Explorer access logs for the period between the vulnerability introduction and the patch deployment.

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-49581 — 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-2024-49581 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