Vulnerability in github.com/elastic/apm-server (CVE-2024-37286)
Summary
Vulnerability in github.com/elastic/apm-server (CVE-2024-37286). Confidential information can be exposed externally. Mitigation: upgrade to 8.14.0 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2024-37286 has been found in github.com/elastic/apm-server.
Confidential information can be exposed externally.
What to do: upgrade github.com/elastic/apm-server to 8.14.0 or later.
If unsure, ask your IT team or search "github.com/elastic/apm-server CVE-2024-37286" on the vendor's site.
CVE-2024-37286 (github.com/elastic/apm-server) — CWE-532
Attack vector: adjacent-network / no user interaction
Patched: 8.14.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-532) exists in github.com/elastic/apm-server.
Check the vendor advisory for the affected versions of github.com/elastic/apm-server.
Severity: ?. Confidential information can be exposed externally.
Update to 8.14.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/elastic/apm-server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/elastic/apm-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/elastic/apm-serverを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/elastic/apm-server to 8.14.0ステージング環境で 8.14.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web discuss.elastic.co
- web pkg.go.dev