{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-22164 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-22164 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-22164 is a medium-severity denial of service vulnerability in Splunk Enterprise Security (ES), published on 9 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-22164 and fix it if it is affected.\n\nWhat it is: CVE-2024-22164 is a medium-severity denial of service vulnerability in Splunk Enterprise Security (ES), published on 9 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-22164 in the wild and no public exploit code.\n\nAffected product: Splunk Enterprise Security (ES). 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-2024-22164/ (Markdown: https://insights.sbomify.com/CVE-2024-22164/index.md)","id":"CVE-2024-22164","markdown":"https://insights.sbomify.com/CVE-2024-22164/index.md","name":"CVE-2024-22164","record":{"aliases":["GHSA-5q6v-3768-8xq7"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk Enterprise Security","requires_auth":"low_privilege","summary":"An attacker can cause a denial of service in Splunk Enterprise Security investigations by sending oversized attachment requests, rendering them inaccessible.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Splunk","cpe":[{"product":"enterprise_security","vendor":"splunk"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"In Splunk Enterprise Security (ES) versions below 7.1.2, an attacker can use investigation attachments to perform a denial of service (DoS) to the Investigation. The attachment endpoint does not properly limit the size of the request which lets an attacker cause the Investigation to become inaccessible.","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":"Denial of Service of an Investigation in Splunk Enterprise Security through Investigation attachments","id":"CVE-2024-22164","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of Service in Splunk Enterprise Security of the Investigations manager through Investigation creation","id":"CVE-2024-22165"},"packages":[],"prev":{"headline":"WordPress Shield Security Plugin \u003c= 18.5.7 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2024-22163"},"products":["Splunk Enterprise Security (ES)"],"published":"2024-01-09","related":[{"cvss_score":8.1,"headline":"SPL Injection through the REST API in Splunk Enterprise Security","id":"CVE-2026-76387","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":8.1,"headline":"Privilege Escalation through Search Macro Permissions in Splunk Enterprise Security","id":"CVE-2026-76388","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":6.5,"headline":"Denial of Service in Splunk Enterprise Security of the Investigations manager through Investigation creation","id":"CVE-2024-22165","kev_date_added":null,"published":"2024-01-09"}],"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-06-03","vendors":["Splunk"]},"summary":"An attacker can cause a denial of service in Splunk Enterprise Security investigations by sending oversized attachment requests, rendering them inaccessible.","url":"https://insights.sbomify.com/CVE-2024-22164/"}