Peer impersonation via invalid handshake signature
Published Mar 17, 2022 · Updated Apr 23, 2025
Improper signature verification in ChainSafe js-libp2p-noise before 4.1.2 and 5.0.3 allows man-in-the-middle attackers to impersonate peers. During the Noise handshake, the library fails to correctly validate peer signatures, letting an intermediary pose as another peer and cause that peer to be banned. Exploitation requires man-in-the-middle network positioning; the documented consequence is peer impersonation and integrity disruption rather than direct data disclosure.
Summary
What happened
Improper signature verification in ChainSafe js-libp2p-noise before 4.1.2 and 5.0.3 allows man-in-the-middle attackers to impersonate peers. During the Noise handshake, the library fails to correctly validate peer signatures, letting an intermediary pose as another peer and cause that peer to be banned. Exploitation requires man-in-the-middle network positioning; the documented consequence is peer impersonation and integrity disruption rather than direct data disclosure.
The record
- CVE
- CVE-2022-24759
- Published
- Mar 17, 2022
- Updated
- Apr 23, 2025
- Vendor
- ChainSafe Systems
- Product
- js-libp2p-noise
- Classifications
- CWE-347, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 17, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.1.2
- Affected versionversion=>= 5.0.0, < 5.0.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo