libp2p nodes vulnerable to attack using large RSA keys (CVE-2023-39533)
Published Last modified Sources: BSI, CVE.org, OSV
What is affected, what to do
go-libp2p is the Go implementation of the libp2p Networking Stack. Prior to versions 0.27.8, 0.28.2, and 0.29.1 malicious peer can use large RSA keys to run a resource exhaustion attack & force a node to spend time doing signature verification of the large key.
Update Libp2p Go-libp2p to version 0.27.8.
- Affected
- Libp2p Go-libp2p
gte 0.28.0, < 0.28.2..* - Libp2p Go-libp2p
lt *..0.27.8 - Libp2p Go-libp2p
eq 0.29.0..0.29.0
- Libp2p Go-libp2p
- Fixed in
- Libp2p Go-libp2p
0.27.8
- Libp2p Go-libp2p
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
7.5
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v3
7.5
CVSS v3
Severity High on the scale from 0 to 10.
Source: BSI, CVE.org, OSV
1.5 %
EPSS score
Moderate — model estimates 1-10% exploitation likelihood.
Source: FIRST EPSS, percentile 74.4
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 85.00 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 7.5 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 7.5
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 1.5 %
- Moderate — model estimates 1-10% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 74.4
- High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
- CISA assessment (SSVC)
- Exploitation: proof of concept · automatable · Technical impact: partial
- Source: CISA Vulnrichment, as of 10 October 2024
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-770
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
go-libp2p is the Go implementation of the libp2p Networking Stack. Prior to versions 0.27.8, 0.28.2, and 0.29.1 malicious peer can use large RSA keys to run a resource exhaustion attack & force a node to spend time doing signature verification of the large key. This vulnerability is present in the core/crypto module of go-libp2p and can occur during the Noise handshake and the libp2p x509 extension verification step. To prevent this attack, go-libp2p versions 0.27.8, 0.28.2, and 0.29.1 restrict RSA keys to <= 8192 bits. To protect one's application, it is necessary to update to these patch releases and to use the updated Go compiler in 1.20.7 or 1.19.12. There are no known workarounds for this issue.
Source: BSI CSAF, BSI WID Portal, cvelistv5, NVD (NIST), OSV (Open Source Vulnerabilities)
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| libp2p | go-libp2p |
|
|
| Dell | ECS |
|
|
| go | github.com/libp2p/go-libp2p |
|
|
Vendors and products
Weakness classes (CWE)
CWE-770Allocation of Resources Without Limits or Throttling
Base
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Entry at MITRE CWE-770
References & sources
- github.comlibp2p/go-libp2p/security/advisories/GHSA-876p-8259-xjggadvisory, x_refsource_CONFIRM
- go.devissue/61460report
- github.comlibp2p/go-libp2p/commit/0cce607219f3710addc7e18672cffd1f1d912fbbfix, x_refsource_MISC
- github.comgolang/go/issues/61460x_refsource_MISC
- github.comlibp2p/go-libp2p/pull/2454x_refsource_MISC
- github.comquic-go/quic-go/pull/4012x_refsource_MISC
- github.comgolang/go/commit/2350afd2e8ab054390e284c95d5b089c142db017x_refsource_MISC
- github.comlibp2p/go-libp2p/commit/445be526aea4ee0b1fa5388aa65d32b2816d3a00x_refsource_MISC
- github.comlibp2p/go-libp2p/commit/e30fcf7dfd4715ed89a5e68d7a4f774d3b9aa92dx_refsource_MISC
- nrdax.comtechniques/NRDAX-T0205-pre-handshake-crypto-cpu-burnx_refsource_MISC
- NVD (NIST)vuln/detail/CVE-2023-39533advisory
- github.comlibp2p/go-libp2ppackage
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedGitHub
New references:- https://github.com/golang/go/commit/2350afd2e8ab054390e284c95d5b089c142db017
- https://github.com/golang/go/issues/61460
- https://github.com/libp2p/go-libp2p/commit/0cce607219f3710addc7e18672cffd1f1d912fbb
- https://github.com/libp2p/go-libp2p/commit/445be526aea4ee0b1fa5388aa65d32b2816d3a00
and 5 more references
Show 25 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://github.com/golang/go/commit/2350afd2e8ab054390e284c95d5b089c142db017Reference added —https://github.com/golang/go/issues/61460Reference added —https://github.com/libp2p/go-libp2p/commit/0cce607219f3710addc7e18672cffd1f1d912fbbReference added —https://github.com/libp2p/go-libp2p/commit/445be526aea4ee0b1fa5388aa65d32b2816d3a00Reference added —https://github.com/libp2p/go-libp2p/commit/e30fcf7dfd4715ed89a5e68d7a4f774d3b9aa92dReference added —https://github.com/libp2p/go-libp2p/pull/2454Reference added —https://github.com/libp2p/go-libp2p/security/advisories/GHSA-876p-8259-xjggReference added —https://github.com/quic-go/quic-go/pull/4012Reference added —https://nrdax.com/techniques/NRDAX-T0205-pre-handshake-crypto-cpu-burnReference removed https://github.com/golang/go/commit/2350afd2e8ab054390e284c95d5b089c142db017—Reference removed https://github.com/golang/go/issues/61460—Reference removed https://github.com/libp2p/go-libp2p/commit/0cce607219f3710addc7e18672cffd1f1d912fbb—Reference removed https://github.com/libp2p/go-libp2p/commit/445be526aea4ee0b1fa5388aa65d32b2816d3a00—Reference removed https://github.com/libp2p/go-libp2p/commit/e30fcf7dfd4715ed89a5e68d7a4f774d3b9aa92d—Reference removed https://github.com/libp2p/go-libp2p/pull/2454—Reference removed https://github.com/libp2p/go-libp2p/security/advisories/GHSA-876p-8259-xjgg—Reference removed https://github.com/quic-go/quic-go/pull/4012—Reference type removed https://github.com/golang/go/commit/2350afd2e8ab054390e284c95d5b089c142db017 Types: Not Applicable, Patch—Reference type removed https://github.com/golang/go/issues/61460 Types: Issue Tracking, Not Applicable, Vendor Advisory—Reference type removed https://github.com/libp2p/go-libp2p/commit/0cce607219f3710addc7e18672cffd1f1d912fbb Types: Patch—Reference type removed https://github.com/libp2p/go-libp2p/commit/445be526aea4ee0b1fa5388aa65d32b2816d3a00 Types: Patch—Reference type removed https://github.com/libp2p/go-libp2p/commit/e30fcf7dfd4715ed89a5e68d7a4f774d3b9aa92d Types: Patch—Reference type removed https://github.com/libp2p/go-libp2p/pull/2454 Types: Exploit, Patch, Vendor Advisory—Reference type removed https://github.com/libp2p/go-libp2p/security/advisories/GHSA-876p-8259-xjgg Types: Patch, Vendor Advisory—Reference type removed https://github.com/quic-go/quic-go/pull/4012 Types: Patch, Third Party Advisory—Source identifier: security-advisories@github.com
Record modifiedCVE Program
New references:- https://github.com/golang/go/commit/2350afd2e8ab054390e284c95d5b089c142db017
- https://github.com/golang/go/issues/61460
- https://github.com/libp2p/go-libp2p/commit/0cce607219f3710addc7e18672cffd1f1d912fbb
- https://github.com/libp2p/go-libp2p/commit/445be526aea4ee0b1fa5388aa65d32b2816d3a00
and 4 more references
Show 24 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://github.com/golang/go/commit/2350afd2e8ab054390e284c95d5b089c142db017Reference added —https://github.com/golang/go/issues/61460Reference added —https://github.com/libp2p/go-libp2p/commit/0cce607219f3710addc7e18672cffd1f1d912fbbReference added —https://github.com/libp2p/go-libp2p/commit/445be526aea4ee0b1fa5388aa65d32b2816d3a00Reference added —https://github.com/libp2p/go-libp2p/commit/e30fcf7dfd4715ed89a5e68d7a4f774d3b9aa92dReference added —https://github.com/libp2p/go-libp2p/pull/2454Reference added —https://github.com/libp2p/go-libp2p/security/advisories/GHSA-876p-8259-xjggReference added —https://github.com/quic-go/quic-go/pull/4012Reference removed https://github.com/golang/go/commit/2350afd2e8ab054390e284c95d5b089c142db017—Reference removed https://github.com/golang/go/issues/61460—Reference removed https://github.com/libp2p/go-libp2p/commit/0cce607219f3710addc7e18672cffd1f1d912fbb—Reference removed https://github.com/libp2p/go-libp2p/commit/445be526aea4ee0b1fa5388aa65d32b2816d3a00—Reference removed https://github.com/libp2p/go-libp2p/commit/e30fcf7dfd4715ed89a5e68d7a4f774d3b9aa92d—Reference removed https://github.com/libp2p/go-libp2p/pull/2454—Reference removed https://github.com/libp2p/go-libp2p/security/advisories/GHSA-876p-8259-xjgg—Reference removed https://github.com/quic-go/quic-go/pull/4012—Reference type removed https://github.com/golang/go/commit/2350afd2e8ab054390e284c95d5b089c142db017 Types: Not Applicable, Patch—Reference type removed https://github.com/golang/go/issues/61460 Types: Issue Tracking, Not Applicable, Vendor Advisory—Reference type removed https://github.com/libp2p/go-libp2p/commit/0cce607219f3710addc7e18672cffd1f1d912fbb Types: Patch—Reference type removed https://github.com/libp2p/go-libp2p/commit/445be526aea4ee0b1fa5388aa65d32b2816d3a00 Types: Patch—Reference type removed https://github.com/libp2p/go-libp2p/commit/e30fcf7dfd4715ed89a5e68d7a4f774d3b9aa92d Types: Patch—Reference type removed https://github.com/libp2p/go-libp2p/pull/2454 Types: Exploit, Patch, Vendor Advisory—Reference type removed https://github.com/libp2p/go-libp2p/security/advisories/GHSA-876p-8259-xjgg Types: Patch, Vendor Advisory—Reference type removed https://github.com/quic-go/quic-go/pull/4012 Types: Patch, Third Party Advisory—Source identifier: af854a3a-2127-422b-91ae-364da2661108
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2023-39533"><img src="https://intel.neosec.eu/badge/cve/CVE-2023-39533.svg?lang=en" alt="CVE-2023-39533 – NEOSEC Intel" height="20"></a>