{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2023-22943 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-22943 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-22943 is a medium-severity vulnerability in Splunk Add-on Builder, published on 14 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-22943 and fix it if it is affected.\n\nWhat it is: CVE-2023-22943 is a medium-severity vulnerability in Splunk Add-on Builder, published on 14 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-22943 in the wild and no public exploit code.\n\nAffected product: Splunk Add-on Builder. 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-2023-22943/ (Markdown: https://insights.sbomify.com/CVE-2023-22943/index.md)","id":"CVE-2023-22943","markdown":"https://insights.sbomify.com/CVE-2023-22943/index.md","name":"CVE-2023-22943","record":{"aliases":["GHSA-jjqg-fqrm-g2vj"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk Add-on Builder","requires_auth":"none","summary":"Attackers can intercept traffic because the application falls back to insecure HTTP after HTTPS certificate validation fails in Splunk Add-on Builder and CloudConnect SDK.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Splunk","cpe":[{"product":"add-on_builder","vendor":"splunk"},{"product":"cloudconnect_software_development_kit","vendor":"splunk"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"},{"id":"CWE-636","name":"Not Failing Securely"}],"description":"In Splunk Add-on Builder (AoB) versions below 4.1.2 and the Splunk CloudConnect SDK versions below 3.1.3, requests to third-party APIs through the REST API Modular Input incorrectly revert to using HTTP to connect after a failure to connect over HTTPS occurs.","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":"Security feature bypass in Splunk Add-on Builder","id":"CVE-2023-22943","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"** REJECT ** DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2023-22944"},"packages":[],"prev":{"headline":"Cross-Site Request Forgery in the ‘ssg/kvstore_client’ REST Endpoint in Splunk Enterprise","id":"CVE-2023-22942"},"products":["Splunk Add-on Builder","Splunk CloudConnect SDK"],"published":"2023-02-14","related":[{"cvss_score":8.8,"headline":"Session Token Disclosure to Internal Log Files in Splunk Add-on Builder","id":"CVE-2023-46231","kev_date_added":null,"published":"2024-01-30"},{"cvss_score":8.2,"headline":"Sensitive Information Disclosure to Internal Log Files in Splunk Add-on Builder","id":"CVE-2023-46230","kev_date_added":null,"published":"2024-01-30"}],"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":"2025-02-28","vendors":["Splunk"]},"summary":"Attackers can intercept traffic because the application falls back to insecure HTTP after HTTPS certificate validation fails in Splunk Add-on Builder and CloudConnect SDK.","url":"https://insights.sbomify.com/CVE-2023-22943/"}