CVE-2022-24759

Failure to validate signature during handshake in @chainsafe/libp2p-noise

HIGH
7.4
CVSS Score
Published: March 17, 2022 at 04:40 PM UTC
Updated: June 17, 2026 at 04:32 AM UTC
1 product affected across 1 vendorJs LIBP2P Noise

Using js-libp2p-noise by ChainSafe?

Get instant alerts when new vulnerabilities affect js-libp2p-noise - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.4
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

`@chainsafe/libp2p-noise` contains TypeScript implementation of noise protocol, an encryption protocol used in libp2p. `@chainsafe/libp2p-noise` before 4.1.2 and 5.0.3 does not correctly validate signatures during the handshake process. This may allow a man-in-the-middle to pose as other peers and get those peers banned. Users should upgrade to version 4.1.2 or 5.0.3 to receive a patch. There are currently no known workarounds.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 4.1.2v < 5.0.35.0.0 ≤ v < 5.0.3
Affected range stops below 4.1.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.0.3, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-347

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card