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.
Metrics
Affected Vendors & Products
References
History
No history.
MITRE
Status: PUBLISHED
Assigner: Palantir
Published: 2023-02-16T00:00:00
Updated: 2024-08-03T05:41:10.808Z
Reserved: 2022-03-25T00:00:00
Link: CVE-2022-27890
Vulnrichment
No data.
NVD
Status : Modified
Published: 2023-02-16T16:15:11.930
Modified: 2024-11-21T06:56:25.430
Link: CVE-2022-27890
Redhat
No data.