{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-3825 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-3825 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-3825 is a medium-severity vulnerability in Elastic Cloud Enterprise (ECE), published on 19 Sep 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-2018-3825 and fix it if it is affected.\n\nWhat it is: CVE-2018-3825 is a medium-severity vulnerability in Elastic Cloud Enterprise (ECE), published on 19 Sep 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-2018-3825 in the wild and no public exploit code.\n\nAffected product: Elastic Cloud Enterprise (ECE). 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-3825/ (Markdown: https://insights.sbomify.com/CVE-2018-3825/index.md)","id":"CVE-2018-3825","markdown":"https://insights.sbomify.com/CVE-2018-3825/index.md","name":"CVE-2018-3825","record":{"aliases":["GHSA-4xqm-vfvr-257f"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Elastic Cloud Enterprise","requires_auth":"none","summary":"Attackers can access tenant configuration data via ZooKeeper due to a predictable default master encryption key in Elastic Cloud Enterprise.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"elastic_cloud_enterprise","vendor":"elastic"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-1188","name":"Initialization of a Resource with an Insecure Default"},{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"}],"description":"In Elastic Cloud Enterprise (ECE) versions prior to 1.1.4 a default master encryption key is used in the process of granting ZooKeeper access to Elasticsearch clusters. Unless explicitly overwritten, this master key is predictable across all ECE deployments. If an attacker can connect to ZooKeeper directly they would be able to access configuration information of other tenants if their cluster ID is known.","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":"Hardcoded credentials in Elastic Cloud Enterprise (ECE)","id":"CVE-2018-3825","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Elasticsearch","id":"CVE-2018-3826"},"packages":[],"prev":{"headline":"Elasticsearch subject to cross site scripting","id":"CVE-2018-3824"},"products":["Elastic Cloud Enterprise (ECE)"],"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"}],"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 can access tenant configuration data via ZooKeeper due to a predictable default master encryption key in Elastic Cloud Enterprise.","url":"https://insights.sbomify.com/CVE-2018-3825/"}