CVE-2022-27897
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 · uneditedPalantir Gotham versions prior to 3.22.11.2 included an unauthenticated endpoint that would load portions of maliciously crafted zip files to memory. An attacker could repeatedly upload a malicious zip file, which would allow them to exhaust memory resources on the dispatch server.
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 confidencePalantir Gotham versions prior to 3.22.11.2 contain an unauthenticated endpoint that processes zip file uploads by loading portions of the file into memory. An attacker can repeatedly upload specially crafted zip files to exhaust memory resources on the dispatch server, causing denial of service.
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< 3.22.11.2CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 Palantir Gotham versionLocate the installed Gotham version via the product's admin console, version file, or system information panel. Common locations include the server management interface or version metadata in the installation directory.Affected if Installed version is below 3.22.11.2
-
Locate the dispatch serverIdentify which server handles file upload processing. This is typically the dispatch server component indicated in Gotham architecture documentation or server inventory.Affected if The dispatch server is the system receiving uploaded files
-
Verify endpoint exposureDetermine if the unauthenticated zip file upload endpoint is accessible from the network. Check whether network access controls or authentication are required to reach the upload functionality.Affected if The zip upload endpoint is exposed without authentication on the dispatch server
-
Assess network accessibilityReview firewall rules, network segmentation, or ACLs controlling access to the dispatch server's upload endpoint from external or untrusted networks.Affected if The endpoint can be reached from networks beyond the trusted internal environment
You are affected if Palantir Gotham version is prior to 3.22.11.2 AND the zip upload endpoint on the dispatch server is network-accessible without authentication.
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 · scoped3.22.11.2
Update Palantir Gotham to version 3.22.11.2 or later to receive the vendor patch. Additionally, implement network-level access controls to restrict exposure of the vulnerable endpoint and consider temporary rate limiting on file upload endpoints until patching is complete.
3.22.11.2
- Obtain Gotham version 3.22.11.2 from official Palantir distribution channels
- Review Palantir Gotham upgrade documentation for your deployment model
- Execute the standard upgrade procedure for your Gotham installation
- Verify the upgrade was successful by checking the Gotham version
- Confirm the vulnerable unauthenticated endpoint is no longer accessible or has been patched
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27897 — 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-2022-27897 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