{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-43571 exists.","fix":"No fix has been published for CVE-2022-43571 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-43571 is a high-severity code injection vulnerability in Splunk Splunk, published on 3 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-43571 and fix it if it is affected.\n\nWhat it is: CVE-2022-43571 is a high-severity code injection vulnerability in Splunk Splunk, published on 3 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-43571 exists.\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-43571/ (Markdown: https://insights.sbomify.com/CVE-2022-43571/index.md)","id":"CVE-2022-43571","markdown":"https://insights.sbomify.com/CVE-2022-43571/index.md","name":"CVE-2022-43571","record":{"aliases":["GHSA-fw8h-qc74-r2c2"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk Enterprise","requires_auth":"low_privilege","summary":"An authenticated user can execute arbitrary code via the dashboard PDF generation component in Splunk Enterprise.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Splunk","cpe":[{"product":"splunk","vendor":"splunk"},{"product":"splunk_cloud_platform","vendor":"splunk"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"In Splunk Enterprise versions below 8.2.9, 8.1.12, and 9.0.2, an authenticated user can execute arbitrary code through the dashboard PDF generation component.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2022-11-02","github_poc":1,"max_poc_stars":0,"metasploit":1,"nuclei":0,"refs":[{"date":"2022-11-02","kind":"metasploit","ref":"exploit/multi/http/splunk_auth_rce_cve_2022_43571","stars":null,"title":"Authenticated RCE in Splunk (SimpleXML dashboard PDF generation)"},{"date":"2022-12-27T08:00:44Z","kind":"github_poc","ref":"https://github.com/ohnonoyesyes/CVE-2022-43571","stars":0,"title":null}],"tier":"weaponised"},"has_fix":null,"headline":"Remote Code Execution through dashboard PDF generation component in Splunk Enterprise","id":"CVE-2022-43571","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"splunk:splunk","products":["splunk:splunk","splunk:splunk_cloud_platform"],"type":"code_injection","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Indexing blockage via malformed data sent through S2S or HEC protocols in Splunk Enterprise","id":"CVE-2022-43572"},"packages":[],"prev":{"headline":"XML External Entity Injection through a custom View in Splunk Enterprise","id":"CVE-2022-43570"},"products":["Splunk Enterprise"],"published":"2022-11-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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-02","vendors":["Splunk"]},"summary":"An authenticated user can execute arbitrary code via the dashboard PDF generation component in Splunk Enterprise.","url":"https://insights.sbomify.com/CVE-2022-43571/"}