{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-3829 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-3829 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-3829 is a medium-severity authentication bypass vulnerability in Elastic Cloud Enterprise, 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-3829 and fix it if it is affected.\n\nWhat it is: CVE-2018-3829 is a medium-severity authentication bypass vulnerability in Elastic Cloud Enterprise, 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-3829 in the wild and no public exploit code.\n\nAffected product: Elastic Cloud Enterprise. 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-2018-3829/ (Markdown: https://insights.sbomify.com/CVE-2018-3829/index.md)","id":"CVE-2018-3829","markdown":"https://insights.sbomify.com/CVE-2018-3829/index.md","name":"CVE-2018-3829","record":{"aliases":["GHSA-pc7v-g5f6-75fv"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Elastic Cloud Enterprise","requires_auth":"low_privilege","summary":"Attackers with specific host details can bypass role validation to add rogue allocators, gaining unauthorized access to cluster data.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"elastic_cloud_enterprise","vendor":"elastic"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"},{"id":"CWE-285","name":"Improper Authorization"}],"description":"In Elastic Cloud Enterprise (ECE) versions prior to 1.1.4 it was discovered that a user could scale out allocators on new hosts with an invalid roles token. An attacker with access to the previous runner ID and IP address of the coordinator-host could add a allocator to an existing ECE install to gain access to other clusters data.","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":"Auth bypass in Elastic Cloud Enterprise","id":"CVE-2018-3829","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in Kibana","id":"CVE-2018-3830"},"packages":[],"prev":{"headline":"Information disclosure in Elastic Cloud Enterprise","id":"CVE-2018-3828"},"products":["Elastic Cloud Enterprise"],"published":"2018-09-19","related":[{"cvss_score":9.1,"headline":"Elastic Cloud Enterprise (ECE) Improper Neutralization of Special Elements Used in a Template Engine","id":"CVE-2025-37729","kev_date_added":null,"published":"2025-10-13"},{"cvss_score":8.8,"headline":"Elastic Cloud Enterprise Improper Authorization","id":"CVE-2025-37736","kev_date_added":null,"published":"2025-11-07"},{"cvss_score":8.1,"headline":"Privilege escalation in Elastic Cloud Enterprise","id":"CVE-2024-37282","kev_date_added":null,"published":"2024-06-28"},{"cvss_score":7.5,"headline":"Elasticsearch uncontrolled resource consumption","id":"CVE-2023-31418","kev_date_added":null,"published":"2023-10-26"},{"cvss_score":7.5,"headline":"Information disclosure in Elastic Cloud Enterprise","id":"CVE-2018-3828","kev_date_added":null,"published":"2018-09-19"},{"cvss_score":6.5,"headline":"Information disclosure in Elastic Cloud Enterprise","id":"CVE-2022-23715","kev_date_added":null,"published":"2022-08-25"},{"cvss_score":5.9,"headline":"Hardcoded credentials in Elastic Cloud Enterprise (ECE)","id":"CVE-2018-3825","kev_date_added":null,"published":"2018-09-19"}],"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-05","vendors":["Elastic"]},"summary":"Attackers with specific host details can bypass role validation to add rogue allocators, gaining unauthorized access to cluster data.","url":"https://insights.sbomify.com/CVE-2018-3829/"}