{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-46667 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-46667 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-46667 is a high-severity vulnerability in Elastic Fleet Server, published on 26 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-46667 and fix it if it is affected.\n\nWhat it is: CVE-2023-46667 is a high-severity vulnerability in Elastic Fleet Server, published on 26 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-46667 in the wild and no public exploit code.\n\nAffected product: Elastic Fleet Server. 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-46667/ (Markdown: https://insights.sbomify.com/CVE-2023-46667/index.md)","id":"CVE-2023-46667","markdown":"https://insights.sbomify.com/CVE-2023-46667/index.md","name":"CVE-2023-46667","record":{"aliases":["GHSA-wv9p-64pj-gq2g"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Elastic Fleet Server","requires_auth":"low_privilege","summary":"Attackers can read enrollment tokens from logs to enroll agents and access sensitive secrets or inject arbitrary events.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"fleet_server","vendor":"elastic"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"An issue was discovered in Fleet Server \u003e= v8.10.0 and \u003c v8.10.3 where Agent enrolment tokens are being inserted into the Fleet Server’s log file in plain text. These enrolment tokens could allow someone to enrol an agent into an agent policy, and potentially use that to retrieve other secrets in the policy including for Elasticsearch and third-party services. Alternatively a threat actor could potentially enrol agents to the clusters and send arbitrary events to Elasticsearch.","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":"Fleet Server Insertion of Sensitive Information into Log File","id":"CVE-2023-46667","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 Endpoint Insertion of Sensitive Information into Log File","id":"CVE-2023-46668"},"packages":[],"prev":{"headline":"Elastic Sharepoint Online Python Connector Improper Access Control","id":"CVE-2023-46666"},"products":["Fleet Server"],"published":"2023-10-26","related":[{"cvss_score":6.5,"headline":"Authorization Bypass Through User-Controlled Key in Fleet Server Leading to Information Disclosure","id":"CVE-2026-72657","kev_date_added":null,"published":"2026-08-13"},{"cvss_score":6.5,"headline":"Allocation of Resources Without Limits or Throttling in Fleet Server Leading to Denial of Service","id":"CVE-2026-56150","kev_date_added":null,"published":"2026-07-01"},{"cvss_score":3.1,"headline":"Incorrect Authorization in Fleet Server Leading to Denial of Service of Agent Upload Operations","id":"CVE-2026-78587","kev_date_added":null,"published":"2026-09-02"}],"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":"total"},"state":"PUBLISHED","updated":"2024-09-09","vendors":["Elastic"]},"summary":"Attackers can read enrollment tokens from logs to enroll agents and access sensitive secrets or inject arbitrary events.","url":"https://insights.sbomify.com/CVE-2023-46667/"}