# CVE-2019-10054: Null dereference in n/a

> An attacker can cause a denial of service in Suricata by triggering an invalid memory access due to missing length checks in NFS reply processing.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 28 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-10054, GHSA-wm52-jfxr-m7x9, UBUNTU-CVE-2019-10054

## What is CVE-2019-10054?

CVE-2019-10054 is a high-severity vulnerability in n/a, published on 28 Aug 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.3. The function process_reply_record_v3 lacks a check for the length of reply.data. It causes an invalid memory access and the program crashes within the nfs/nfs3.rs file.

Weakness: CWE-20 (Improper Input Validation), CWE-191 (Integer Underflow (Wrap or Wraparound))

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

It affects 1 product.


Products: Suricata-Ids Suricata.

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

Upgrade to a fixed version.

## Is CVE-2019-10054 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-16411](https://insights.sbomify.com/CVE-2019-16411/): Memory corruption in n/a (critical 9.8)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10054 is a high-severity vulnerability in n/a, published on 28 Aug 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-10054 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-10054/ (Markdown: https://insights.sbomify.com/CVE-2019-10054/index.md)
```

## Sources

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

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