Cloudanix VulnDB

CVE-2024-55629

None

CVSS

—

EPSS

0.5%

Published

Jan 6, 2025

CISA due date

—

Cloudanix analysis

Monitor only SSVC: Track

A network monitoring tool can be tricked by certain special data inside connections, letting some unwanted traffic pass without being noticed.

Chainable
Exploitation
Remote Unauthenticated
Attacker needs
None
Complexity
Low
Impact
Other
Component
Application
Class
Improper Input Validation
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

Suricata processes TCP streams containing urgent (out-of-band) data differently from the endpoint applications, allowing rule evasion in detection and prevention modes.

Why it matters to the business

Attackers may bypass network inspection controls, raising the chance that malicious traffic reaches internal systems undetected and increasing overall breach exposure in environments that rely on this engine.

How an attack unfolds

An attacker crafts TCP segments with the URG flag set so that Suricata interprets the stream differently than the destination host; the mismatch lets attack traffic avoid matching signatures or anomaly checks until the fix is applied.

How to fix it

Upgrade to Suricata 7.0.8 or apply commit 97e69ffb1bc2b7358115ee59f460a924893664e8. Configure the new urgent-data handling options and, in IPS mode, deploy rules such as drop tcp any any -> any any (sid:1; tcp.flags:U*;) to drop packets with the urgent flag when appropriate.

How to confirm the fix worked

Confirm the installed version is 7.0.8 or later, review the urgent-data configuration, and test with sample traffic containing the URG flag to verify expected handling and rule enforcement.

Typical attack path

  1. Identify a network path monitored by an unpatched Suricata instance
  2. Send TCP packets carrying the URG flag with a payload crafted to evade rules
  3. Rely on the engine's divergent stream processing to bypass detection or blocking
  4. Deliver follow-on malicious activity that would otherwise have been inspected

How to detect it

Search Suricata and network logs for TCP segments with the URG flag set; review any alerts or rule hits referencing tcp.flags:U*; examine configuration files for pre-7.0.8 urgent-data settings.

  • tcp.flags:U*
  • sid:1; tcp.flags:U*

What your security team should do

  • Upgrade all Suricata deployments to 7.0.8 or the referenced commit without delay
  • Enable and tune the new urgent-data configuration options to match endpoint behavior
  • Add or enable IPS rules that drop URG-flagged packets if urgent data is not required in the environment
  • Update detection content and run regression tests against evasion test cases

The record

Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. Prior to 7.0.8, TCP streams with TCP urgent data (out of band data) can lead to Suricata analyzing data differently than the applications at the TCP endpoints, leading to possible evasions. Suricata 7.0.8 includes options to allow users to configure how to handle TCP urgent data. In IPS mode, you can use a rule such as drop tcp any any -> any any (sid:1; tcp.flags:U*;) to drop all the packets with urgent flag set.

Affected packages

Ecosystem Package Introduced Fixed
Debian:11 suricata 0 No fix
Debian:12 suricata 0 No fix
Debian:13 suricata 0 1:7.0.8-1
Debian:14 suricata 0 1:7.0.8-1
Ubuntu:16.04:LTS suricata 0 No fix
Ubuntu:18.04:LTS suricata 0 No fix
Ubuntu:22.04:LTS suricata 0 No fix
Ubuntu:24.04:LTS suricata 0 No fix
Ubuntu:24.10 suricata 0 No fix
Ubuntu:Pro:16.04:LTS suricata 0 No fix
Ubuntu:Pro:18.04:LTS suricata 0 No fix
openSUSE:Tumbleweed suricata 0 8.0.0-1.1

Related vulnerabilities