GHSA-58xc-hpvq-8473
Redox UEFI Safe API can cause heap-buffer-overflow
ffi::nstr() should be marked unsafe, since a pointer to a buffer without a trailing 0 value will cause a heap buffer overflow.
What each source reports
GitHub AdvisoriesNo score
Redox UEFI Safe API can cause heap-buffer-overflow
ffi::nstr() should be marked unsafe, since a pointer to a buffer without a trailing 0 value will cause a heap buffer overflow.
- Record
GHSA-58xc-hpvq-8473- Weakness
- CWE-122
- Updated
- 2026-11-02
OSVNo score
Redox UEFI Safe API can cause heap-buffer-overflow
ffi::nstr() should be marked unsafe, since a pointer to a buffer without a trailing 0 value will cause a heap buffer overflow.
- Record
GHSA-58xc-hpvq-8473- Weakness
- CWE-122
- Updated
- 2026-11-02
OSVRUSTSEC-2025-0032No score
Safe API can cause heap-buffer-overflow
ffi::nstr() should be marked unsafe, since a pointer to a buffer without a trailing 0 value will cause a heap buffer overflow.
- Record
RUSTSEC-2025-0032- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
redox_uefi_stdcrates.io | 0.1.8 up to 0.1.14 | 0.1.14 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-58xc-hpvq-8473 is a vulnerability with no CVSS score yet in redox_uefi_std, published March 27, 2025. No source lists public exploit code. Fixed in redox_uefi_std 0.1.14.