How severe is GHSA-c439-chv8-8g2j?

No CVSS score has been assigned to GHSA-c439-chv8-8g2j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-c439-chv8-8g2j?

GHSA-c439-chv8-8g2j affects the following packages: os_socketaddr (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-c439-chv8-8g2j?

Update os_socketaddr to 0.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c439-chv8-8g2j is resolved across your whole dependency graph.

How do I detect GHSA-c439-chv8-8g2j in my crates.io dependencies?

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

How do I mitigate GHSA-c439-chv8-8g2j 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-c439-chv8-8g2j?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-c439-chv8-8g2j can be triaged on real exposure rather than presence alone.

Is GHSA-c439-chv8-8g2j actively exploited in the wild?

No public exploit code has been indexed for GHSA-c439-chv8-8g2j 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-c439-chv8-8g2j published, and has it been updated?

GHSA-c439-chv8-8g2j was published on September 2, 2022 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-c439-chv8-8g2j — os_socketaddr

Fix: rust-lang/rust#78802

GHSA-c439-chv8-8g2j is a security vulnerability in os_socketaddr. A fix is available for os_socketaddr — see the affected versions and patch details below.

`os_socketaddr` invalidly assumes the memory layout of std::net::SocketAddr

Also known asRUSTSEC-2022-0052

Published

Sep 2, 2022

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

🦀os_socketaddr

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

The os_socketaddr crate has assumed std::net::SocketAddrV4 and std::net::SocketAddrV6 have the same memory layout as the system C representation sockaddr. It has simply casted the pointers to convert the socket addresses to the system representation.

These layout were changed into idiomatic rust types in nightly std. Starting from rustc 1.64 the affected versions of this crate will have undefined behaviour.

Affected Packages

1 total 1 fixed

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

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for os_socketaddr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update os_socketaddr to 0.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c439-chv8-8g2j 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-c439-chv8-8g2j can be triaged on real exposure rather than presence alone.

Tailored to GHSA-c439-chv8-8g2j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The [`os_socketaddr`](https://crates.io/crates/os_socketaddr) crate has assumed `std::net::SocketAddrV4` and `std::net::SocketAddrV6` have the same memory layout as the system C representation `sockaddr`. It has simply casted the pointers to convert the socket addresses to the system representation. These layout were [changed into idiomatic rust types](https://github.com/rust-lang/rust/pull/78802) in nightly `std`. Starting from rustc 1.64 the affected versions of this crate will have undefined behaviour.

O3 Security · Impact-Aware SCA

Is GHSA-c439-chv8-8g2j in your dependencies?

O3 Security finds GHSA-c439-chv8-8g2j 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