{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-6687 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-6687 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-6687 is a medium-severity vulnerability in Elastic Agent, published on 12 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-6687 and fix it if it is affected.\n\nWhat it is: CVE-2023-6687 is a medium-severity vulnerability in Elastic Agent, published on 12 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-6687 in the wild and no public exploit code.\n\nAffected product: Elastic Agent. 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-2023-6687/ (Markdown: https://insights.sbomify.com/CVE-2023-6687/index.md)","id":"CVE-2023-6687","markdown":"https://insights.sbomify.com/CVE-2023-6687/index.md","name":"CVE-2023-6687","record":{"aliases":["GHSA-xqc7-q7jr-cg3w"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Elastic Agent","requires_auth":"low_privilege","summary":"Elastic Agent logs sensitive data when ingestion fails, allowing attackers with log access to view private information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"elastic_agent","vendor":"elastic"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"An issue was discovered by Elastic whereby Elastic Agent would log a raw event in its own logs at the WARN or ERROR level if ingesting that event to Elasticsearch failed with any 4xx HTTP status code except 409 or 429. Depending on the nature of the event that Elastic Agent attempted to ingest, this could lead to the insertion of sensitive or private information in the Elastic Agent logs. Elastic has released 8.11.3 and 7.17.16 that prevents this issue by limiting these types of logs to DEBUG level logging, which is disabled by default.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Elastic Agent Insertion of Sensitive Information into Log File","id":"CVE-2023-6687","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Inefficient Regular Expression Complexity in GitLab","id":"CVE-2023-6688"},"packages":[],"prev":{"headline":"Ibtana – WordPress Website Builder \u003c= 1.2.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode","id":"CVE-2023-6684"},"products":["Elastic Agent"],"published":"2023-12-12","related":[{"cvss_score":7.8,"headline":"Incorrect Permission Assignment for Critical Resource in Elastic Agent Leading to Local Privilege Escalation to SYSTEM","id":"CVE-2026-78604","kev_date_added":null,"published":"2026-09-02"},{"cvss_score":6.5,"headline":"Elastic Agent Insertion of Sensitive Information into Log File","id":"CVE-2024-37283","kev_date_added":null,"published":"2024-08-08"},{"cvss_score":6.2,"headline":"Elastic Agent / Elastic Endpoint Security local API key disclosure","id":"CVE-2023-46669","kev_date_added":null,"published":"2025-05-01"},{"cvss_score":4.4,"headline":"Elastic Agent Inclusion of Functionality from Untrusted Control Sphere","id":"CVE-2024-52976","kev_date_added":null,"published":"2025-05-01"}],"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-02","vendors":["Elastic"]},"summary":"Elastic Agent logs sensitive data when ingestion fails, allowing attackers with log access to view private information.","url":"https://insights.sbomify.com/CVE-2023-6687/"}