{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-3827 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-3827 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-3827 is a high-severity vulnerability in Elasticsearch, 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-3827 and fix it if it is affected.\n\nWhat it is: CVE-2018-3827 is a high-severity vulnerability in Elasticsearch, 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-3827 in the wild and no public exploit code.\n\nAffected product: 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-2018-3827/ (Markdown: https://insights.sbomify.com/CVE-2018-3827/index.md)","id":"CVE-2018-3827","markdown":"https://insights.sbomify.com/CVE-2018-3827/index.md","name":"CVE-2018-3827","record":{"aliases":["GHSA-xc6w-7c69-3cf8"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Elasticsearch Azure plugin","requires_auth":"none","summary":"Azure credentials may be exposed in logs when the Elasticsearch repository-azure plugin is configured to log at TRACE level.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"azure_repository","vendor":"elastic"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"A sensitive data disclosure flaw was found in the Elasticsearch repository-azure (formerly elasticsearch-cloud-azure) plugin. When the repository-azure plugin is set to log at TRACE level Azure credentials can be inadvertently logged.","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":"Information disclosure in Elasticsearch","id":"CVE-2018-3827","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Elastic Cloud Enterprise","id":"CVE-2018-3828"},"packages":[],"prev":{"headline":"Information disclosure in Elasticsearch","id":"CVE-2018-3826"},"products":["Elasticsearch"],"published":"2018-09-19","related":[],"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":"Azure credentials may be exposed in logs when the Elasticsearch repository-azure plugin is configured to log at TRACE level.","url":"https://insights.sbomify.com/CVE-2018-3827/"}