js-libp2p-noise: Improper Verification of Cryptographic Signature
CVE-2022-24759 is a high-severity improper verification of cryptographic signature vulnerability in js-libp2p-noise from ChainSafe, with a CVSS 3.1 base score of 7.4 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected js-libp2p-noise versions: < 4.1.2; >= 5.0.0, < 5.0.3. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.5% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of js-libp2p-noise you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| ChainSafe | js-libp2p-noise | < 4.1.2; >= 5.0.0, < 5.0.3 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.1 | High | CNA (github.com) |
| CVSS 3.1 | 7.4 | High | NVD |
| CVSS 2.0 | 5.8 | Medium | NVD |
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Verification of Cryptographic Signature
The product does not verify, or incorrectly verifies, the cryptographic signature for data.
More Improper Verification of Cryptographic Signature vulnerabilities (CWE-347)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- github.com/ChainSafe/js-libp2p-noise/security/advisories/GHSA-j3ff-xp6c-6gccThird Party Advisory
Patches and release notes
- github.com/ChainSafe/js-libp2p-noise/pull/130Third Party Advisory
- github.com/ChainSafe/js-libp2p-noise/releases/tag/v5.0.3Third Party Advisory
Recent Improper Verification of Cryptographic Signature vulnerabilities
- 8.1 High severity
- 7.8 High severity
- 7.5 High severity
- 5.5 Medium severity
Microsoft Windows Spoofing Exploited
- 10.0 Critical severity
- 8.8 High severity
Spotted an error? Tell us.