{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-49923 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-49923 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-49923 is a medium-severity vulnerability in Elastic Enterprise Search, 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-49923 and fix it if it is affected.\n\nWhat it is: CVE-2023-49923 is a medium-severity vulnerability in Elastic Enterprise Search, 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-49923 in the wild and no public exploit code.\n\nAffected product: Elastic Enterprise Search. 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-49923/ (Markdown: https://insights.sbomify.com/CVE-2023-49923/index.md)","id":"CVE-2023-49923","markdown":"https://insights.sbomify.com/CVE-2023-49923/index.md","name":"CVE-2023-49923","record":{"aliases":["GHSA-q3p5-xqf4-5mgf"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Elastic Enterprise Search","requires_auth":"low_privilege","summary":"Attackers with log access can read sensitive data from indexed documents logged at INFO level in Elastic Enterprise Search.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"enterprise_search","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 the Documents API of App Search logged the raw contents of indexed documents at INFO log level. Depending on the contents of such documents, this could lead to the insertion of sensitive or private information in the App Search logs. Elastic has released 8.11.2 and 7.17.16 that resolves this issue by changing the log level at which these are logged to DEBUG, 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":null,"headline":"Enterprise Search Insertion of Sensitive Information into Log File","id":"CVE-2023-49923","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":"Cross-site scripting in n/a","id":"CVE-2023-49926"},"packages":[],"prev":{"headline":"Beats Insertion of Sensitive Information into Log File","id":"CVE-2023-49922"},"products":["Enterprise Search"],"published":"2023-12-12","related":[{"cvss_score":8.8,"headline":"Missing authorization in Elastic Enterprise Search","id":"CVE-2021-22148","kev_date_added":null,"published":"2021-09-15"},{"cvss_score":8.8,"headline":"Missing authorization in Elastic Enterprise Search","id":"CVE-2021-22149","kev_date_added":null,"published":"2021-09-15"},{"cvss_score":8.8,"headline":"Privilege escalation in Elastic Enterprise Search","id":"CVE-2020-7018","kev_date_added":null,"published":"2020-08-18"},{"cvss_score":6.8,"headline":"Server-side request forgery in Enterprisesearch","id":"CVE-2021-37940","kev_date_added":null,"published":"2021-12-07"}],"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":"2025-05-24","vendors":["Elastic"]},"summary":"Attackers with log access can read sensitive data from indexed documents logged at INFO level in Elastic Enterprise Search.","url":"https://insights.sbomify.com/CVE-2023-49923/"}