dbcve.org
Foundry IssuesApplication · Palantir

CVE-2022-27888

MEDIUM · 5.5 CVSS v3.1 Published 2022-04-26
Fix available
A fix is available. Upgrade to 2.249.1 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Foundry Issues service versions 2.244.0 to 2.249.0 was found to be logging in a manner that captured sensitive information (session tokens). This issue was fixed in 2.249.1.

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

The Foundry Issues service versions 2.244.0 through 2.249.0 had improper logging configuration that captured session tokens in plaintext logs. An attacker with access to those logs could extract valid session tokens and impersonate authenticated users.

MitigationUpgrade Foundry Issues service to version 2.249.1 or later. Review and rotate any session tokens that may have been exposed in logs, and ensure logging configurations exclude sensitive authentication data.

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
Foundry IssuesApplication
Affected:>= 2.244.0, < 2.249.1

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/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 Foundry Issues service version
    Query the Foundry platform or container metadata for the installed version of the Palantir Foundry Issues service. This may be available via the Foundry admin console, container orchestration labels, or service configuration files.
    Affected if The installed version is 2.244.0 through 2.249.0 (inclusive)
  2. Compare version to vulnerable range
    Review the identified version against the affected range: versions >= 2.244.0 and < 2.249.1 are vulnerable.
    Affected if The version falls within 2.244.0 to 2.249.0
  3. Inspect logging configuration
    Examine the logging configuration for the Foundry Issues service. Look for settings or filters related to HTTP request headers, cookies, or authentication tokens. Specifically check if session token or authorization header capture is enabled in the logging framework.
    Affected if Logging configuration captures HTTP headers, cookies, or specifically session tokens in plaintext
  4. Search logs for plaintext session tokens
    Search the Foundry Issues service log files for patterns resembling session tokens (often long alphanumeric strings, JWT format, or session IDs in cookie headers). Use grep or similar tools to search log directories for keywords like 'session', 'token', 'cookie', or examine raw log entries for suspicious plaintext credential-like strings.
    Affected if Log files contain plaintext session tokens or authentication credentials

You are affected if the Foundry Issues service version is between 2.244.0 and 2.249.0 AND either the logging configuration captures authentication data OR plaintext session tokens are present in the logs.

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 2.249.1 or later
Fixed in 2.249.1
Interim mitigation

Upgrade Foundry Issues service to version 2.249.1 or later. Review and rotate any session tokens that may have been exposed in logs, and ensure logging configurations exclude sensitive authentication data.

Recommended fix High confidence

2.249.1 or later

  1. Upgrade Foundry Issues service from any version between 2.244.0 and 2.249.0 to version 2.249.1 or later
  2. After upgrading, verify that session tokens are no longer being written to logs
  3. Review existing log files to ensure no sensitive session token information was previously captured and can be securely disposed of if needed

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

Fix this in Foundry Issues Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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