CVE-2022-27892
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 have allowed an attacker to exhaust the memory of the Gotham dispatch service.
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 allows remote attackers to cause memory exhaustion (Denial of Service) on the Gotham dispatch service. No authentication is required to trigger the memory exhaustion, making this a network-exploitable DoS vulnerability with high availability impact.
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 installationLocate Palantir Gotham components on your system. Check for Gotham dispatch service processes or installed packages using system inventory tools.Affected if Palantir Gotham is installed on the system
-
Determine installed Gotham versionQuery the Gotham dispatch service for its version information, typically via the product's built-in version command, administrative console, or service metadata.Affected if The installed version is less than 3.22.11.2
-
Verify dispatch service accessibilityDetermine if the Gotham dispatch service is listening on network interfaces accessible from untrusted networks. Check firewall rules and network bindings.Affected if The dispatch service is exposed to untrusted network segments without authentication barriers
-
Confirm unauthenticated endpoint exposureTest connectivity to common Gotham dispatch service endpoints without providing credentials to verify they are accessible.Affected if Unauthenticated endpoints on the dispatch service are reachable from untrusted networks
You are affected if Palantir Gotham version is below 3.22.11.2 and the dispatch service is network-accessible to untrusted users.
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
Upgrade Palantir Gotham to version 3.22.11.2 or later to receive the vendor patch. As a compensating control, network segmentation or firewall rules can limit exposure to untrusted networks until the patch is applied.
Gotham version 3.22.11.2
- 1. Backup your current Gotham configuration and data.
- 2. Consult Palantir's official upgrade documentation for Gotham.
- 3. Stop the Gotham dispatch service before upgrading.
- 4. Upgrade Gotham to version 3.22.11.2 or later.
- 5. Verify the upgrade was successful by checking the Gotham version.
- 6. Restart the Gotham dispatch service.
- 7. Test that the previously vulnerable unauthenticated endpoint is no longer accessible or properly secured.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27892 — 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-27892 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