CVE-2022-27890
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 · uneditedIt was discovered that the sls-logging was not verifying hostnames in TLS certificates due to a misuse of the javax.net.ssl.SSLSocketFactory API. A malicious attacker in a privileged network position could abuse this to perform a man-in-the-middle attack. A successful man-in-the-middle attack would allow them to intercept, read, or modify network communications to and from the affected service. In the case of AtlasDB, the vulnerability was mitigated by other network controls such as two-way TLS when deployed as part of a Palantir platform. Palantir still recommends upgrading to a non-vulnerable version out of an abundance of caution.
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 confidenceThe sls-logging library does not verify hostnames in TLS certificates due to misuse of the javax.net.ssl.SSLSocketFactory API. This allows a man-in-the-middle attacker in a privileged network position to intercept, read, or modify communications between the client and server.
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< 0.730.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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 if Palantir Atlasdb is installedSearch for Atlasdb installation directories, JAR files, or check build/packaging artifacts (pom.xml, gradle files, Docker images) for Atlasdb presenceAffected if Atlasdb is found in the environment
-
Determine installed Atlasdb versionCheck version metadata in JAR manifests, pom.xml dependencies, gradle lock files, or Docker image labels. Compare the version number against 0.730.0Affected if The installed version is lower than 0.730.0
-
Verify TLS client connections are in useReview application configuration files for SSL/TLS settings, look for javax.net.ssl properties, or examine code that initializes SSLSocketFactoryAffected if The application is configured to make outbound TLS connections
-
Confirm sls-logging library is presentInspect the dependency tree (Maven dependency:tree or Gradle dependencies) for the sls-logging library, or check lib/ directories for sls-logging JAR filesAffected if The sls-logging library is included in the runtime dependencies
A user is affected if Palantir Atlasdb version 0.730.0 or higher is not in use AND the application makes TLS connections using the vulnerable sls-logging library.
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 · scoped0.730.0
Upgrade to a non-vulnerable version of sls-logging. Where immediate upgrade is not feasible, ensure network controls such as mutual TLS (two-way TLS) are enforced to mitigate the MITM risk.
AtlasDB version 0.730.0
- Upgrade AtlasDB to version 0.730.0 or later to obtain the fixed sls-logging component
- Verify the upgrade in a test environment before deploying to production
- After upgrade, confirm TLS connections are properly validating hostnames
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27890 — 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-27890 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