Security readout for executives and security teams
Plain-English summary
This is a critical memory-safety flaw in miniupnp that could expose sensitive data or corrupt memory. The sources specifically call out Bitcoin Core before 0.12 and say remote code execution was possible there when combined with CVE-2015-6031.
Executive priority
Treat as urgent for legacy or embedded miniupnp environments, especially old Bitcoin Core nodes. Prioritize inventory first, because the public affected-product list is incomplete.
Technical view
miniupnp before commit 4c90b87 did not check snprintf return values, leading to buffer overflow and significant data leakage. The CVE distinguishes this from CVE-2019-12107. In Bitcoin Core before 0.12, impact could reach remote code execution only in conjunction with CVE-2015-6031.
Likely exposure
Exposure is most likely in legacy software embedding miniupnp code before commit 4c90b87, especially Bitcoin Core versions before 0.12. The source data does not enumerate all downstream affected products, so asset owners should verify embedded miniupnp usage.
Exploitation context
The provided data does not show CISA KEV listing or confirmed active exploitation. The highest-impact scenario cited is Bitcoin Core before 0.12 where remote code execution was possible when chained with CVE-2015-6031.
Researcher notes
The key evidence is the unchecked snprintf handling fixed by miniupnp commit 4c90b87 and Bitcoin Core’s disclosure tying older Bitcoin Core impact to CVE-2015-6031 chaining. Downstream product scope remains under-specified in the supplied sources.
Mitigation direction
- Upgrade Bitcoin Core deployments older than 0.12.
- Update embedded miniupnp code to include commit 4c90b87 or later vendor fixes.
- Inventory products that bundle miniupnp rather than relying only on package names.
- Check vendor advisories for downstream products using miniupnp.
- Disable unnecessary UPnP functionality where vendor guidance supports doing so.
Validation and detection
- Identify any Bitcoin Core versions older than 0.12.
- Review SBOMs and source bundles for embedded miniupnp copies.
- Confirm miniupnp code includes commit 4c90b87 or equivalent changes.
- Check whether UPnP features are enabled in affected deployments.
- Document downstream products where miniupnp version cannot be confirmed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-120: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2015-20111 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_ExposuresCVE reference
- https://bitcoincore.org/en/2024/07/03/disclose_upnp_rce/CVE reference
- https://github.com/miniupnp/miniupnp/pull/157CVE reference
- https://github.com/miniupnp/miniupnp/commit/4c90b87ce3d2517097880279e8c3daa7731100e6CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.