Skip to content
Fencer Vulns
high 7.5

CVE-2023-37192 json

Memory management and protection issues in Bitcoin Core v22 allows attackers to modify the stored sending address within the app's memory,…

published 2023-07-06 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-41112

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 47%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitcoin openSUSE Leap 16.0 27.1-bp160.2.1
  • bitcoin openSUSE Tumbleweed 31.0-2.1

opensuse advisories openSUSE-SU-2026:21149-1openSUSE-SU-2026:11073-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-37192 updated cvss 7.5

bitcoin-core: memory manipulation leading to transaction redirection

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
partial
Assessed
23 mo ago

Exploit prediction

0.57% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • satoshihunter1.blogspot.com https://satoshihunter1.blogspot.com/2023/06/the-bitcoin-app-is-vulnerable-to-hackers.html referenced PoC, tagged "exploit" by a source, unverified
  • youtube.com https://www.youtube.com/watch?v=oEl4M1oZim0 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Classification

Weakness
  • CWE-311 Missing Encryption of Sensitive Data

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.