# CVE-2024-55629: Suricata generic detection bypass using TCP urgent support

> Attackers can bypass Suricata detection by using TCP urgent data, causing the IDS to analyze traffic differently than endpoints.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Jan 2025
- **Updated:** 6 Jan 2025
- **Also known as:** DEBIAN-CVE-2024-55629, GHSA-69wr-vhwg-84h2, UBUNTU-CVE-2024-55629

## What is CVE-2024-55629?

CVE-2024-55629 is a high-severity vulnerability in Oisf Suricata, published on 6 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-436 (Interpretation Conflict), CWE-437 (Incomplete Model of Endpoint Features)

## Which versions are affected by CVE-2024-55629?

It affects 1 product.


Products: Oisf Suricata.

## How do I fix CVE-2024-55629?

Upgrade to a fixed version.

## Is CVE-2024-55629 being exploited?

There is no known exploitation of CVE-2024-55629 in the wild and no public exploit code.

## Other vulnerabilities in Oisf Suricata

- [CVE-2023-35853](https://insights.sbomify.com/CVE-2023-35853/): Code injection in n/a (critical 9.8)
- [CVE-2021-37592](https://insights.sbomify.com/CVE-2021-37592/): Other in n/a (critical 9.8)
- [CVE-2018-10244](https://insights.sbomify.com/CVE-2018-10244/): Integer overflow in n/a (critical 9.8)
- [CVE-2026-94083](https://insights.sbomify.com/CVE-2026-94083/): Memory corruption in Suricata (critical 9.4)
- [CVE-2026-94084](https://insights.sbomify.com/CVE-2026-94084/): Use after free in Suricata (critical 9.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-55629 and fix it if it is affected.

What it is: CVE-2024-55629 is a high-severity vulnerability in Oisf Suricata, published on 6 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-55629 in the wild and no public exploit code.

Affected product: Oisf Suricata. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-55629/ (Markdown: https://insights.sbomify.com/CVE-2024-55629/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-55629
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-55629
- OSV: https://osv.dev/vulnerability/CVE-2024-55629

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-55629/
Summaries are generated and may contain mistakes; the official description above is the record.