How severe is GHSA-58xc-hpvq-8473?

No CVSS score has been assigned to GHSA-58xc-hpvq-8473 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-58xc-hpvq-8473?

GHSA-58xc-hpvq-8473 affects the following packages: redox_uefi_std (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-58xc-hpvq-8473?

Update redox_uefi_std to 0.1.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-58xc-hpvq-8473 is resolved across your whole dependency graph.

How do I detect GHSA-58xc-hpvq-8473 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for redox_uefi_std. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-58xc-hpvq-8473 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-58xc-hpvq-8473?

O3 pinpoints whether GHSA-58xc-hpvq-8473 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-58xc-hpvq-8473 actively exploited in the wild?

No public exploit code has been indexed for GHSA-58xc-hpvq-8473 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-58xc-hpvq-8473 published, and has it been updated?

GHSA-58xc-hpvq-8473 was published on May 6, 2025 and was last updated on October 28, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

GHSA-58xc-hpvq-8473

Redox UEFI Safe API can cause heap-buffer-overflow

Also known asRUSTSEC-2025-0032

Published

May 6, 2025

Updated

Oct 28, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🦀redox_uefi_std

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`redox_uefi_std`	≥ 0.1.8&&< 0.1.14	0.1.14

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for redox_uefi_std. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update redox_uefi_std to 0.1.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-58xc-hpvq-8473 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-58xc-hpvq-8473 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-58xc-hpvq-8473. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-58xc-hpvq-8473 in your dependencies?

O3 detects GHSA-58xc-hpvq-8473 across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works