# CVE-2018-19800: aubio Buffer Overflow vulnerability

> A buffer overflow in the aubio library allows attackers to execute arbitrary code or cause a denial of service via crafted audio data.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 7 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** CVE-2019-1010223, DEBIAN-CVE-2018-19800, GHSA-grmf-4fq6-2r79, PYSEC-2019-162, UBUNTU-CVE-2018-19800

## What is CVE-2018-19800?

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

### Official description

aubio v0.4.0 to v0.4.8 has a Buffer Overflow in new_aubio_tempo.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

3 open source packages ship an affected version, including aubio. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `aubio` | PyPI | From 0.4.0 | 0.4.9 |
| `aubio` | PyPI | From 0.4.0 | 0.4.9 |
| `aubio` | PyPI | From 0.4.0 | 0.4.9 |

Products: Aubio Aubio.

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

Upgrade aubio to 0.4.9 or later.

## Is CVE-2018-19800 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-14521](https://insights.sbomify.com/CVE-2018-14521/): Aubio is vulnerable to denial of service via aubio_source_avcodec_readframe function (high 8.8)
- [CVE-2018-14522](https://insights.sbomify.com/CVE-2018-14522/): Aubio is vulnerable to denial of service via aubio_pitch_set_unit function (high 8.8)
- [CVE-2018-14523](https://insights.sbomify.com/CVE-2018-14523/): Aubio is vulnerable to out of bound read when samplerate > 50kHz (high 8.8)
- [CVE-2018-19801](https://insights.sbomify.com/CVE-2018-19801/): Aubio is vulnerable to a NULL pointer dereference in new_aubio_filterbank (high 7.5)
- [CVE-2018-19802](https://insights.sbomify.com/CVE-2018-19802/): Aubio is vulnerable to a NULL pointer dereference in new_aubio_notes function (high 7.5)

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- aubio (PyPI): affected from 0.4.0; fixed in 0.4.9
- aubio (PyPI): affected from 0.4.0; fixed in 0.4.9
- aubio (PyPI): affected from 0.4.0; fixed in 0.4.9

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-19800/ (Markdown: https://insights.sbomify.com/CVE-2018-19800/index.md)
```

## Sources

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

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