CVE-2024-26369

7.5 HIGH

📋 TL;DR

A vulnerability in FastDDS's HistoryQosPolicy component causes a SIGABRT (abort signal) when receiving DataWriter data, leading to denial of service. This affects systems using FastDDS v2.6.x through v2.12.x for data distribution in real-time applications.

💻 Affected Systems

Products:
  • FastDDS (eProsima Fast DDS)
Versions: v2.6.x, v2.10.x, v2.11.x, v2.12.x
Operating Systems: All platforms running FastDDS
Default Config Vulnerable: ⚠️ Yes
Notes: Affects systems using HistoryQosPolicy with DataWriter communication.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete service disruption through repeated crashes, potentially affecting critical real-time systems like autonomous vehicles or industrial control.

🟠

Likely Case

Intermittent service interruptions and instability in DDS-based communication systems.

🟢

If Mitigated

Minimal impact with proper monitoring and restart mechanisms in place.

🌐 Internet-Facing: MEDIUM - Exploitable if DDS endpoints are exposed, but requires specific DDS traffic.
🏢 Internal Only: HIGH - Internal systems using FastDDS for critical communication are vulnerable to DoS.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW - Triggering requires sending specific DDS data packets.

Exploitation requires network access to DDS endpoints and knowledge of DDS protocol.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Fixed in FastDDS v2.13.0 and later versions

Vendor Advisory: https://github.com/eProsima/Fast-DDS/issues/4365

Restart Required: Yes

Instructions:

1. Update FastDDS to v2.13.0 or later. 2. Recompile applications using FastDDS. 3. Restart all FastDDS services.

🔧 Temporary Workarounds

Disable HistoryQosPolicy

all

Avoid using HistoryQosPolicy in vulnerable configurations if possible.

Modify DDS QoS configuration to use different policies

Network Segmentation

all

Restrict access to DDS endpoints to trusted systems only.

Configure firewall rules to limit DDS traffic (typically ports 7400-7410)

🧯 If You Can't Patch

  • Implement monitoring for SIGABRT signals and automatic restart mechanisms.
  • Isolate FastDDS systems in separate network segments with strict access controls.

🔍 How to Verify

Check if Vulnerable:

Check FastDDS version: if using v2.6.x, v2.10.x, v2.11.x, or v2.12.x, system is vulnerable.

Check Version:

fastdds --version or check package manager (e.g., dpkg -l | grep fastdds)

Verify Fix Applied:

Confirm FastDDS version is v2.13.0 or later and test DataWriter communication.

📡 Detection & Monitoring

Log Indicators:

  • SIGABRT signals in system logs
  • FastDDS process crashes
  • Error messages related to HistoryQosPolicy

Network Indicators:

  • Unusual DDS traffic patterns to DataWriter endpoints
  • Repeated connection attempts to DDS ports

SIEM Query:

process_name:"fastdds" AND signal:"SIGABRT"

🔗 References

📤 Share & Export