# CVE-2019-13351: Race condition in n/a

> A race condition in JACK2 allows attackers to cause crashes, information disclosure, or file corruption via double file descriptor closure.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/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:** 5 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-13351, GHSA-cjwm-ffg5-vxwh, MGASA-2020-0476, UBUNTU-CVE-2019-13351, USN-5656-1

## What is CVE-2019-13351?

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

### Official description

posix/JackSocket.cpp in libjack in JACK2 1.9.1 through 1.9.12 (as distributed with alsa-plugins 1.1.7 and later) has a "double file descriptor close" issue during a failed connection attempt when jackd2 is not running. Exploitation success depends on multithreaded timing of that double close, which can result in unintended information disclosure, crashes, or file corruption due to having the wrong file associated with the file descriptor.

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

It affects 2 products.


Products: Alsa-Project Alsa, Jackaudio Jack2.

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

Apply the vendor's patch.

## Is CVE-2019-13351 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-0035](https://insights.sbomify.com/CVE-2009-0035/): Path traversal in alsa-driver (medium 5.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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