CVE-2022-24759: Failure to validate signature during handshake in @chainsafe/libp2p-noise

@chainsafe/libp2p-noise Updated 02 Oct 2025

Summary

18/03/2022
Yes i
High
8.1

CVE-2022-24759: Failure to validate signature during handshake. Affects @chainsafe/libp2p-noise across 2 version ranges.

< 4.1.2 >= 5.0.0, < 5.0.3

Fixed in 4.1.2 or 5.0.3, depending on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @chainsafe/libp2p-noise package is an npm package that provides functionality for the libp2p protocol. It is used for secure communication between peers in a decentralized network. The package implements the Noise Protocol Framework, which is a framework for building secure and efficient cryptographic protocols. The vulnerability in this package allows for a failure to validate signatures during the handshake process, which can be exploited by a man-in-the-middle attacker to pose as other peers and potentially get those peers banned from the network.

Vulnerability Detail

The vulnerability in @chainsafe/libp2p-noise arises from a failure to correctly validate signatures during the handshake process. This means that an attacker can intercept the communication between peers and impersonate other peers without being detected. This can lead to various security issues, such as unauthorized access to sensitive information, manipulation of network traffic, and potential banning of innocent peers. The vulnerability has a CVSS score of 8.1, indicating a high severity level. It is important to note that this vulnerability affects versions before 4.1.2 and 5.0.3 of the package.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 4.1.2 4.1.2
    npm install @chainsafe/libp2p-noise@4.1.2
  • >= 5.0.0, < 5.0.3 5.0.3
    npm install @chainsafe/libp2p-noise@5.0.3

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Conclusion

The @chainsafe/libp2p-noise package before versions 4.1.2 and 5.0.3 is vulnerable to a failure to validate signatures during the handshake process. This can be exploited by a man-in-the-middle attacker to impersonate other peers and potentially get them banned from the network. To mitigate this vulnerability, users should upgrade to the fixed versions of the package. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for @chainsafe/libp2p-noise →

Share this vulnerability

FAQ

@chainsafe/libp2p-noise is an npm package that provides secure communication functionality for the libp2p protocol.

The vulnerability allows a man-in-the-middle attacker to impersonate other peers and potentially get them banned from the network.

You can fix this vulnerability by upgrading to version 4.1.2 or 5.0.3 of the @chainsafe/libp2p-noise package.

No, the only solution is to upgrade to the fixed versions of the package.

The CVSS score of this vulnerability is 8.1, indicating a high severity level.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 4.1.2 4.1.2
    npm install @chainsafe/libp2p-noise@4.1.2
  • >= 5.0.0, < 5.0.3 5.0.3
    npm install @chainsafe/libp2p-noise@5.0.3

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback