← Back
CVE-2021-47935
high
CVSS 8.8
Code Injection in sentry (CVE-2021-47935)
Summary
code injection in sentry (CVE-2021-47935). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `8.2.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2021-47935** has been found in sentry.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade sentry to **8.2.2** or later.
If unsure, ask your IT team or search "sentry CVE-2021-47935" on the vendor's site.
CVE-2021-47935 (sentry) — CWE-94 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Patched: `8.2.2` — 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.
❓ What is the problem
**arbitrary code execution** (CWE-94) exists in sentry.
📍 Affected scope
sentry — .
🔥 Severity
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **8.2.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade sentry to 8.2.2ステージング環境で 8.2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
sentry
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"8.2.0"}]}]
pip
sentry
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.2.2"}]}]
References
- advisory https://www.vulncheck.com/advisories/sentry-remote-code-execution-via-pickle-deserialization
- advisory https://nvd.nist.gov/vuln/detail/CVE-2021-47935
- advisory https://github.com/advisories/GHSA-444r-2whx-3685
- package https://github.com/getsentry/sentry
- report https://www.exploit-db.com/exploits/50318
- web https://sentry.io/welcome/
- web https://sentry.io/welcome
- web https://github.com/getsentry/sentry/commit/19a0ba63d9ffb6aff79c7b78e2fa951a94edd61a
- web https://github.com/getsentry/sentry/commit/1f6090dc64b237c3da22bf35a5863a7136ac4669
- web https://github.com/pypa/advisory-database/tree/main/vulns/sentry/PYSEC-2026-131.yaml