Redox UEFI Safe API can cause heap-buffer-overflow

published 2025-03-27 last yr. modified 2025-10-28 last yr. also RUSTSEC-2025-0032

cvss: —; not scored
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

ffi::nstr() should be marked unsafe, since a pointer to a buffer without a trailing 0 value will cause a heap buffer overflow.

Patch / fix

fixed in 1 links 1

crates.io redox_uefi_std 0.1.14

gitlab.redox-os.org/redox-os/uefi@b711d47 commit

Is GHSA-58xc-hpvq-8473 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem	package	affected	fixed in
crates.io	redox_uefi_std	>=0.1.8, <0.1.14	0.1.14

Classification

Weakness

CWE-122 Heap-based Buffer Overflow

References

gitlab.redox-os.org /redox-os/uefi/-/commit/b711d47e815665b0ec8949e39292ad8e3fdd0756
web
gitlab.redox-os.org /redox-os/uefi
package
rustsec.org /advisories/RUSTSEC-2025-0032.html
web, advisory
crates.io /crates/redox_uefi_std
package

Sources

GitHub Advisory GHSA-58xc-hpvq-8473
OSV RUSTSEC-2025-0032

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.