{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-7612 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-7612 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-7612 is a critical vulnerability in Elastic Logstash, published on 25 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-7612 and fix it if it is affected.\n\nWhat it is: CVE-2019-7612 is a critical vulnerability in Elastic Logstash, published on 25 Mar 2019. 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-2019-7612 in the wild and no public exploit code.\n\nAffected product: Elastic Logstash. 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-2019-7612/ (Markdown: https://insights.sbomify.com/CVE-2019-7612/index.md)","id":"CVE-2019-7612","markdown":"https://insights.sbomify.com/CVE-2019-7612/index.md","name":"CVE-2019-7612","record":{"aliases":["GHSA-76jg-hr4p-qmfv"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Logstash data pipeline","requires_auth":"none","summary":"Attackers can view sensitive credentials in logs if malformed URLs are used in Logstash configuration, requiring an upgrade to fix.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"logstash","vendor":"elastic"},{"product":"active_iq_performance_analytics_services","vendor":"netapp"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"},{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"description":"A sensitive data disclosure flaw was found in the way Logstash versions before 5.6.15 and 6.6.1 logs malformed URLs. If a malformed URL is specified as part of the Logstash configuration, the credentials for the URL could be inadvertently logged as part of the error message.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Information disclosure in Logstash","id":"CVE-2019-7612","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Winlogbeat versions before 5.6.16 and 6.6.2 had an insufficient logging flaw.","id":"CVE-2019-7613"},"packages":[],"prev":{"headline":"Improper Access Control in Elasticsearch","id":"CVE-2019-7611"},"products":["Logstash"],"published":"2019-03-25","related":[{"cvss_score":8.4,"headline":"Logstash Insertion of Sensitive Information into Log File","id":"CVE-2023-46672","kev_date_added":null,"published":"2023-11-15"},{"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":"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":"2024-08-04","vendors":["Elastic"]},"summary":"Attackers can view sensitive credentials in logs if malformed URLs are used in Logstash configuration, requiring an upgrade to fix.","url":"https://insights.sbomify.com/CVE-2019-7612/"}