Failure to verify the public key of a `SignedEnvelope` against the `PeerId` in a `PeerRecord`
Priority LOW 38Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
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`.
Why it matters now
Fix Fixed libp2p-core (crates.io): 0.30.2
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | libp2p-core (crates.io) | 0.30.0-rc.1 to before 0.30.2 | 0.30.2 | Patch available | GHSA-wc36-xgcc-jwpr |
- libp2p-core (crates.io) Vendor— Affected 0.30.0-rc.1 to before 0.30.2 Fixed in 0.30.2 Patch available GHSA-wc36-xgcc-jwpr
Remediation
- Fix · GHSA-wc36-xgcc-jwpr libp2p-core (crates.io) Fixed in 0.30.2 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-wc36-xgcc-jwpr
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences