How severe is GHSA-wc36-xgcc-jwpr?

No CVSS score has been assigned to GHSA-wc36-xgcc-jwpr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wc36-xgcc-jwpr?

GHSA-wc36-xgcc-jwpr affects the following packages: libp2p-core (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-wc36-xgcc-jwpr?

Update libp2p-core to 0.30.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wc36-xgcc-jwpr is resolved across your whole dependency graph.

How do I detect GHSA-wc36-xgcc-jwpr in my crates.io dependencies?

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

How do I mitigate GHSA-wc36-xgcc-jwpr 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-wc36-xgcc-jwpr?

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

Is GHSA-wc36-xgcc-jwpr actively exploited in the wild?

No public exploit code has been indexed for GHSA-wc36-xgcc-jwpr 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-wc36-xgcc-jwpr published, and has it been updated?

GHSA-wc36-xgcc-jwpr was published on June 17, 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-wc36-xgcc-jwpr — libp2p-core

GHSA-wc36-xgcc-jwpr is a security vulnerability in libp2p-core. A fix is available for libp2p-core — see the affected versions and patch details below.

Failure to verify the public key of a `SignedEnvelope` against the `PeerId` in a `PeerRecord`

Also known asRUSTSEC-2022-0009

Published

Jun 17, 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

🦀libp2p-core

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

Affected versions of this crate did not check that the public key the signature was created with matches the peer ID of the peer record. Any combination was considered valid.

This allows an attacker to republish an existing PeerRecord with a different PeerId.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`libp2p-core`	≥ 0.30.0-rc.1&&< 0.30.2	0.30.2`cargo update -p libp2p-core --precise 0.30.2`

Detection & mitigation playbook

Open-source dependency

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

Tailored to GHSA-wc36-xgcc-jwpr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected versions of this crate did not check that the public key the signature was created with matches the peer ID of the peer record. Any combination was considered valid. This allows an attacker to republish an existing `PeerRecord` with a different `PeerId`.

O3 Security · Impact-Aware SCA

Is GHSA-wc36-xgcc-jwpr in your dependencies?

O3 Security finds GHSA-wc36-xgcc-jwpr 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