CVE-2024-32867
📋 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
- Suricata IDS/IPS
📦 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.
🎯 Exploit Status
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
allConfigure 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
- https://github.com/OISF/suricata/commit/1e110d0a71db46571040b937e17a4bc9f91d6de9
- https://github.com/OISF/suricata/commit/2f39ba75f153ba9bdf8eedc2a839cc973dbaea66
- https://github.com/OISF/suricata/commit/414f97c6695c5a2e1d378a36a6f50d7288767634
- https://github.com/OISF/suricata/commit/bf3d420fb709ebe074019a99e3bd3a2364524a4b
- https://github.com/OISF/suricata/commit/d13bd2ae217a6d2ceb347f74d27cbfcd37b9bda9
- https://github.com/OISF/suricata/commit/e6267758ed5da27f804f0c1c07f9423bdf4d72b8
- https://github.com/OISF/suricata/security/advisories/GHSA-xvrx-88mv-xcq5
- https://redmine.openinfosecfoundation.org/issues/6672
- https://redmine.openinfosecfoundation.org/issues/6673
- https://redmine.openinfosecfoundation.org/issues/6677
- https://github.com/OISF/suricata/commit/1e110d0a71db46571040b937e17a4bc9f91d6de9
- https://github.com/OISF/suricata/commit/2f39ba75f153ba9bdf8eedc2a839cc973dbaea66
- https://github.com/OISF/suricata/commit/414f97c6695c5a2e1d378a36a6f50d7288767634
- https://github.com/OISF/suricata/commit/bf3d420fb709ebe074019a99e3bd3a2364524a4b
- https://github.com/OISF/suricata/commit/d13bd2ae217a6d2ceb347f74d27cbfcd37b9bda9
- https://github.com/OISF/suricata/commit/e6267758ed5da27f804f0c1c07f9423bdf4d72b8
- https://github.com/OISF/suricata/security/advisories/GHSA-xvrx-88mv-xcq5
- https://redmine.openinfosecfoundation.org/issues/6672
- https://redmine.openinfosecfoundation.org/issues/6673
- https://redmine.openinfosecfoundation.org/issues/6677