LiveActive security incident?Get immediate response
CVE Record

CVE-2023-37192: Memory management and protection issues in Bitcoin Core v22 allows attackers to modify the stored sending a...

Memory management and protection issues in Bitcoin Core v22 allows attackers to modify the stored sending address within the app's memory, potentially allowing them to redirect Bitcoin transactions to wallets of their own choosing.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

The CVE record claims Bitcoin Core v22 may allow memory tampering that changes a stored recipient address, potentially redirecting Bitcoin transactions. The public bundle does not provide CVSS, CWE, confirmed affected CPEs, vendor advisory details, or a named fix, so urgency should be based on confirmed local use of Bitcoin Core v22.

Executive priority

Prioritize verification over emergency action. If Bitcoin Core v22 is used for real funds, apply compensating controls immediately and seek official guidance, because the alleged impact is direct financial redirection but the evidence is incomplete.

Technical view

CVE-2023-37192 is described as a memory management and protection issue in Bitcoin Core v22 affecting stored sending address integrity. The evidence bundle is sparse and includes generic Bitcoin Core, blog, and YouTube references, with no structured vulnerability details, patch statement, or validated exploit conditions.

Likely exposure

Exposure is most relevant where Bitcoin Core v22 is used to prepare or send transactions. The bundle lists affected vendor and product as n/a, so teams should verify actual software versions rather than assuming broad Bitcoin Core exposure.

Exploitation context

The CVE is not listed as KEV in the provided bundle. No cited source in the bundle confirms active exploitation, weaponized exploit availability, or exploitation prerequisites. Treat public claims cautiously until vendor or maintainer guidance confirms impact.

Researcher notes

The record lacks CVSS, CWE, CPE, technical detail, and remediation metadata. The main analytical value is triage: confirm product/version use, assess transaction-address integrity controls, and watch for stronger maintainer or CNA clarification.

Mitigation direction

  • Inventory systems and workflows using Bitcoin Core v22.
  • Check official Bitcoin Core guidance before assuming a patched version.
  • Require independent recipient-address verification for high-value transactions.
  • Restrict transaction signing to trusted, hardened systems.
  • Monitor CVE and Bitcoin Core sources for clarification.

Validation and detection

  • Confirm whether Bitcoin Core v22 is installed or used operationally.
  • Review wallet workflows for recipient address verification controls.
  • Check transaction-signing hosts for unauthorized memory-access tooling.
  • Compare local versions against official Bitcoin Core release guidance.
  • Document uncertainty where vendor confirmation is unavailable.
Prepared
Confidence
low
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cve · low confidence lookup

CVE-2023-37192 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.