Vulnerability Description
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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Palantir | Atlasdb | < 0.730.0 |
Related Weaknesses (CWE)
References
- https://github.com/palantir/security-bulletins/blob/main/PLTRSEC-2022-15.mdVendor Advisory
- https://github.com/palantir/security-bulletins/blob/main/PLTRSEC-2022-15.mdVendor Advisory
FAQ
What is CVE-2022-27890?
CVE-2022-27890 is a vulnerability with a CVSS score of 6.3 (MEDIUM). 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 ...
How severe is CVE-2022-27890?
CVE-2022-27890 has been rated MEDIUM with a CVSS base score of 6.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2022-27890?
Check the references section above for vendor advisories and patch information. Affected products include: Palantir Atlasdb.