{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-37439 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-37439 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-37439 is a medium-severity denial of service vulnerability in Splunk Splunk, published on 16 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-37439 and fix it if it is affected.\n\nWhat it is: CVE-2022-37439 is a medium-severity denial of service vulnerability in Splunk Splunk, published on 16 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-37439 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-37439/ (Markdown: https://insights.sbomify.com/CVE-2022-37439/index.md)","id":"CVE-2022-37439","markdown":"https://insights.sbomify.com/CVE-2022-37439/index.md","name":"CVE-2022-37439","record":{"aliases":["GHSA-mg48-gp9q-6j63"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Splunk Enterprise","requires_auth":"low_privilege","summary":"Attackers can crash Splunk Enterprise and Universal Forwarders by indexing a malformed ZIP file, requiring manual intervention to restore service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Splunk","cpe":[{"product":"splunk","vendor":"splunk"},{"product":"universal_forwarder","vendor":"splunk"}],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-409","name":"Improper Handling of Highly Compressed Data (Data Amplification)"}],"description":"In Splunk Enterprise and Universal Forwarder versions in the following table, indexing a specially crafted ZIP file using the file monitoring input can result in a crash of the application. Attempts to restart the application would result in a crash and would require manually removing the malformed file.","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":"Malformed ZIP file crashes Universal Forwarders and Splunk Enterprise through file monitoring input","id":"CVE-2022-37439","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"splunk:splunk","products":["splunk:splunk","splunk:universal_forwarder"],"type":"denial_of_service","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2022-37440"},"packages":[],"prev":{"headline":"Information disclosure via the dashboard drilldown in Splunk Enterprise","id":"CVE-2022-37438"},"products":["Splunk Enterprise","Universal Forwarders"],"published":"2022-08-16","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-09-16","vendors":["Splunk"]},"summary":"Attackers can crash Splunk Enterprise and Universal Forwarders by indexing a malformed ZIP file, requiring manual intervention to restore service.","url":"https://insights.sbomify.com/CVE-2022-37439/"}