CVE-2023-40583Network attack vector

Node crash via unchecked peer-record identity

Published Aug 25, 2023 · Updated Oct 2, 2024

Uncontrolled resource consumption in libp2p go-libp2p before 0.27.4 allows remote attackers to crash nodes via signed peer records. The identify service validates each record signature but fails to require its public-key-derived peer ID to match the connected remote peer, so records for fabricated peers accumulate indefinitely in the peerstore. Any network peer can submit valid self-signed records; because fabricated peers never connect, disconnect cleanup never removes their data, allowing memory exhaustion and a node crash.

CVSS severity7.5
High
EPSS probability0.95%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Uncontrolled resource consumption in libp2p go-libp2p before 0.27.4 allows remote attackers to crash nodes via signed peer records. The identify service validates each record signature but fails to require its public-key-derived peer ID to match the connected remote peer, so records for fabricated peers accumulate indefinitely in the peerstore. Any network peer can submit valid self-signed records; because fabricated peers never connect, disconnect cleanup never removes their data, allowing memory exhaustion and a node crash.

The record

CVE
CVE-2023-40583
Published
Aug 25, 2023
Updated
Oct 2, 2024
Vendor
libp2p
Product
go-libp2p
Classifications
CWE-400, T1499.004
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 25, 2023CVE publishedPublication date reported by the CVE source.
  2. Oct 2, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 0.27.4

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

libp2p · go-libp2pversion=< 0.27.4

Published CVSS scores

7.5NISTCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
7.5GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-400Uncontrolled Resource Consumption
T1499.004Application or System Exploitation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo