Advisory record · GHSA-j7qp-mfxf-8xjw

Resource exhaustion in github.com/libp2p/go-libp2p

CVSS 7.5 HighEPSS 0.011 · 65th percentile

Published by the GitHub Advisory Database at 14 Dec 2022, 02:21 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/libp2p/go-libp2pGo<0.18.00.18.0
Identifiers
GHSA-j7qp-mfxf-8xjw · CVE-2022-23492 · GO-2022-1148
Weakness (CWE)
CWE-400
Published
14 Dec 2022
Updated
20 May 2024

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

go-libp2p versions before 0.18.0 are vulnerable to targeted resource exhaustion attacks against its connection, stream, peer, and memory management. An attacker can make the process allocate large amounts of memory until the host operating system kills it. The source does not say what network access is required. Upgrade to version 0.18.0 or later; the source recommends v0.21.0 or later for better resource limits and metrics.

Written 10 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.011, the 65th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the GitHub Advisory Database, published 14 Dec 2022. New records show when each source confirmed them.

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.