← Back
CVE-2024-32474
Vulnerability in sentry (CVE-2024-32474)
Summary
vulnerability in sentry (CVE-2024-32474). Confidential information can be exposed externally. Exploitable via ``INFO``. Mitigation: upgrade to `24.4.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-32474** has been found in sentry.
Attackers can target a specific entry point like ``INFO`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade sentry to **24.4.1** or later.
If unsure, ask your IT team or search "sentry CVE-2024-32474" on the vendor's site.
CVE-2024-32474 (sentry) — CWE-117 /
Attack vector: remote (network-reachable)
Attack surface: `INFO` / `WARNING`
Patched: `24.4.1` — apply immediately
Workaround: Users can configure the logging level to exclude logs of the `INFO` level and only generate logs for levels at `WARNING` or higher.
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.
❓ What is the problem
**A vulnerability** (CWE-117) exists in sentry. Attackers reach the vulnerable code path via ``INFO`` without authentication.
📍 Affected scope
sentry — . Attack surface: `INFO` / `WARNING`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **24.4.1**.
🛡️ Workaround
Workaround: Users can configure the logging level to exclude logs of the `INFO` level and only generate logs for levels at `WARNING` or higher.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'sentry' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'sentry' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `sentry` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Users can configure the logging level to exclude logs of the `INFO` level and only generate logs for levels at `WARNING` or higher.パッチが適用されるまでの応急処置として、Users can configure the logging level to exclude logs of the `INFO` level and only generate logs for levels at `WARNING` or higher. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade sentry to 24.4.1ステージング環境で 24.4.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
sentry
[{"type":"ECOSYSTEM","events":[{"introduced":"24.3.0"},{"fixed":"24.4.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-32474
- advisory https://github.com/advisories/GHSA-6cjm-4pxw-7xp9
- package https://github.com/getsentry/sentry
- package https://pypi.org/project/sentry
- web https://github.com/getsentry/sentry/security/advisories/GHSA-6cjm-4pxw-7xp9
- web https://github.com/getsentry/sentry/pull/66393
- web https://github.com/getsentry/sentry/pull/69148
- web https://github.com/getsentry/sentry/commit/d5b34568d9f1c41362ccb62141532a0a2169512f