{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-5377 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-5377 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-5377 is a critical code injection vulnerability in Elastic Elasticsearch, published on 6 Mar 2018. 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-5377 and fix it if it is affected.\n\nWhat it is: CVE-2015-5377 is a critical code injection vulnerability in Elastic Elasticsearch, published on 6 Mar 2018. 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-5377 in the wild and no public exploit code.\n\nAffected product: Elastic Elasticsearch. 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-5377/ (Markdown: https://insights.sbomify.com/CVE-2015-5377/index.md)","id":"CVE-2015-5377","markdown":"https://insights.sbomify.com/CVE-2015-5377/index.md","name":"CVE-2015-5377","record":{"aliases":["GHSA-vwpr-g44g-2pf3"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Elasticsearch search engine","requires_auth":"none","summary":"Remote attackers can execute arbitrary code on Elasticsearch servers via the transport protocol, requiring immediate upgrades.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"elasticsearch","vendor":"elastic"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"Elasticsearch before 1.6.1 allows remote attackers to execute arbitrary code via unspecified vectors involving the transport protocol.  NOTE: ZDI appears to claim that CVE-2015-3253 and CVE-2015-5377 are the same vulnerability","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2020-12-28","github_poc":1,"max_poc_stars":3,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-12-28T21:30:22Z","kind":"github_poc","ref":"https://github.com/fi3ro/CVE-2015-5377","stars":3,"title":"Java deserialization exploit for elasticsearch 1.5.2 CVE-2015-5377"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2015-5377","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"elastic:elasticsearch","products":["elastic:elasticsearch"],"type":"code_injection","year":"2015"},"n_packages":0,"n_references":4,"next":{"headline":"Information disclosure in n/a","id":"CVE-2015-5378"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2015-5376"},"products":["n/a"],"published":"2018-03-06","related":[{"cvss_score":9.8,"headline":"Elasticsearch Groovy Scripting Engine Remote Code Execution","id":"CVE-2015-1427","kev_date_added":"2022-03-25","published":"2015-02-17"},{"cvss_score":8.1,"headline":"Elasticsearch Remote Code Execution","id":"CVE-2014-3120","kev_date_added":"2022-03-25","published":"2014-07-28"},{"cvss_score":8.8,"headline":"Deserialization of Untrusted Data in Elasticsearch Leading to Remote Code Execution","id":"CVE-2026-72649","kev_date_added":null,"published":"2026-09-01"},{"cvss_score":8.8,"headline":"Use of Out-of-range Pointer Offset in the Elasticsearch Machine Learning Native Inference Process","id":"CVE-2026-72642","kev_date_added":null,"published":"2026-08-13"},{"cvss_score":8.8,"headline":"Privilege Escalation Flaw in Elasticsearch","id":"CVE-2020-7014","kev_date_added":null,"published":"2020-06-03"},{"cvss_score":8.8,"headline":"Improper Privilege Management in Elasticsearch","id":"CVE-2020-7009","kev_date_added":null,"published":"2020-03-31"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code on Elasticsearch servers via the transport protocol, requiring immediate upgrades.","url":"https://insights.sbomify.com/CVE-2015-5377/"}