CVE-2022-27894
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 · uneditedThe Foundry Blobster service was found to have a cross-site scripting (XSS) vulnerability that could have allowed an attacker with access to Foundry to launch attacks against other users. This vulnerability is resolved in Blobster 3.228.0.
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 confidenceThe Foundry Blobster service contains a cross-site scripting (XSS) vulnerability that allows authenticated attackers to inject malicious scripts into web pages viewed by other Foundry users. This stored XSS could enable session hijacking, credential theft, or further propagation of malicious content within the Foundry application.
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.207.0, < 3.227.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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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 Foundry Blobster installationLocate Blobster service by checking for 'blobster' in running processes, installed packages, or service definitions within the Foundry/Palantir deploymentAffected if Blobster service is not found in the environment
-
Determine Blobster versionCheck the installed Blobster version via the service's version endpoint, configuration files, or deployment metadata - typically accessible through the Foundry administration interface or service logsAffected if Unable to retrieve version information for Blobster
-
Compare version against affected rangeCompare the installed Blobster version to the affected range: versions >= 3.207.0 and < 3.227.0Affected if Installed version falls within >= 3.207.0 and < 3.227.0
-
Verify Blobster web service is exposedConfirm that the Blobster web interface or API endpoints are accessible from the network where users interact with FoundryAffected if Blobster service is exposed and reachable by users
The environment is affected if Foundry Blobster is installed with a version between 3.207.0 and 3.226.x inclusive, and the Blobster web service is accessible to authenticated 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.227.0
Upgrade Blobster to version 3.228.0 or later to remediate the vulnerability. Since the attack requires an attacker to have existing access to Foundry, also review user permissions and implement additional input validation as defense-in-depth.
Blobster 3.228.0
- Upgrade Foundry Blobster from the current version to version 3.228.0 or later
- Verify the upgrade completed successfully by checking the Blobster version
- Test that the application functions correctly and the XSS vulnerability is no longer exploitable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27894 — 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-27894 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