Quick answers
- Is CVE-2022-23487 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-23487 being exploited in the wild.
- How severe is CVE-2022-23487?
- Low severity, with a CVSS score of 3.1, published 7 December 2022.
- Which products and versions are affected?
- Libp2p Js-Libp2p < 0.38.0.
- Is there a fix for CVE-2022-23487?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2022-23487 attacked?
- It is attacked over the network.
- Am I affected by CVE-2022-23487?
- Check whether you run Libp2p Js-Libp2p at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This is a resource exhaustion vulnerability (CWE-400, CWE-770) in js-libp2p's connection, stream, peer, and memory management. The root cause is inadequate resource limits in the connection manager, which was designed to handle normal peer churn but not deliberate DoS attacks. An attacker with network access can send crafted requests that force the allocation of large amounts of memory, ultimately leading to out-of-memory conditions and process termination. The attack requires no authentication or user interaction. The vulnerability is fixed in js-libp2p v0.38.0 and later, which implements tighter resource scoping and limits.
Affected products
- libp2p js-libp2p < 0.38.0
Identifiers
- CVE-2022-23487
- GHSA-f44q-634c-jvwv
Timeline
- 2022-12-07: disclosed