CVE-2024-38365

HIGHNVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 37% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.4Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

btcd is an alternative full node bitcoin implementation written in Go (golang). The btcd Bitcoin client (versions 0.10 to 0.24) did not correctly re-implement Bitcoin Core's "FindAndDelete()" functionality. This logic is consensus-critical: the difference in behavior with the other Bitcoin clients can lead to btcd clients accepting an invalid Bitcoin block (or rejecting a valid one). This consensus failure can be leveraged to cause a chain split (accepting an invalid Bitcoin block) or be exploited to DoS the btcd nodes (rejecting a valid Bitcoin block). An attacker can create a standard transaction where FindAndDelete doesn't return a match but removeOpCodeByData does making btcd get a different sighash, leading to a chain split. Importantly, this vulnerability can be exploited remotely by any Bitcoin user and does not require any hash power. This is because the difference in behavior can be triggered by a "standard" Bitcoin transaction, that is a transaction which gets relayed through the P2P network before it gets included in a Bitcoin block. removeOpcodeByData(script []byte, dataToRemove []byte) removes any data pushes from script that contain dataToRemove. However, FindAndDelete only removes exact matches. So for example, with script = " " and dataToRemove = "data" btcd will remove both data pushes but Bitcoin Core's FindAndDelete only removes the first `` push. This has been patched in btcd version v0.24.2. Users are advised to upgrade. There are no known workarounds for this issue.

CVSS v3
7.4
EG Score
7.4(medium)
EPSS
59.4%
KEV
Not listed

Published

October 11, 2024

Last Modified

August 20, 2025

References (4)

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/btcsuite/btcd—0.24.2-beta.rc1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 42× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:26 UTCEPSS rescore
  2. 2026-07-11 08:26 UTCEPSS rescore
  3. 2026-07-09 19:09 UTCEPSS rescore
  4. 2026-07-08 15:14 UTCEPSS rescore
  5. 2026-07-08 15:13 UTCEPSS rescore
  6. 2026-07-07 13:45 UTCEPSS rescore
  7. 2026-07-06 16:26 UTCEPSS rescore
  8. 2026-07-06 02:22 UTCEPSS rescore
  9. 2026-07-06 02:22 UTCEPSS rescore
  10. 2026-07-05 02:29 UTCEPSS rescore
  11. 2026-07-04 06:30 UTCEPSS rescore
  12. 2026-07-01 15:05 UTCEPSS rescore
  13. 2026-06-28 14:06 UTCEPSS rescore
  14. 2026-06-28 14:06 UTCEPSS rescore
  15. 2026-06-28 04:55 UTCEPSS rescore
  16. 2026-06-28 04:55 UTCEPSS rescore
  17. 2026-06-27 03:07 UTCEPSS rescore
  18. 2026-06-27 03:07 UTCEPSS rescore
  19. 2026-06-25 21:16 UTCOSV refresh
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-24 14:04 UTCEPSS rescore
  22. 2026-06-24 14:04 UTCEPSS rescore
  23. 2026-06-23 21:32 UTCEPSS rescore
  24. 2026-06-23 21:32 UTCEPSS rescore
  25. 2026-06-22 14:25 UTCEPSS rescore
Show 52 more
  1. 2026-06-22 14:25 UTCEPSS rescore
  2. 2026-06-21 14:55 UTCEPSS rescore
  3. 2026-06-21 14:55 UTCEPSS rescore
  4. 2026-06-21 01:58 UTCEPSS rescore
  5. 2026-06-21 01:58 UTCEPSS rescore
  6. 2026-06-19 19:25 UTCEPSS rescore
  7. 2026-06-19 19:25 UTCEPSS rescore
  8. 2026-06-18 17:52 UTCEPSS rescore
  9. 2026-06-18 17:51 UTCEPSS rescore
  10. 2026-06-17 17:52 UTCEPSS rescore
  11. 2026-06-16 17:52 UTCEPSS rescore
  12. 2026-06-16 17:52 UTCEPSS rescore
  13. 2026-06-15 17:47 UTCEPSS rescore
  14. 2026-06-14 23:16 UTCEPSS rescore
  15. 2026-06-13 22:59 UTCEPSS rescore
  16. 2026-06-13 22:59 UTCEPSS rescore
  17. 2026-06-12 23:11 UTCEPSS rescore
  18. 2026-06-11 13:59 UTCEPSS rescore
  19. 2026-06-10 22:17 UTCEPSS rescore
  20. 2026-06-10 13:21 UTCEPSS rescore
  21. 2026-06-08 14:16 UTCEPSS rescore
  22. 2026-06-08 10:28 UTCOSV refresh
  23. 2026-06-07 15:24 UTCEPSS rescore
  24. 2026-06-07 15:24 UTCEPSS rescore
  25. 2026-06-06 13:46 UTCEPSS rescore
  26. 2026-06-06 13:46 UTCEPSS rescore
  27. 2026-06-05 22:46 UTCEPSS rescore
  28. 2026-06-05 22:46 UTCEPSS rescore
  29. 2026-06-05 06:09 UTCEPSS rescore
  30. 2026-06-05 06:09 UTCEPSS rescore
  31. 2026-06-04 13:11 UTCEPSS rescore
  32. 2026-06-04 13:11 UTCEPSS rescore
  33. 2026-06-02 20:12 UTCEPSS rescore
  34. 2026-06-01 13:51 UTCEPSS rescore
  35. 2026-06-01 13:51 UTCEPSS rescore
  36. 2026-05-31 22:30 UTCEPSS rescore
  37. 2026-05-31 22:30 UTCEPSS rescore
  38. 2026-05-31 00:15 UTCEPSS rescore
  39. 2026-05-31 00:15 UTCEPSS rescore
  40. 2026-05-29 13:43 UTCEPSS rescore
  41. 2026-05-28 13:44 UTCEPSS rescore
  42. 2026-05-28 13:44 UTCEPSS rescore
  43. 2026-05-28 13:44 UTCEPSS rescore
  44. 2026-05-27 13:40 UTCEPSS rescore
  45. 2026-05-27 13:40 UTCEPSS rescore
  46. 2026-05-27 13:40 UTCEPSS rescore
  47. 2026-05-26 13:43 UTCEPSS rescore
  48. 2026-05-26 13:43 UTCEPSS rescore
  49. 2026-05-26 07:18 UTCEPSS rescore
  50. 2026-05-26 07:18 UTCEPSS rescore
  51. 2026-05-26 07:18 UTCEPSS rescore
  52. 2026-05-23 20:39 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-38365?
CVE-2024-38365 is a high vulnerability published on October 11, 2024. btcd is an alternative full node bitcoin implementation written in Go (golang). The btcd Bitcoin client (versions 0.10 to 0.24) did not correctly re-implement Bitcoin Core's "FindAndDelete()" functionality. This logic is consensus-critical: the difference in behavior with the other Bitcoin clients…
When was CVE-2024-38365 disclosed?
CVE-2024-38365 was first published in the National Vulnerability Database on October 11, 2024, with the most recent update on August 20, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-38365 actively exploited?
CVE-2024-38365 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 59.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-38365?
CVE-2024-38365 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2024-38365?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-38365, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-38365

Explore →

Is Your Infrastructure Affected by CVE-2024-38365?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs