← Back
CVE-2020-29367
Out-of-Bounds Write in blosc2 (CVE-2020-29367)
Summary
out-of-bounds write in blosc2 (CVE-2020-29367). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `c4c6470e88210afc95262c8b9fcc27e30ca043ee` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2020-29367** has been found in blosc2.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade blosc2 to **c4c6470e88210afc95262c8b9fcc27e30ca043ee** or later.
If unsure, ask your IT team or search "blosc2 CVE-2020-29367" on the vendor's site.
CVE-2020-29367 (blosc2) — CWE-787 /
Attack vector: local / unauthenticated
Patched: `c4c6470e88210afc95262c8b9fcc27e30ca043ee` — 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
**out-of-bounds write** (CWE-787) exists in blosc2.
📍 Affected scope
blosc2 — .
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **c4c6470e88210afc95262c8b9fcc27e30ca043ee**.
🛡️ 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 'blosc2' .` 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 'blosc2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `blosc2` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade blosc2 to c4c6470e88210afc95262c8b9fcc27e30ca043eeステージング環境で c4c6470e88210afc95262c8b9fcc27e30ca043ee に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
blosc2
[{"repo":"https:\/\/github.com\/Blosc\/c-blosc2","type":"GIT","events":[{"introduced":"0"},{"fixed":"c4c6470e88210afc95262c8b9fcc27e30ca043ee"}]},{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
References
- advisory https://github.com/advisories/GHSA-8c7c-2c8j-3xfp
- advisory https://nvd.nist.gov/vuln/detail/CVE-2020-29367
- package https://github.com/Blosc/python-blosc2
- patch https://github.com/Blosc/c-blosc2/commit/c4c6470e88210afc95262c8b9fcc27e30ca043ee
- web https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26442
- web https://github.com/Blosc/python-blosc2/releases/tag/v0.1.7
- web https://github.com/pypa/advisory-database/tree/main/vulns/blosc2/PYSEC-2020-343.yaml