# CVE-2019-16411: Memory corruption in n/a

> An attacker can cause a denial of service in Suricata by sending crafted IPv4 packets that trigger an out-of-bounds memory read.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-16411, GHSA-wrwg-3wxg-wppx, UBUNTU-CVE-2019-16411

## What is CVE-2019-16411?

CVE-2019-16411 is a critical memory corruption vulnerability in n/a, published on 24 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Suricata 4.1.4. By sending multiple IPv4 packets that have invalid IPv4Options, the function IPV4OptValidateTimestamp in decode-ipv4.c tries to access a memory region that is not allocated. There is a check for o->len < 5 (corresponding to 2 bytes of header and 3 bytes of data). Then, "flag = *(o->data + 3)" places one beyond the 3 bytes, because the code should have been "flag = *(o->data + 1)" instead.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2019-16411?

It affects 1 product.


Products: Suricata-Ids Suricata.

## How do I fix CVE-2019-16411?

Apply the vendor's patch.

## Is CVE-2019-16411 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-10053](https://insights.sbomify.com/CVE-2019-10053/): Integer overflow in n/a (critical 9.8)
- [CVE-2019-15699](https://insights.sbomify.com/CVE-2019-15699/): Memory corruption in n/a (critical 9.1)
- [CVE-2019-16410](https://insights.sbomify.com/CVE-2019-16410/): Null dereference in n/a (critical 9.1)
- [CVE-2019-10051](https://insights.sbomify.com/CVE-2019-10051/): Denial of service in n/a (high 7.5)
- [CVE-2019-10052](https://insights.sbomify.com/CVE-2019-10052/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-16411 and fix it if it is affected.

What it is: CVE-2019-16411 is a critical memory corruption vulnerability in n/a, published on 24 Sep 2019. 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-2019-16411 in the wild and no public exploit code.

Affected product: n/a. 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-2019-16411/ (Markdown: https://insights.sbomify.com/CVE-2019-16411/index.md)
```

## Sources

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

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