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

> A NULL pointer dereference in SoX allows attackers to cause a denial of service via crafted audio files.

- **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:** 15 Feb 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-8357, GHSA-qmr3-6jfh-4h6m, UBUNTU-CVE-2019-8357

## What is CVE-2019-8357?

CVE-2019-8357 is a medium-severity vulnerability in n/a, published on 15 Feb 2019. 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

An issue was discovered in SoX 14.4.2. lsx_make_lpf in effect_i_dsp.c allows a NULL pointer dereference.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Sound Exchange Project Sound Exchange.

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

Apply the vendor's patch.

## Is CVE-2019-8357 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-40426](https://insights.sbomify.com/CVE-2021-40426/): Memory corruption in libsox (critical 10.0)
- [CVE-2021-3643](https://insights.sbomify.com/CVE-2021-3643/): Information disclosure in sox (critical 9.1)
- [CVE-2021-23159](https://insights.sbomify.com/CVE-2021-23159/): Memory corruption in SoX (Sound eXchange) (medium 5.5)
- [CVE-2021-23172](https://insights.sbomify.com/CVE-2021-23172/): Memory corruption in SoX (Sound eXchange) (medium 5.5)
- [CVE-2021-23210](https://insights.sbomify.com/CVE-2021-23210/): Denial of service in SoX (Sound eXchange) (medium 5.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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