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.
The product communicates with a host that provides a certificate, but the product does not properly ensure that the certificate is actually associated with that host.
The product does not validate, or incorrectly validates, a certificate.
| Link | Tags |
|---|---|
| https://github.com/palantir/security-bulletins/blob/main/PLTRSEC-2022-15.md | vendor advisory |