{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-20373 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-20373 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-20373 is a low-severity vulnerability in Splunk Add-on for Palo Alto Networks, published on 26 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-20373 and fix it if it is affected.\n\nWhat it is: CVE-2025-20373 is a low-severity vulnerability in Splunk Add-on for Palo Alto Networks, published on 26 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-20373 in the wild and no public exploit code.\n\nAffected product: Splunk Add-on for Palo Alto Networks. 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-20373/ (Markdown: https://insights.sbomify.com/CVE-2025-20373/index.md)","id":"CVE-2025-20373","markdown":"https://insights.sbomify.com/CVE-2025-20373/index.md","name":"CVE-2025-20373","record":{"aliases":["GHSA-hj72-63wj-r3wg"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk Add-on","requires_auth":"high_privilege","summary":"An attacker with local or admin access can read client secrets exposed in plain text in the internal index of the Splunk Add-on for Palo Alto Networks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisco","cpe":[],"cvss":{"score":2.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"In Splunk Add-on for Palo Alto Networks versions below 2.0.2, the add-on exposes client secrets in plain text in the _internal index during the addition of new “Data Security Accounts“. The vulnerability would require either local access to the log files or administrative access to internal indexes, which by default only the admin role receives. Review roles and capabilities on your instance and restrict internal index access to administrator-level roles. See [Define roles on the Splunk platform with capabilities](https://docs.splunk.com/Documentation/Splunk/latest/Security/Rolesandcapabilities) in the Splunk documentation for more information.","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":"Sensitive Information Disclosure in “_internal“ index through Splunk Add-On for Palo Alto Networks","id":"CVE-2025-20373","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Cisco Unified Contact Center Express Arbitrary File Download Vulnerability","id":"CVE-2025-20374"},"packages":[],"prev":{"headline":"Unauthenticated Blind Server Side Request Forgery (SSRF) in Splunk Enterprise","id":"CVE-2025-20371"},"products":["Splunk Add-on for Palo Alto Networks"],"published":"2025-11-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-11-26","vendors":["Splunk"]},"summary":"An attacker with local or admin access can read client secrets exposed in plain text in the internal index of the Splunk Add-on for Palo Alto Networks.","url":"https://insights.sbomify.com/CVE-2025-20373/"}