# CVE-2022-27890: Weak cryptography in AtlasDB

> A library fails to verify TLS hostnames, allowing attackers in privileged network positions to intercept or modify communications via man-in-the-middle attacks.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Feb 2023
- **Updated:** 18 Mar 2025
- **Also known as:** GHSA-v8rr-9cww-2334

## What is CVE-2022-27890?

CVE-2022-27890 is a medium-severity vulnerability in Palantir AtlasDB, published on 16 Feb 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

It 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.

Weakness: CWE-295 (Improper Certificate Validation), CWE-297 (Improper Validation of Certificate with Host Mismatch)

## Which versions are affected by CVE-2022-27890?

It affects 1 product.


Products: Palantir Atlasdb.

## How do I fix CVE-2022-27890?

No fix has been published for CVE-2022-27890 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-27890 being exploited?

There is no known exploitation of CVE-2022-27890 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-27890 and fix it if it is affected.

What it is: CVE-2022-27890 is a medium-severity vulnerability in Palantir AtlasDB, published on 16 Feb 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-27890 in the wild and no public exploit code.

Affected product: Palantir AtlasDB. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-27890/ (Markdown: https://insights.sbomify.com/CVE-2022-27890/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-27890
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-27890
- OSV: https://osv.dev/vulnerability/CVE-2022-27890

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-27890/
Summaries are generated and may contain mistakes; the official description above is the record.