CVE-2024-52912

7.5 HIGH

📋 TL;DR

This vulnerability in Bitcoin Core allows attackers to cause a network split by exploiting an integer overflow when calculating time offsets for new peers. It affects all Bitcoin Core nodes running vulnerable versions, potentially disrupting network consensus and transaction validation.

💻 Affected Systems

Products:
  • Bitcoin Core
Versions: All versions before 0.21.0
Operating Systems: All platforms running Bitcoin Core
Default Config Vulnerable: ⚠️ Yes
Notes: All Bitcoin Core nodes with default configurations are vulnerable if running affected versions.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete network partition where different segments of the Bitcoin network operate with different transaction histories, enabling double-spend attacks and undermining blockchain integrity.

🟠

Likely Case

Temporary network instability, increased orphaned blocks, and potential short-term consensus issues among affected nodes.

🟢

If Mitigated

Minor network latency or connection issues that self-correct as nodes reconnect with proper time synchronization.

🌐 Internet-Facing: HIGH
🏢 Internal Only: LOW

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

Exploitation requires network-level access to target nodes and understanding of Bitcoin peer-to-peer protocol.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Bitcoin Core 0.21.0 and later

Vendor Advisory: https://bitcoincore.org/en/2024/07/03/disclose-timestamp-overflow/

Restart Required: Yes

Instructions:

1. Download Bitcoin Core 0.21.0 or later from bitcoincore.org. 2. Stop the Bitcoin Core service. 3. Install the new version. 4. Restart Bitcoin Core.

🔧 Temporary Workarounds

Restrict Peer Connections

all

Limit incoming peer connections to trusted nodes only

bitcoin-cli setban 0.0.0.0/0 add
bitcoin-cli addnode <trusted_node_ip> add

🧯 If You Can't Patch

  • Implement strict network ACLs to limit peer connections to known trusted nodes only
  • Monitor for unusual network partition events and node disconnections

🔍 How to Verify

Check if Vulnerable:

Check Bitcoin Core version: bitcoin-cli getnetworkinfo | grep version

Check Version:

bitcoin-cli getnetworkinfo | grep version

Verify Fix Applied:

Confirm version is 0.21.0 or higher and monitor for stable peer connections

📡 Detection & Monitoring

Log Indicators:

  • Unusual time offset warnings in debug.log
  • Multiple peer disconnections in short timeframes
  • Network partition warnings

Network Indicators:

  • Sudden drop in connected peers
  • Increased orphaned blocks
  • Inconsistent blockchain height across nodes

SIEM Query:

source="bitcoin.log" AND ("time offset" OR "peer disconnected" OR "network split")

🔗 References

📤 Share & Export