{"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-37286 in the wild and no public exploit code.","fix":"Upgrade github.com/elastic/apm-server to 8.14.0 or later.","what":"CVE-2024-37286 is a medium-severity vulnerability in Elastic APM Server, published on 3 Aug 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-37286 and fix it if it is affected.\n\nWhat it is: CVE-2024-37286 is a medium-severity vulnerability in Elastic APM Server, published on 3 Aug 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-37286 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.14.0\n- github.com/elastic/apm-server (Go): affected all versions; fixed in 8.14.0\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-37286/ (Markdown: https://insights.sbomify.com/CVE-2024-37286/index.md)","id":"CVE-2024-37286","markdown":"https://insights.sbomify.com/CVE-2024-37286/index.md","name":"CVE-2024-37286","record":{"aliases":["GHSA-f6cj-4h3g-hwq4","GO-2024-3037"],"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 document data leaked into APM Server logs during failed bulk index requests.","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":"APM server logs contain document body from a partially failed bulk index request. For example, in case of unavailable_shards_exception for a specific document, since the ES response line contains the document body, and that APM server logs the ES response line on error, the document is effectively logged.","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-37286","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":3,"n_references":1,"next":{"headline":"Kibana arbitrary code execution via prototype pollution","id":"CVE-2024-37287"},"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-3037"},{"ecosystem":"Go","fixed":["8.14.0"],"introduced":["0"],"last_affected":[],"package":"github.com/elastic/apm-server","purl":null,"source":"GHSA-f6cj-4h3g-hwq4"},{"ecosystem":"Go","fixed":["8.14.0"],"introduced":["0"],"last_affected":[],"package":"github.com/elastic/apm-server","purl":"pkg:golang/github.com/elastic/apm-server","source":"GHSA-f6cj-4h3g-hwq4"}],"prev":{"headline":"Kibana arbitrary code execution via YAML deserialization","id":"CVE-2024-37285"},"products":["APM Server"],"published":"2024-08-03","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-23448","kev_date_added":null,"published":"2024-02-07"},{"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-09-03","vendors":["Elastic"]},"summary":"Attackers with log access can read sensitive document data leaked into APM Server logs during failed bulk index requests.","url":"https://insights.sbomify.com/CVE-2024-37286/"}