CVE-2024-49587
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 · uneditedGlutton V1 service endpoints were exposed without any authentication on Gotham stacks, this could have allowed users that did not have any permission to hit glutton backend directly and read/update/delete data. The affected service has been patched and automatically deployed to all Apollo-managed Gotham 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 · high confidenceGlutton V1 service endpoints on Gotham stacks were exposed without authentication, allowing unauthorized users to directly access the glutton backend and perform read, update, and delete operations on data without any permission checks.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Glutton V1 service presenceCheck if the Glutton V1 service is running on your Gotham stack by reviewing your deployed services, container logs, or service inventory. Look for processes or containers named 'glutton' or related backend services.Affected if Glutton V1 service is deployed and running on your Gotham stack.
-
Verify authentication enforcement on Glutton endpointsAttempt to access Glutton V1 service endpoints (typically REST API endpoints for the glutton backend) without providing any credentials. Use a tool like curl to send requests to the service URLs.Affected if Endpoints respond successfully without requiring any authentication token or credentials.
-
Check for unauthorized data access capabilitySend read, update, or delete requests to the Glutton backend API without authentication and observe if operations complete without permission validation.Affected if Read, update, or delete operations execute successfully without authentication or authorization checks.
-
Review Glutton service versionInspect the Glutton service version by checking the deployed artifact, container image tag, or service metadata. Compare against any known patched versions or the original vulnerable V1 release.Affected if The deployed Glutton version is an unpatched V1 release that lacks authentication enforcement.
You are affected if Glutton V1 service is running on your Gotham stack and its endpoints are accessible and functional without any authentication credentials.
Generated from the published advisory. Verify against your own configuration.
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 · scopedVerify that the patch has been applied to all Gotham stack instances; for non-Apollo-managed instances, manually apply the patched Glutton V1 service and confirm authentication is now enforced on all endpoints.
- This vulnerability has already been addressed by Palantir. The description states: 'The affected service has been patched and automatically deployed to all Apollo-managed Gotham Instances'. No manual action is required as the fix was automatically deployed.
- If you are managing Gotham instances outside of Apollo, verify that the Glutton V1 service has been updated to include authentication on all endpoints.
- Confirm through Palantir Safebase or your Palantir contact that your Gotham stack is running the patched Glutton version.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49587 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-49587 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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