{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-11409 exists.","fix":"No fix has been published for CVE-2018-11409 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-11409 is a medium-severity vulnerability in Splunk Splunk, published on 8 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-11409 and fix it if it is affected.\n\nWhat it is: CVE-2018-11409 is a medium-severity vulnerability in Splunk Splunk, published on 8 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-11409 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-2018-11409/ (Markdown: https://insights.sbomify.com/CVE-2018-11409/index.md)","id":"CVE-2018-11409","markdown":"https://insights.sbomify.com/CVE-2018-11409/index.md","name":"CVE-2018-11409","record":{"aliases":["GHSA-m7vq-f4cp-vwc4"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk server","requires_auth":"none","summary":"Attackers can disclose sensitive information, such as license keys, by appending specific parameters to queries in Splunk server.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"splunk","vendor":"splunk"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Splunk through 7.0.1 allows information disclosure by appending __raw/services/server/info/server-info?output_mode=json to a query, as demonstrated by discovering a license key.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2018-06-08","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":1,"refs":[{"date":"2018-06-08","kind":"exploitdb","ref":"44865","stars":null,"title":"Splunk \u003c 7.0.1 - Information Disclosure"},{"date":"2018-06-08","kind":"metasploit","ref":"auxiliary/gather/splunk_raw_server_info","stars":null,"title":"Splunk __raw Server Info Disclosure "},{"date":null,"kind":"nuclei","ref":"http/cves/2018/CVE-2018-11409.yaml","stars":null,"title":"Splunk \u003c=7.0.1 - Information Disclosure"}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2018-11409","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"splunk:splunk","products":["splunk:splunk"],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Use after free in n/a","id":"CVE-2018-11410"},"packages":[],"prev":{"headline":"Symfony Open Redirect","id":"CVE-2018-11408"},"products":["n/a"],"published":"2018-06-08","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":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can disclose sensitive information, such as license keys, by appending specific parameters to queries in Splunk server.","url":"https://insights.sbomify.com/CVE-2018-11409/"}