Buffer Overflow in crossbeam-channel (CVE-2020-15254)
Summary
Vulnerability in crossbeam-channel (CVE-2020-15254). Successful exploitation can lead to full system takeover. Exploitable via bounded. Mitigation: upgrade to 0.4.4 or later.
Original description
The description as published by the source.
Impact
The affected version of this crate's the bounded channel incorrectly assumes that Vec::from_iter has allocated capacity that same as the number of iterator elements. Vec::from_iter does not actually guarantee that and may allocate extra memory. The destructor of the bounded channel reconstructs Vec from the raw pointer based on the incorrect assumes described above. This is unsound and causing deallocation with the incorrect capacity when Vec::from_iter has allocated different sizes with the number of iterator elements.
Patches
This has been fixed in crossbeam-channel 0.4.4.
We recommend users to upgrade to 0.4.4.
References
See https://github.com/crossbeam-rs/crossbeam/pull/533, https://github.com/crossbeam-rs/crossbeam/issues/539, and https://github.com/RustSec/advisory-db/pull/425 for more details.
License
This advisory is in the public domain.
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-2020-15254 has been found in crossbeam-channel.
Attackers can target a specific entry point like bounded over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade crossbeam-channel to 0.4.4 or later.
If unsure, ask your IT team or search "crossbeam-channel CVE-2020-15254" on the vendor's site.
CVE-2020-15254 (crossbeam-channel) — CWE-119
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: bounded / Vec
Patched: 0.4.4 — 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-119) exists in crossbeam-channel. Attackers reach the vulnerable code path via bounded without authentication.
Check the vendor advisory for the affected versions of crossbeam-channel. Attack surface: bounded / Vec.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 0.4.4.
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 'crossbeam-channel' . 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 'crossbeam-channel' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
crossbeam-channelを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade crossbeam-channel to 0.4.4ステージング環境で 0.4.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2020-15254 firefox Fixed in: 82.0+build2-0ubuntu0.16.04.5
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web rustsec.org