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

> Attackers can crash the rpcapd daemon via a NULL pointer dereference when a crypt() call fails, causing denial of service.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2019-15163, DEBIAN-CVE-2019-15163, GHSA-8f74-v8w6-4296

## What is CVE-2019-15163?

CVE-2019-15163 is a high-severity vulnerability in n/a, published on 3 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

rpcapd/daemon.c in libpcap before 1.9.1 allows attackers to cause a denial of service (NULL pointer dereference and daemon crash) if a crypt() call fails.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Tcpdump Libpcap.

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

Upgrade to a fixed version.

## Is CVE-2019-15163 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-1935](https://insights.sbomify.com/CVE-2011-1935/): Information disclosure in n/a (critical 9.8)
- [CVE-2019-15161](https://insights.sbomify.com/CVE-2019-15161/): Integer overflow in n/a (medium 5.3)
- [CVE-2019-15162](https://insights.sbomify.com/CVE-2019-15162/): Information disclosure in n/a (medium 5.3)
- [CVE-2019-15164](https://insights.sbomify.com/CVE-2019-15164/): Server-side request forgery in n/a (medium 5.3)
- [CVE-2023-7256](https://insights.sbomify.com/CVE-2023-7256/): Double-free in libpcap before 1.10.5 with remote packet capture support. (medium 4.4)

## Fix prompt for AI coding agents

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

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

## Sources

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

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