CVE-2022-48308

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.

Categories

6.3
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.13%
Vendor Advisory github.com
Affected: Palantir sls-logging
Published at:
Updated at:

References

Link Tags
https://github.com/palantir/security-bulletins/blob/main/PLTRSEC-2022-14.md vendor advisory

Frequently Asked Questions

What is the severity of CVE-2022-48308?
CVE-2022-48308 has been scored as a medium severity vulnerability.
How to fix CVE-2022-48308?
To fix CVE-2022-48308, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-48308 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2022-48308 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-48308?
CVE-2022-48308 affects Palantir sls-logging.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.