CVE-2022-27895
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 · uneditedInformation Exposure Through Log Files vulnerability discovered in Foundry when logs were captured using an underlying library known as Build2. This issue was present in versions earlier than 1.785.0. Upgrade to Build2 version 1.785.0 or greater.
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 confidenceAn information exposure vulnerability exists in Foundry where logs captured through the Build2 library can expose sensitive information. This occurs due to improper handling or protection of log file contents, allowing potential unauthorized access to sensitive data recorded in logs.
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< 1.785.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Foundry Build2 installationLocate the Build2 library in your environment. Check common installation paths or dependency manifests (e.g., package.json, requirements.txt, pom.xml) for the @foundry/build2 or palantir-build2 package.Affected if Build2 library is present in the environment
-
Determine installed Build2 versionRun a package manager command to inspect the installed version, such as npm list @foundry/build2, pip show build2, or check your dependency lock file for the specific version number.Affected if The installed version is below 1.785.0
-
Check if logging feature is enabledReview your application configuration files for logging settings related to Build2. Look for log4j, logback, or Python logging configurations that capture Build2 output.Affected if Logging is enabled and writing Build2 output to files or console
-
Inspect log file permissions and locationsExamine the filesystem permissions on any log directories used by your application. Verify who has read access to log files containing Build2 output.Affected if Log files containing Build2 data are readable by unauthorized users or processes
A user is affected if Foundry Build2 version is below 1.785.0 and logging is active, exposing potential sensitive data in log files.
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 · scoped1.785.0
Upgrade the Build2 library to version 1.785.0 or later to resolve the information exposure through log files.
Build2 version 1.785.0 or greater
- Identify the Foundry product and its Build2 dependency version currently in use
- Locate the dependency configuration file (e.g., package.json, pom.xml, build.gradle, or similar) that specifies the Build2 library version
- Update the Build2 library dependency to version 1.785.0 or higher
- Rebuild or recompile the Foundry application with the updated dependency
- Verify the upgrade was successful by checking the Build2 library version in the deployed artifact
- Test the application to ensure functionality remains intact after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27895 — 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-27895 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