CVE-2023-22836
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 · uneditedIn cases where a multi-tenant stack user is operating Foundry’s Linter service, and the user changes a group name from the default value, the renamed value may be visible to the rest of the stack’s tenants.
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 confidenceIn Palantir Foundry's multi-tenant Linter service, when a user changes a group name from its default value, the renamed group name becomes visible to other tenants in the stack due to improper tenant isolation in the Linter service's group name handling.
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< 2.278.0CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 the installed version of Guardiansoft GuardianUse your system inventory or software management tools to determine the exact version number of Guardiansoft Guardian deployed in your environmentAffected if The installed version is lower than 2.278.0
-
Confirm the Linter service is activeCheck whether Foundry's Linter service is enabled and in use within your Palantir Foundry deploymentAffected if The Linter service is configured and running
-
Review custom group name configurationsExamine group configurations to determine if any group names have been changed from their default valuesAffected if Non-default group names exist in the configuration
You are affected if your Guardiansoft Guardian version is below 2.278.0, the Linter service is active, and custom group names have been configured, as renamed groups may be visible to other tenants.
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 · scoped2.278.0
This is a configuration or code-level fix in Foundry's Linter service to properly scope group names per tenant. Organizations should contact Palantir for a patch or guidance onworkaround until a fix is available.
Guardian 2.278.0
- 1. Identify the current version of Guardian currently deployed in your stack
- 2. Review the Guardian 2.278.0 release notes and changelog for details on the security fix and any other changes
- 3. Ensure you have a backup of your current Guardian configuration
- 4. Follow the standard Guardian upgrade procedure for your deployment method (e.g., via Palantir Foundry console, CLI, or deployment pipeline)
- 5. Upgrade Guardian to version 2.278.0 or later
- 6. Verify the upgrade was successful and confirm the multi-tenant authorization fix is applied
- 7. Test that group name changes in the Linter service are no longer visible to other tenants in the multi-tenant stack
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22836 — 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-2023-22836 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