First published: Thu Feb 16 2023(Updated: )
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.
Credit: cve-coordination@palantir.com
Affected Software | Affected Version | How to fix |
---|---|---|
Palantir AtlasDB | <0.730.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-27890 is a vulnerability in the sls-logging component of Palantir Atlasdb that allows a malicious attacker in a privileged network position to perform a man-in-the-middle attack.
CVE-2022-27890 has a severity rating of 7.4, which is considered high.
CVE-2022-27890 occurs due to a misuse of the javax.net.ssl.SSLSocketFactory API, which leads to the sls-logging component not verifying hostnames in TLS certificates.
The affected software for CVE-2022-27890 is Palantir Atlasdb up to version 0.730.0.
Yes, you should update Palantir Atlasdb to a version beyond 0.730.0 to fix CVE-2022-27890.