{"answers":{"affected":"2 open source packages ship an affected version, including org.elasticsearch:elasticsearch. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-17244 in the wild and no public exploit code.","fix":"Upgrade org.elasticsearch:elasticsearch to 6.4.3 or later.","what":"CVE-2018-17244 is a medium-severity vulnerability in Elastic Elasticsearch, published on 20 Dec 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-17244 and fix it if it is affected.\n\nWhat it is: CVE-2018-17244 is a medium-severity vulnerability in Elastic Elasticsearch, published on 20 Dec 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-17244 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.elasticsearch:elasticsearch (Maven): affected from 6.4.0; fixed in 6.4.3\n- org.elasticsearch:elasticsearch (Maven): affected from 6.4.0; fixed in 6.4.3\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-2018-17244/ (Markdown: https://insights.sbomify.com/CVE-2018-17244/index.md)","id":"CVE-2018-17244","markdown":"https://insights.sbomify.com/CVE-2018-17244/index.md","name":"CVE-2018-17244","record":{"aliases":["GHSA-vpqm-88c4-x4cv"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Elasticsearch security","requires_auth":"low_privilege","summary":"Concurrent authentication requests may leak headers, allowing users to access unauthorized data or run as incorrect users in Elasticsearch.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"elasticsearch","vendor":"elastic"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/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"},{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"Elasticsearch Security versions 6.4.0 to 6.4.2 contain an error in the way request headers are applied to requests when using the Active Directory, LDAP, Native, or File realms. A request may receive headers intended for another request if the same username is being authenticated concurrently; when used with run as, this can result in the request running as the incorrect user. This could allow a user to access information that they should not have access to.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Exposure of Sensitive Information to an Unauthorized Actor in Elasticsearch","id":"CVE-2018-17244","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"elastic:elasticsearch","products":["elastic:elasticsearch"],"type":"race_condition","year":"2018"},"n_packages":2,"n_references":3,"next":{"headline":"Information disclosure in Kibana","id":"CVE-2018-17245"},"packages":[{"ecosystem":"Maven","fixed":["6.4.3"],"introduced":["6.4.0"],"last_affected":[],"package":"org.elasticsearch:elasticsearch","purl":null,"source":"GHSA-vpqm-88c4-x4cv"},{"ecosystem":"Maven","fixed":["6.4.3"],"introduced":["6.4.0"],"last_affected":[],"package":"org.elasticsearch:elasticsearch","purl":"pkg:maven/org.elasticsearch/elasticsearch","source":"GHSA-vpqm-88c4-x4cv"}],"prev":{"headline":"SQL injection in n/a","id":"CVE-2018-17243"},"products":["Elasticsearch"],"published":"2018-12-20","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":9.8,"headline":"Code injection in n/a","id":"CVE-2015-5377","kev_date_added":null,"published":"2018-03-06"},{"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":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-05","vendors":["Elastic"]},"summary":"Concurrent authentication requests may leak headers, allowing users to access unauthorized data or run as incorrect users in Elasticsearch.","url":"https://insights.sbomify.com/CVE-2018-17244/"}