{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2025-20389 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-20389 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-20389 is a medium-severity denial of service vulnerability in Splunk Splunk, published on 3 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-20389 and fix it if it is affected.\n\nWhat it is: CVE-2025-20389 is a medium-severity denial of service vulnerability in Splunk Splunk, published on 3 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-20389 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-2025-20389/ (Markdown: https://insights.sbomify.com/CVE-2025-20389/index.md)","id":"CVE-2025-20389","markdown":"https://insights.sbomify.com/CVE-2025-20389/index.md","name":"CVE-2025-20389","record":{"aliases":["GHSA-49x5-pp3j-h44f"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk Secure Gateway","requires_auth":"low_privilege","summary":"A low-privileged user can cause a client-side denial of service in Splunk Secure Gateway by crafting a malicious payload in the label field.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisco","cpe":[{"product":"splunk","vendor":"splunk"},{"product":"splunk_cloud_platform","vendor":"splunk"},{"product":"splunk_secure_gateway","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-20","name":"Improper Input Validation"}],"description":"In Splunk Enterprise versions below 10.0.2, 9.4.6, 9.3.8, and 9.2.10, and versions below 3.9.10, 3.8.58 and 3.7.28 of the Splunk Secure Gateway app on Splunk Cloud Platform, a low-privileged user that does not hold the \"admin\" or \"power\" Splunk roles could craft a malicious payload through the `label` column field after adding a new device in the Splunk Secure Gateway app. This could potentially lead to a client-side denial of service (DoS).","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":"Improper Input Validation in \"label\" column field in Splunk Secure Gateway App","id":"CVE-2025-20389","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"splunk:splunk","products":["splunk:splunk","splunk:splunk_cloud_platform"],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Cisco Multiple Products Improper Input Validation","id":"CVE-2025-20393"},"packages":[],"prev":{"headline":"Blind Server Side Request Forgery (SSRF) through Distributed Search Peers in Splunk Enterprise","id":"CVE-2025-20388"},"products":["Splunk Cloud Platform","Splunk Enterprise","Splunk Secure Gateway"],"published":"2025-12-03","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-03","vendors":["Splunk"]},"summary":"A low-privileged user can cause a client-side denial of service in Splunk Secure Gateway by crafting a malicious payload in the label field.","url":"https://insights.sbomify.com/CVE-2025-20389/"}