{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-32156 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-32156 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-32156 is a high-severity vulnerability in Splunk Splunk, published on 14 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-32156 and fix it if it is affected.\n\nWhat it is: CVE-2022-32156 is a high-severity vulnerability in Splunk Splunk, published on 14 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-32156 in the wild and no public exploit code.\n\nAffected product: Splunk Splunk. 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-32156/ (Markdown: https://insights.sbomify.com/CVE-2022-32156/index.md)","id":"CVE-2022-32156","markdown":"https://insights.sbomify.com/CVE-2022-32156/index.md","name":"CVE-2022-32156","record":{"aliases":["GHSA-775p-gpqh-xf63"],"analysis":{"component_type":"server_software","fix_type":"configuration_change","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk Enterprise","requires_auth":"none","summary":"Attackers can intercept CLI traffic via MITM because TLS certificate validation is disabled by default, requiring manual configuration to fix.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Splunk","cpe":[{"product":"splunk","vendor":"splunk"},{"product":"universal_forwarder","vendor":"splunk"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"In Splunk Enterprise and Universal Forwarder versions before 9.0, the Splunk command-line interface (CLI) did not validate TLS certificates while connecting to a remote Splunk platform instance by default. After updating to version 9.0, see  Configure TLS host name validation for the Splunk CLI https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation#Configure_TLS_host_name_validation_for_the_Splunk_CLI  to enable the remediation. The vulnerability does not affect the Splunk Cloud Platform. At the time of publishing, we have no evidence of exploitation of this vulnerability by external parties.\n\nThe issue requires conditions beyond the control of a potential bad actor such as a machine-in-the-middle attack. Hence, Splunk rates the complexity of the attack as High.","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":"Splunk Enterprise and Universal Forwarder CLI connections lacked TLS cert validation","id":"CVE-2022-32156","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"splunk:splunk","products":["splunk:splunk","splunk:universal_forwarder"],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Splunk Enterprise deployment servers allow unauthenticated forwarder bundle downloads","id":"CVE-2022-32157"},"packages":[],"prev":{"headline":"Universal Forwarder management services allows remote login by default","id":"CVE-2022-32155"},"products":["Splunk Enterprise","Universal Forwarder"],"published":"2022-06-14","related":[{"cvss_score":9.8,"headline":"Splunk Enterprise Missing Authentication for Critical Function","id":"CVE-2026-20253","kev_date_added":"2026-06-18","published":"2026-06-10"},{"cvss_score":9.8,"headline":"Missing Authentication for Critical Function in the Patroni REST API in Splunk Enterprise","id":"CVE-2026-76268","kev_date_added":null,"published":"2026-10-07"},{"cvss_score":9.8,"headline":"Improper Neutralization in Splunk Enterprise","id":"CVE-2026-76284","kev_date_added":null,"published":"2026-10-07"},{"cvss_score":9.8,"headline":"Improper Adherence to Coding Standards in Splunk Enterprise","id":"CVE-2026-76285","kev_date_added":null,"published":"2026-10-07"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2017-17067","kev_date_added":null,"published":"2017-11-30"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2016-10126","kev_date_added":null,"published":"2017-01-10"},{"cvss_score":9.4,"headline":"Improper Access Control through Embedded Report REST API Requests in Splunk Enterprise","id":"CVE-2026-76310","kev_date_added":null,"published":"2026-08-19"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Splunk"]},"summary":"Attackers can intercept CLI traffic via MITM because TLS certificate validation is disabled by default, requiring manual configuration to fix.","url":"https://insights.sbomify.com/CVE-2022-32156/"}