CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2022 · Palantir

CVE-2022-27890
Palantir Atlasdb vulnerability

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.

Affected products

Atlasdb. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Palantir Atlasdb runs anywhere in your environment, including systems of suppliers.
  • UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
  • Set the orderSystems that can be reached from the internet come first, then the rest.

References

More vulnerabilities in Palantir products

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.