CVE-2022-24759 is a high-severity (CVSS 8.1) CWE-347 vulnerability in @chainsafe/libp2p-noise. A fix is available for @chainsafe/libp2p-noise — see the affected versions and patch details below.
Failure to validate signature during handshake in @chainsafe/libp2p-noise
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-24759.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2022-24759 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@chainsafe/libp2p-noisenpmDescription
@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 Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @chainsafe/libp2p-noise | all versions | 4.1.2npm install @chainsafe/libp2p-noise@4.1.2 |
| 📦npm | @chainsafe/libp2p-noise | ≥ 5.0.0&&< 5.0.3 | 5.0.3npm install @chainsafe/libp2p-noise@5.0.3 |
Affected Products
js-libp2p-noisechainsafeDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @chainsafe/libp2p-noise, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @chainsafe/libp2p-noise to 4.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24759 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2022-24759 in your dependencies?
Find it across npm, including transitive dependencies.