Redox UEFI Safe API can cause heap-buffer-overflow
Priority LOW 38CWE-122Published · 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
ffi::nstr() should be marked unsafe, since a pointer to a buffer without a trailing 0 value will cause a heap buffer overflow.
Why it matters now
Fix Fixed redox_uefi_std (crates.io): 0.1.14
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 |
|---|---|---|---|---|---|
| — | redox_uefi_std (crates.io) | 0.1.8 to before 0.1.14 | 0.1.14 | Patch available | GHSA-58xc-hpvq-8473 |
- redox_uefi_std (crates.io) Vendor— Affected 0.1.8 to before 0.1.14 Fixed in 0.1.14 Patch available GHSA-58xc-hpvq-8473
Remediation
- Fix · GHSA-58xc-hpvq-8473 redox_uefi_std (crates.io) Fixed in 0.1.14 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-58xc-hpvq-8473
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences