{"answers":{"affected":"4 open source packages ship an affected version, including org.elasticsearch:elasticsearch. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-3831 in the wild and no public exploit code.","fix":"Upgrade org.elasticsearch:elasticsearch to a fixed version for your release line: 5.6.12 or 6.4.1.","what":"CVE-2018-3831 is a high-severity vulnerability in Elastic Elasticsearch, published on 19 Sep 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-3831 and fix it if it is affected.\n\nWhat it is: CVE-2018-3831 is a high-severity vulnerability in Elastic Elasticsearch, published on 19 Sep 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-3831 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.elasticsearch:elasticsearch (Maven): affected from 5.6.0; fixed in 5.6.12\n- org.elasticsearch:elasticsearch (Maven): affected from 5.6.0; fixed in 5.6.12\n- org.elasticsearch:elasticsearch (Maven): affected from 6.0.0; fixed in 6.4.1\n- org.elasticsearch:elasticsearch (Maven): affected from 6.0.0; fixed in 6.4.1\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-3831/ (Markdown: https://insights.sbomify.com/CVE-2018-3831/index.md)","id":"CVE-2018-3831","markdown":"https://insights.sbomify.com/CVE-2018-3831/index.md","name":"CVE-2018-3831","record":{"aliases":["GHSA-r9fv-qpm9-rj4g"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Elasticsearch search engine","requires_auth":"low_privilege","summary":"Authenticated users can view sensitive configuration secrets like passwords and tokens via the cluster settings API in Elasticsearch.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"elasticsearch","vendor":"elastic"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Elasticsearch Alerting and Monitoring in versions before 6.4.1 or 5.6.12 have an information disclosure issue when secrets are configured via the API. The Elasticsearch _cluster/settings API, when queried, could leak sensitive configuration information such as passwords, tokens, or usernames. This could allow an authenticated Elasticsearch user to improperly view these details.","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-3831","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"elastic:elasticsearch","products":["elastic:elasticsearch"],"type":"information_disclosure","year":"2018"},"n_packages":4,"n_references":2,"next":{"headline":"File upload in Insteon","id":"CVE-2018-3832"},"packages":[{"ecosystem":"Maven","fixed":["5.6.12"],"introduced":["5.6.0"],"last_affected":[],"package":"org.elasticsearch:elasticsearch","purl":null,"source":"GHSA-r9fv-qpm9-rj4g"},{"ecosystem":"Maven","fixed":["5.6.12"],"introduced":["5.6.0"],"last_affected":[],"package":"org.elasticsearch:elasticsearch","purl":"pkg:maven/org.elasticsearch/elasticsearch","source":"GHSA-r9fv-qpm9-rj4g"},{"ecosystem":"Maven","fixed":["6.4.1"],"introduced":["6.0.0"],"last_affected":[],"package":"org.elasticsearch:elasticsearch","purl":null,"source":"GHSA-r9fv-qpm9-rj4g"},{"ecosystem":"Maven","fixed":["6.4.1"],"introduced":["6.0.0"],"last_affected":[],"package":"org.elasticsearch:elasticsearch","purl":"pkg:maven/org.elasticsearch/elasticsearch","source":"GHSA-r9fv-qpm9-rj4g"}],"prev":{"headline":"Cross-site scripting in Kibana","id":"CVE-2018-3830"},"products":["Elasticsearch"],"published":"2018-09-19","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":"Authenticated users can view sensitive configuration secrets like passwords and tokens via the cluster settings API in Elasticsearch.","url":"https://insights.sbomify.com/CVE-2018-3831/"}