{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-7620 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-7620 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-7620 is a high-severity denial of service vulnerability in Elastic Logstash, published on 30 Oct 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-7620 and fix it if it is affected.\n\nWhat it is: CVE-2019-7620 is a high-severity denial of service vulnerability in Elastic Logstash, published on 30 Oct 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-7620 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-7620/ (Markdown: https://insights.sbomify.com/CVE-2019-7620/index.md)","id":"CVE-2019-7620","markdown":"https://insights.sbomify.com/CVE-2019-7620/index.md","name":"CVE-2019-7620","record":{"aliases":["GHSA-77mg-86wc-vj3g"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Logstash data pipeline","requires_auth":"none","summary":"An unauthenticated attacker can cause Logstash to stop responding by sending a specially crafted network packet to the Beats input port.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"logstash","vendor":"elastic"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"Logstash versions before 7.4.1 and 6.8.4 contain a denial of service flaw in the Logstash Beats input plugin. An unauthenticated user who is able to connect to the port the Logstash beats input could send a specially crafted network packet that would cause Logstash to stop responding.","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":"Denial of service in Logstash","id":"CVE-2019-7620","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in Kibana","id":"CVE-2019-7621"},"packages":[],"prev":{"headline":"Exposure of Sensitive Information to an Unauthorized Actor in Elasticsearch","id":"CVE-2019-7619"},"products":["Logstash"],"published":"2019-10-30","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.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":"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":"An unauthenticated attacker can cause Logstash to stop responding by sending a specially crafted network packet to the Beats input port.","url":"https://insights.sbomify.com/CVE-2019-7620/"}