{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2015-5378 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-5378 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-5378 is a high-severity vulnerability in n/a, published on 27 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2015-5378 and fix it if it is affected.\n\nWhat it is: CVE-2015-5378 is a high-severity vulnerability in n/a, published on 27 Jun 2017. 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-2015-5378 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2015-5378/ (Markdown: https://insights.sbomify.com/CVE-2015-5378/index.md)","id":"CVE-2015-5378","markdown":"https://insights.sbomify.com/CVE-2015-5378/index.md","name":"CVE-2015-5378","record":{"aliases":["GHSA-g6rc-3fpq-w2gr"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Logstash server","requires_auth":"none","summary":"Remote attackers can read communications between Logstash Forwarder agents and the Logstash server, exposing sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"logstash","vendor":"elastic"},{"product":"logstash","vendor":"elasticsearch"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Logstash 1.5.x before 1.5.3 and 1.4.x before 1.4.4 allows remote attackers to read communications between Logstash Forwarder agent and Logstash server.","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":"Information disclosure in n/a","id":"CVE-2015-5378","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2015"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2015-5379"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2015-5377"},"products":["n/a"],"published":"2017-06-27","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":"Denial of service in Logstash","id":"CVE-2019-7620","kev_date_added":null,"published":"2019-10-30"},{"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-06","vendors":["n/a"]},"summary":"Remote attackers can read communications between Logstash Forwarder agents and the Logstash server, exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2015-5378/"}