CVE-2024-32867

5.3 MEDIUM

📋 TL;DR

This vulnerability in Suricata involves improper handling of IP fragmentation anomalies, which can cause the intrusion detection/prevention system to misapply security rules and policies. This affects all Suricata deployments prior to versions 7.0.5 and 6.0.19, potentially allowing attackers to evade detection or cause false positives.

💻 Affected Systems

Products:
  • Suricata IDS/IPS
Versions: All versions prior to 7.0.5 and 6.0.19
Operating Systems: All operating systems running Suricata
Default Config Vulnerable: ⚠️ Yes
Notes: All Suricata deployments using default or custom rulesets are affected when processing fragmented network traffic.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could bypass critical security rules, allowing malicious traffic to pass undetected through the IDS/IPS, potentially leading to successful network intrusions or data exfiltration.

🟠

Likely Case

Inconsistent rule matching causing either false negatives (missed attacks) or false positives (legitimate traffic blocked), reducing the effectiveness of network security monitoring.

🟢

If Mitigated

With proper segmentation and defense-in-depth, the impact is limited to potential evasion of Suricata's detection capabilities, but other security controls may still catch malicious activity.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires sending specially crafted fragmented network packets to trigger the anomaly handling issues.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 7.0.5 or 6.0.19

Vendor Advisory: https://github.com/OISF/suricata/releases

Restart Required: Yes

Instructions:

1. Download Suricata 7.0.5 or 6.0.19 from the official repository. 2. Stop the Suricata service. 3. Install the new version following your distribution's package management procedures. 4. Restart the Suricata service.

🔧 Temporary Workarounds

Disable IP Defragmentation

all

Configure Suricata to not reassemble fragmented IP packets, which prevents the vulnerability but reduces detection capability for fragmented attacks.

Set 'defrag: no' in suricata.yaml

🧯 If You Can't Patch

  • Implement network segmentation to limit exposure of vulnerable Suricata instances
  • Deploy additional network monitoring tools as compensating controls

🔍 How to Verify

Check if Vulnerable:

Check Suricata version with 'suricata --build-info' and compare to vulnerable versions (below 7.0.5 or 6.0.19)

Check Version:

suricata --build-info | grep 'Version:'

Verify Fix Applied:

After patching, verify version is 7.0.5 or higher (for 7.x branch) or 6.0.19 or higher (for 6.x branch)

📡 Detection & Monitoring

Log Indicators:

  • Unusual fragmentation patterns in network traffic logs
  • Rule matching anomalies in Suricata alert logs

Network Indicators:

  • Abnormal IP fragmentation patterns
  • Traffic that should trigger rules but doesn't

SIEM Query:

source="suricata" ("fragmentation" OR "anomaly") AND severity>=medium

🔗 References

📤 Share & Export