{"answers":{"affected":"3 open source packages ship an affected version, including github.com/elastic/apm-server. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-23448 in the wild and no public exploit code.","fix":"Upgrade github.com/elastic/apm-server to 8.12.1 or later.","what":"CVE-2024-23448 is a medium-severity vulnerability in Elastic APM Server, published on 7 Feb 2024. 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-2024-23448 and fix it if it is affected.\n\nWhat it is: CVE-2024-23448 is a medium-severity vulnerability in Elastic APM Server, published on 7 Feb 2024. 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-2024-23448 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/elastic/apm-server (Go): affected all versions; no fix listed\n- github.com/elastic/apm-server (Go): affected all versions; fixed in 8.12.1\n- github.com/elastic/apm-server (Go): affected all versions; fixed in 8.12.1\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-2024-23448/ (Markdown: https://insights.sbomify.com/CVE-2024-23448/index.md)","id":"CVE-2024-23448","markdown":"https://insights.sbomify.com/CVE-2024-23448/index.md","name":"CVE-2024-23448","record":{"aliases":["GHSA-8r33-q5j5-rh7g","GO-2024-2556"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Elastic APM Server","requires_auth":"low_privilege","summary":"Attackers with log access can read sensitive data leaked into APM Server logs when Elasticsearch indexing fails.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"apm_server","vendor":"elastic"}],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/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 whereby APM Server could log at ERROR level, a response from Elasticsearch indicating that indexing the document failed and that response would contain parts of the original document. Depending on the nature of the document that the APM Server attempted to ingest, this could lead to the insertion of sensitive or private information in the APM Server logs.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"APM Server Insertion of Sensitive Information into Log File","id":"CVE-2024-23448","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":3,"n_references":2,"next":{"headline":"Elasticsearch Uncaught Exception","id":"CVE-2024-23449"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"github.com/elastic/apm-server","purl":"pkg:golang/github.com/elastic/apm-server","source":"GO-2024-2556"},{"ecosystem":"Go","fixed":["8.12.1"],"introduced":["0"],"last_affected":[],"package":"github.com/elastic/apm-server","purl":null,"source":"GHSA-8r33-q5j5-rh7g"},{"ecosystem":"Go","fixed":["8.12.1"],"introduced":["0"],"last_affected":[],"package":"github.com/elastic/apm-server","purl":"pkg:golang/github.com/elastic/apm-server","source":"GHSA-8r33-q5j5-rh7g"}],"prev":{"headline":"Elastic Network Drive Connector Improper Access Control","id":"CVE-2024-23447"},"products":["APM Server"],"published":"2024-02-07","related":[{"cvss_score":5.9,"headline":"Beats, Elastic Agent, APM Server, and Fleet Server Improper Certificate Validation issue","id":"CVE-2023-31421","kev_date_added":null,"published":"2023-10-26"},{"cvss_score":5.7,"headline":"APM Server Insertion of Sensitive Information into Log File","id":"CVE-2024-37286","kev_date_added":null,"published":"2024-08-03"},{"cvss_score":4.9,"headline":"Improper Handling of Highly Compressed Data in APM Server Leading to Persistent Denial of Service","id":"CVE-2026-78594","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":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"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-08-01","vendors":["Elastic"]},"summary":"Attackers with log access can read sensitive data leaked into APM Server logs when Elasticsearch indexing fails.","url":"https://insights.sbomify.com/CVE-2024-23448/"}