CVE-2022-29077

9.8 CRITICAL

📋 TL;DR

A heap-based buffer overflow vulnerability in rippled (XRPL server software) before version 1.8.5 allows remote attackers to crash nodes or potentially execute arbitrary commands. This affects all rippled nodes running vulnerable versions, potentially compromising XRPL network stability and digital assets.

💻 Affected Systems

Products:
  • rippled
Versions: All versions before 1.8.5
Operating Systems: Linux, Windows, macOS
Default Config Vulnerable: ⚠️ Yes
Notes: All rippled nodes with default configurations are vulnerable

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote code execution leading to full node compromise, XRPL mainnet denial of service, and theft of digital assets

🟠

Likely Case

Node crashes causing service disruption and potential ripple effects across the XRPL network

🟢

If Mitigated

Limited impact with proper network segmentation and monitoring, but still vulnerable to DoS

🌐 Internet-Facing: HIGH - rippled nodes are typically internet-facing and the exploit is unauthenticated
🏢 Internal Only: MEDIUM - internal nodes could still be targeted through lateral movement

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Heap buffer overflow vulnerabilities are frequently weaponized, though no public PoC is confirmed

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 1.8.5

Vendor Advisory: https://xrpl.org/blog/2022/rippled-1.8.5.html

Restart Required: Yes

Instructions:

1. Stop rippled service. 2. Backup configuration. 3. Install rippled 1.8.5 from official sources. 4. Restart rippled service. 5. Verify version and functionality.

🔧 Temporary Workarounds

Network Segmentation

linux

Restrict network access to rippled nodes using firewalls

iptables -A INPUT -p tcp --dport 51235 -s trusted_ip -j ACCEPT
iptables -A INPUT -p tcp --dport 51235 -j DROP

🧯 If You Can't Patch

  • Implement strict network ACLs to limit access to rippled nodes
  • Deploy intrusion detection systems to monitor for exploitation attempts

🔍 How to Verify

Check if Vulnerable:

Check rippled version with 'rippled --version' or 'rippled version'

Check Version:

rippled --version

Verify Fix Applied:

Confirm version is 1.8.5 or later and monitor for crashes/abnormal behavior

📡 Detection & Monitoring

Log Indicators:

  • Unexpected rippled crashes
  • Memory allocation errors in logs
  • Abnormal network traffic patterns

Network Indicators:

  • Unusual traffic to rippled port 51235
  • Multiple connection attempts from single sources

SIEM Query:

source="rippled.log" AND ("segmentation fault" OR "buffer overflow" OR "crash")

🔗 References

📤 Share & Export