Identity Spoofing in libp2p-secio

published 2019-08-23 7y ago modified 2021-08-17 5y ago

cvss: 9.1; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

Affected versions of `libp2p-secio` does not correctly verify that the `PeerId` of `DstPeer` matches the `PeerId` discovered in the crypto handshake, resulting in a high severity identity spoofing vulnerability.

## Recommendation

Update to version 0.9.0 or later.

Patch / fix

fixed in 1 links 1

npm libp2p-secio 0.9.0

github.com/libp2p/js-libp2p-secio#95 pull request

Is GHSA-rch7-f4h5-x9rj 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 Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	9.1	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	libp2p-secio	<0.9.0	0.9.0

Classification

Weakness

CWE-290 Authentication Bypass by Spoofing

References

Sources

GitHub Advisory GHSA-rch7-f4h5-x9rj

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.