How severe is GHSA-wfg4-322g-9vqv?

No CVSS score has been assigned to GHSA-wfg4-322g-9vqv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wfg4-322g-9vqv?

GHSA-wfg4-322g-9vqv affects the following packages: memoffset (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-wfg4-322g-9vqv?

Update memoffset to 0.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wfg4-322g-9vqv is resolved across your whole dependency graph.

How do I detect GHSA-wfg4-322g-9vqv in my crates.io dependencies?

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

How do I mitigate GHSA-wfg4-322g-9vqv 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-wfg4-322g-9vqv?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-wfg4-322g-9vqv can be triaged on real exposure rather than presence alone.

Is GHSA-wfg4-322g-9vqv actively exploited in the wild?

No public exploit code has been indexed for GHSA-wfg4-322g-9vqv 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-wfg4-322g-9vqv published, and has it been updated?

GHSA-wfg4-322g-9vqv was published on June 21, 2023 and was last updated on November 8, 2023. 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

GHSA-wfg4-322g-9vqv — memoffset

Fix: Gilnaa/memoffset#50

GHSA-wfg4-322g-9vqv is a security vulnerability in memoffset. A fix is available for memoffset — see the affected versions and patch details below.

memoffset allows reading uninitialized memory

Also known asRUSTSEC-2023-0045

Published

Jun 21, 2023

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀memoffset

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

memoffset allows attempt of reading data from address 0 with arbitrary type. This behavior is an undefined behavior because address 0 to std::mem::size_of<T> may not have valid bit-pattern with T. Old implementation dereferences uninitialized memory obtained from std::mem::align_of. Older implementation prior to it allows using uninitialized data obtained from std::mem::uninitialized with arbitrary type then compute offset by taking the address of field-projection. This may also result in an undefined behavior for "father" that includes (directly or transitively) type that does not allow to be uninitialized.

This flaw was corrected by using std::ptr::addr_of in https://github.com/Gilnaa/memoffset/pull/50.

Affected Packages

1 total 1 fixed

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

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for memoffset, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update memoffset to 0.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wfg4-322g-9vqv 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-wfg4-322g-9vqv can be triaged on real exposure rather than presence alone.

Tailored to GHSA-wfg4-322g-9vqv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

memoffset allows attempt of reading data from address `0` with arbitrary type. This behavior is an undefined behavior because address `0` to `std::mem::size_of<T>` may not have valid bit-pattern with `T`. Old implementation dereferences uninitialized memory obtained from `std::mem::align_of`. Older implementation prior to it allows using uninitialized data obtained from `std::mem::uninitialized` with arbitrary type then compute offset by taking the address of field-projection. This may also result in an undefined behavior for "father" that includes (directly or transitively) type that [does no

O3 Security · Impact-Aware SCA

Is GHSA-wfg4-322g-9vqv in your dependencies?

O3 Security finds GHSA-wfg4-322g-9vqv across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works