{"answers":{"affected":"2 open source packages ship an affected version, including kibana. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-37939 in the wild and no public exploit code.","fix":"Upgrade kibana to 7.15.2 or later.","what":"CVE-2021-37939 is a low-severity server-side request forgery vulnerability in Elastic Kibana, published on 18 Nov 2021. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-37939 and fix it if it is affected.\n\nWhat it is: CVE-2021-37939 is a low-severity server-side request forgery vulnerability in Elastic Kibana, published on 18 Nov 2021. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-37939 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- kibana (npm): affected from 7.8.0; fixed in 7.15.2\n- kibana (npm): affected from 7.8.0; fixed in 7.15.2\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-2021-37939/ (Markdown: https://insights.sbomify.com/CVE-2021-37939/index.md)","id":"CVE-2021-37939","markdown":"https://insights.sbomify.com/CVE-2021-37939/index.md","name":"CVE-2021-37939","record":{"aliases":["GHSA-hp5f-qqrw-c8gj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Kibana data visualization","requires_auth":"high_privilege","summary":"A malicious user with connector creation privileges can exploit Kibana's JIRA and IBM Resilient connectors to view internal HTTP response data.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"kibana","vendor":"elastic"}],"cvss":{"score":2.7,"severity":"low","source":"nvd","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-319","name":"Cleartext Transmission of Sensitive Information"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"It was discovered that Kibana’s JIRA connector \u0026 IBM Resilient connector could be used to return HTTP response data on internal hosts, which may be intentionally hidden from public view. Using this vulnerability, a malicious user with the ability to create connectors, could utilize these connectors to view limited HTTP response data on hosts accessible to the cluster.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Kibana Sensitive Data Disclosure","id":"CVE-2021-37939","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"elastic:kibana","products":["elastic:kibana"],"type":"ssrf","year":"2021"},"n_packages":2,"n_references":1,"next":{"headline":"Server-side request forgery in Enterprisesearch","id":"CVE-2021-37940"},"packages":[{"ecosystem":"npm","fixed":["7.15.2"],"introduced":["7.8.0"],"last_affected":[],"package":"kibana","purl":null,"source":"GHSA-hp5f-qqrw-c8gj"},{"ecosystem":"npm","fixed":["7.15.2"],"introduced":["7.8.0"],"last_affected":[],"package":"kibana","purl":"pkg:npm/kibana","source":"GHSA-hp5f-qqrw-c8gj"}],"prev":{"headline":"Path traversal in Kibana","id":"CVE-2021-37938"},"products":["Kibana"],"published":"2021-11-18","related":[{"cvss_score":9.8,"headline":"Kibana Arbitrary Code Execution","id":"CVE-2019-7609","kev_date_added":"2022-01-10","published":"2019-03-25"},{"cvss_score":9.9,"headline":"Kibana arbitrary code execution via prototype pollution","id":"CVE-2025-25015","kev_date_added":null,"published":"2025-03-05"},{"cvss_score":9.9,"headline":"Deserialization in Kibana","id":"CVE-2024-37288","kev_date_added":null,"published":"2024-09-09"},{"cvss_score":9.9,"headline":"Code injection in Kibana","id":"CVE-2023-31415","kev_date_added":null,"published":"2023-05-04"},{"cvss_score":9.8,"headline":"Information disclosure in Kibana","id":"CVE-2018-17245","kev_date_added":null,"published":"2018-12-20"},{"cvss_score":9.8,"headline":"Code injection in Kibana","id":"CVE-2018-17246","kev_date_added":null,"published":"2018-12-20"},{"cvss_score":9.1,"headline":"Kibana arbitrary code execution via prototype pollution","id":"CVE-2025-25014","kev_date_added":null,"published":"2025-05-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"2024-08-04","vendors":["Elastic"]},"summary":"A malicious user with connector creation privileges can exploit Kibana's JIRA and IBM Resilient connectors to view internal HTTP response data.","url":"https://insights.sbomify.com/CVE-2021-37939/"}