{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-48308 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-48308 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-48308 is a medium-severity vulnerability in Palantir sls-logging, published on 16 Feb 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-48308 and fix it if it is affected.\n\nWhat it is: CVE-2022-48308 is a medium-severity vulnerability in Palantir sls-logging, published on 16 Feb 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-48308 in the wild and no public exploit code.\n\nAffected product: Palantir sls-logging. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-48308/ (Markdown: https://insights.sbomify.com/CVE-2022-48308/index.md)","id":"CVE-2022-48308","markdown":"https://insights.sbomify.com/CVE-2022-48308/index.md","name":"CVE-2022-48308","record":{"aliases":["GHSA-75c8-7ffr-5p4j"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Java logging library","requires_auth":"low_privilege","summary":"A man-in-the-middle attack is possible due to missing TLS hostname verification, allowing attackers to intercept or modify network communications.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Palantir","cpe":[{"product":"sls-logging","vendor":"palantir"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"},{"id":"CWE-297","name":"Improper Validation of Certificate with Host Mismatch"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Security feature bypass in sls-logging","id":"CVE-2022-48308","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site request forgery in Sophos Connect Client","id":"CVE-2022-48309"},"packages":[],"prev":{"headline":"Security feature bypass in Foundry Magritte","id":"CVE-2022-48307"},"products":["sls-logging"],"published":"2023-02-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-18","vendors":["Palantir"]},"summary":"A man-in-the-middle attack is possible due to missing TLS hostname verification, allowing attackers to intercept or modify network communications.","url":"https://insights.sbomify.com/CVE-2022-48308/"}