{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-46668 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-46668 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-46668 is a medium-severity vulnerability in Elastic Endpoint, published on 25 Oct 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-46668 and fix it if it is affected.\n\nWhat it is: CVE-2023-46668 is a medium-severity vulnerability in Elastic Endpoint, published on 25 Oct 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-46668 in the wild and no public exploit code.\n\nAffected product: Elastic Endpoint. 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-46668/ (Markdown: https://insights.sbomify.com/CVE-2023-46668/index.md)","id":"CVE-2023-46668","markdown":"https://insights.sbomify.com/CVE-2023-46668/index.md","name":"CVE-2023-46668","record":{"aliases":["GHSA-59qp-8h5f-h6h4"],"analysis":{"component_type":"server_software","fix_type":"configuration_change","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Elastic Endpoint","requires_auth":"low_privilege","summary":"Attackers can read sensitive API keys from logs if debug logging is enabled, allowing unauthorized data access and modification.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"endpoint","vendor":"elastic"}],"cvss":{"score":4.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"If Elastic Endpoint (v7.9.0 - v8.10.3) is configured to use a non-default option in which the logging level is explicitly set to debug, and when Elastic Agent is simultaneously configured to collect and send those logs to Elasticsearch, then Elastic Agent API keys can be viewed in Elasticsearch in plaintext. These API keys could be used to write arbitrary data and read Elastic Endpoint user artifacts.","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":"Elastic Endpoint Insertion of Sensitive Information into Log File","id":"CVE-2023-46668","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Elastic Agent / Elastic Endpoint Security local API key disclosure","id":"CVE-2023-46669"},"packages":[],"prev":{"headline":"Fleet Server Insertion of Sensitive Information into Log File","id":"CVE-2023-46667"},"products":["Endpoint"],"published":"2023-10-25","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-09","vendors":["Elastic"]},"summary":"Attackers can read sensitive API keys from logs if debug logging is enabled, allowing unauthorized data access and modification.","url":"https://insights.sbomify.com/CVE-2023-46668/"}