GHSA-wc36-xgcc-jwpr json
Failure to verify the public key of a `SignedEnvelope` against the `PeerId` in a `PeerRecord`
published 4y ago modified 3y ago also RUSTSEC-2022-0009
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
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`.
Patch / fix
- crates.io libp2p-core 0.30.2, 0.31.1
Is GHSA-wc36-xgcc-jwpr in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | libp2p-core | >=0.30.0-rc.1, <0.30.2 >=0.31.0-0, <0.31.1 |
0.30.2 0.31.1 |
References
-
github.com
/libp2p/rust-libp2p
package
-
rustsec.org
/advisories/RUSTSEC-2022-0009.html
web, advisory
-
crates.io
/crates/libp2p-core
package
Sources
- GitHub Advisory GHSA-wc36-xgcc-jwpr
- OSV RUSTSEC-2022-0009
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.