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

> A race condition in snapd allows local attackers to gain unintended access to private temporary directories, potentially leading to privilege escalation.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-11502, GHSA-hhc7-jq5j-875q, UBUNTU-CVE-2019-11502

## What is CVE-2019-11502?

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

### Official description

snap-confine in snapd before 2.38 incorrectly set the ownership of a snap application to the uid and gid of the first calling user. Consequently, that user had unintended access to a private /tmp directory.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

It affects 1 product.


Products: Canonical Snapd.

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

Upgrade to a fixed version.

## Is CVE-2019-11502 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-1523](https://insights.sbomify.com/CVE-2023-1523/): Command injection in snapd (critical 10.0)
- [CVE-2020-27352](https://insights.sbomify.com/CVE-2020-27352/): Privilege escalation in snapd (critical 9.3)
- [CVE-2019-7304](https://insights.sbomify.com/CVE-2019-7304/): Local privilege escalation via snapd socket (high 8.8)
- [CVE-2021-4120](https://insights.sbomify.com/CVE-2021-4120/): snapd could be made to bypass intended access restrictions through snap content interfaces and layout paths (high 8.2)
- [CVE-2024-5138](https://insights.sbomify.com/CVE-2024-5138/): CVE-2024-5138: snapd snapctl auth bypass (high 8.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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