# CVE-2024-38534: Suricata modbus: txs without responses are never freed


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 11 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** DEBIAN-CVE-2024-38534, GHSA-59qg-h357-69fq, UBUNTU-CVE-2024-38534

## What is CVE-2024-38534?

CVE-2024-38534 is a high-severity vulnerability in Oisf Suricata, published on 11 Jul 2024. 

### Official description

Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. Crafted modbus traffic can lead to unlimited resource accumulation within a flow. Upgrade to 7.0.6. Set a limited stream.reassembly.depth to reduce the issue.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 1 product.


Products: Oisf Suricata.

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

Upgrade to a fixed version.

## Is CVE-2024-38534 being exploited?

There is no known exploitation of CVE-2024-38534 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-38534 and fix it if it is affected.

What it is: CVE-2024-38534 is a high-severity vulnerability in Oisf Suricata, published on 11 Jul 2024. 
Exploitation: There is no known exploitation of CVE-2024-38534 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-38534/ (Markdown: https://insights.sbomify.com/CVE-2024-38534/index.md)
```

## Sources

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

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