# CVE-2018-19840: Denial of service in n/a

> Attackers can cause denial of service via infinite loop in WavPack library when processing crafted audio files with zero sample rate.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2018-19840, DEBIAN-CVE-2018-19840, GHSA-5xqp-7g33-7hx3, SUSE-SU-2019:13990-1, SUSE-SU-2020:2727-1, UBUNTU-CVE-2018-19840

## What is CVE-2018-19840?

CVE-2018-19840 is a medium-severity denial of service vulnerability in Canonical Ubuntu Linux, published on 4 Dec 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The function WavpackPackInit in pack_utils.c in libwavpack.a in WavPack through 5.1.0 allows attackers to cause a denial-of-service (resource exhaustion caused by an infinite loop) via a crafted wav audio file because WavpackSetConfiguration64 mishandles a sample rate of zero.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

## Which versions are affected by CVE-2018-19840?

It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wavpack` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 4.50.1-1.30.1 |
| `wavpack` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 4.60.99-5.6.3 |
| `wavpack` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 4.50.1-1.30.1 |
| `wavpack` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 4.60.99-5.6.3 |
| `wavpack` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 4.50.1-1.30.1 |
| `wavpack` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 4.60.99-5.6.3 |

Products: Canonical Ubuntu Linux, Fedoraproject Fedora, Opensuse Leap, Wavpack Wavpack.

## How do I fix CVE-2018-19840?

Apply the vendor's patch.

## Is CVE-2018-19840 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-19840 and fix it if it is affected.

What it is: CVE-2018-19840 is a medium-severity denial of service vulnerability in Canonical Ubuntu Linux, published on 4 Dec 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-19840 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. 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-2018-19840/ (Markdown: https://insights.sbomify.com/CVE-2018-19840/index.md)
```

## Sources

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

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