grcov has an out of bounds write triggered by crafted coverage data
Priority LOW 38CWE-787Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
Function `grcov::covdir::get_coverage` uses the `unsafe` function `get_unchecked_mut` without validating that the index is in bounds. This results in memory corruption, and could potentially allow arbitrary code execution provided that an attacker can feed the tool crafted coverage data.
Why it matters now
Fix Fixed grcov (crates.io): 0.8.20
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | grcov (crates.io) | before 0.8.20 | 0.8.20 | Patch available | GHSA-qm2p-4w45-v2vr |
- grcov (crates.io) Vendor— Affected before 0.8.20 Fixed in 0.8.20 Patch available GHSA-qm2p-4w45-v2vr
Remediation
- Fix · GHSA-qm2p-4w45-v2vr grcov (crates.io) Fixed in 0.8.20 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-qm2p-4w45-v2vr
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences