How severe is GHSA-gv7f-5qqh-vxfx?

No CVSS score has been assigned to GHSA-gv7f-5qqh-vxfx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gv7f-5qqh-vxfx?

GHSA-gv7f-5qqh-vxfx affects the following packages: xous (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-gv7f-5qqh-vxfx?

Update xous to 0.9.51 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gv7f-5qqh-vxfx is resolved across your whole dependency graph.

How do I detect GHSA-gv7f-5qqh-vxfx in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for xous, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-gv7f-5qqh-vxfx 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.

Is GHSA-gv7f-5qqh-vxfx actively exploited in the wild?

No public exploit code has been indexed for GHSA-gv7f-5qqh-vxfx 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-gv7f-5qqh-vxfx published, and has it been updated?

GHSA-gv7f-5qqh-vxfx was published on December 30, 2024 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

Not in CISA KEV

xous has unsound usages of `core::slice::from_raw_parts`GHSA-gv7f-5qqh-vxfx

Fix: betrusted-io/xous-core#411

GHSA-gv7f-5qqh-vxfx is a security vulnerability in xous. A fix is available for xous — see the affected versions and patch details below.

Also known asRUSTSEC-2024-0431

Published

Dec 30, 2024

Updated

Oct 28, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 28, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀xous

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

We consider as_slice and as_slice_mut unsound because: the pointer with any bit patterns could be cast to the slice of arbitrary types. The pointer could be created by unsafe new and deprecated from_parts. We consider that from_parts should be removed in latest version because it will help trigger unsoundness in as_slice. With new declared as unsafe, as_slice should also declared as unsafe.

This was patched in by marking two functions as unsafe.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`xous`	all versions	0.9.51`cargo update -p xous --precise 0.9.51`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for xous, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update xous to 0.9.51 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gv7f-5qqh-vxfx 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.

Frequently Asked Questions

We consider `as_slice` and `as_slice_mut` unsound because: the pointer with any bit patterns could be cast to the slice of arbitrary types. The pointer could be created by unsafe new and deprecated `from_parts`. We consider that `from_parts` should be removed in latest version because it will help trigger unsoundness in `as_slice`. With new declared as unsafe, `as_slice` should also declared as unsafe. This was patched in by marking two functions as `unsafe`.

O3 Security · Impact-Aware SCA

Is GHSA-gv7f-5qqh-vxfx in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works