Approved changes feed: RSS · Atom
cpe:2.3:a:palantir:atlasdb:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Palantir (bb329e3d-18af-5273-8fa1-03aa6516a02f) |
|---|---|
| Product | Atlasdb (01b3ad2f-8526-5b13-b94e-30f249f6d79f) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/palantir/atlasdb |
purl2cpe | 2026-06-01 10:16:00.649940 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-27890 |
vulnerable | 2026-06-03 14:46:54.116957 |
Details available
MEDIUM (6.3)
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.
Published: 2023-02-16T00:00:00.000Z
Updated: 2025-03-18T15:09:08.136Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.