{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-7613 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-7613 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-7613 is a high-severity vulnerability in Elastic Logstash, published on 25 Mar 2019."},"fix_prompt":"Check this codebase for CVE-2019-7613 and fix it if it is affected.\n\nWhat it is: CVE-2019-7613 is a high-severity vulnerability in Elastic Logstash, published on 25 Mar 2019. \nExploitation: There is no known exploitation of CVE-2019-7613 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-7613/ (Markdown: https://insights.sbomify.com/CVE-2019-7613/index.md)","id":"CVE-2019-7613","markdown":"https://insights.sbomify.com/CVE-2019-7613/index.md","name":"CVE-2019-7613","record":{"aliases":["GHSA-2mc6-hfwx-q7vw"],"analysis":null,"analysis_generated_by":null,"assigner":"elastic","cpe":[{"product":"winlogbeat","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:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-778","name":"Insufficient Logging"}],"description":"Winlogbeat versions before 5.6.16 and 6.6.2 had an insufficient logging flaw. An attacker able to inject certain characters into a log entry could prevent Winlogbeat from recording the event.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Winlogbeat versions before 5.6.16 and 6.6.2 had an insufficient logging flaw.","id":"CVE-2019-7613","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Concurrent Execution using Shared Resource with Improper Synchronization in Elasticsearch","id":"CVE-2019-7614"},"packages":[],"prev":{"headline":"Information disclosure in Logstash","id":"CVE-2019-7612"},"products":["Logstash"],"published":"2019-03-25","related":[{"cvss_score":7.2,"headline":"Path traversal in Elastic Security","id":"CVE-2024-14047","kev_date_added":null,"published":"2026-09-01"}],"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":null,"url":"https://insights.sbomify.com/CVE-2019-7613/"}