{"answers":{"affected":"1 open source package ship an affected version, including logstash. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-46672 in the wild and no public exploit code.","fix":"Upgrade logstash to a fixed version for your release line: 7.12.2 or 8.11.1.","what":"CVE-2023-46672 is a high-severity vulnerability in Elastic Logstash, published on 15 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-46672 and fix it if it is affected.\n\nWhat it is: CVE-2023-46672 is a high-severity vulnerability in Elastic Logstash, published on 15 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-46672 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- logstash (Bitnami): affected from 7.12.1; fixed in 7.12.2, 8.11.1\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-46672/ (Markdown: https://insights.sbomify.com/CVE-2023-46672/index.md)","id":"CVE-2023-46672","markdown":"https://insights.sbomify.com/CVE-2023-46672/index.md","name":"CVE-2023-46672","record":{"aliases":["BIT-logstash-2023-46672","GHSA-r6fg-prgw-3ff5"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Logstash data pipeline","requires_auth":"low_privilege","summary":"Attackers with log access can read sensitive keystore data if Logstash uses non-default JSON logging.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"logstash","vendor":"elastic"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"An issue was identified by Elastic whereby sensitive information is recorded in Logstash logs under specific circumstances.\n\nThe prerequisites for the manifestation of this issue are:\n\n  *  Logstash  is configured to log in JSON format https://www.elastic.co/guide/en/logstash/current/running-logstash-command-line.html , which is not the default logging format.\n\n  *  Sensitive data is stored in the Logstash keystore and referenced as a variable in Logstash configuration.","ecosystems":["Bitnami"],"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":"Logstash Insertion of Sensitive Information into Log File","id":"CVE-2023-46672","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":1,"n_references":4,"next":{"headline":"Elasticsearch Improper Handling of Exceptional Conditions","id":"CVE-2023-46673"},"packages":[{"ecosystem":"Bitnami","fixed":["7.12.2","8.11.1"],"introduced":["7.12.1","8.10.0"],"last_affected":[],"package":"logstash","purl":"pkg:bitnami/logstash","source":"BIT-logstash-2023-46672"}],"prev":{"headline":"Kibana Insertion of Sensitive Information into Log File","id":"CVE-2023-46671"},"products":["Logstash"],"published":"2023-11-15","related":[{"cvss_score":9.8,"headline":"Information disclosure in Logstash","id":"CVE-2019-7612","kev_date_added":null,"published":"2019-03-25"},{"cvss_score":8.1,"headline":"Improper Limitation of a Pathname to a Restricted Directory in Logstash Leading to Arbitrary File Write","id":"CVE-2026-33466","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":7.5,"headline":"Denial of service in Logstash","id":"CVE-2019-7620","kev_date_added":null,"published":"2019-10-30"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2015-5378","kev_date_added":null,"published":"2017-06-27"},{"cvss_score":7.5,"headline":"Logstash Logs Sensitive Information","id":"CVE-2016-1000221","kev_date_added":null,"published":"2017-06-16"},{"cvss_score":7.5,"headline":"Other in n/a","id":"CVE-2016-1000222","kev_date_added":null,"published":"2017-06-16"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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-13","vendors":["Elastic"]},"summary":"Attackers with log access can read sensitive keystore data if Logstash uses non-default JSON logging.","url":"https://insights.sbomify.com/CVE-2023-46672/"}