CVE-2019-16411 Memory corruption in n/a

Critical 9.8 Published Updated

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

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

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

Which versions are affected by CVE-2019-16411?

It affects 1 product.

Products include Suricata-Ids Suricata.

How do I fix CVE-2019-16411?

Apply the vendor's patch.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2019-16411 being exploited?

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

Sources

Also known as DEBIAN-CVE-2019-16411, GHSA-wrwg-3wxg-wppx, UBUNTU-CVE-2019-16411.

Is CVE-2019-16411 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free