# CVE-2024-6714: Privilege escalation in Ubuntu Desktop Provision

> A local attacker can escalate privileges via a setuid binary in Ubuntu Desktop Provision's provd utility.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jul 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-x66j-2fj9-7c64, UBUNTU-CVE-2024-6714, USN-6912-1

## What is CVE-2024-6714?

CVE-2024-6714 is a high-severity vulnerability in Canonical Ltd. Ubuntu Desktop Provision, published on 23 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in provd before version 0.1.5 with a setuid binary, which allows a local attacker to escalate their privilege.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2024-6714?

It affects 1 product.


Products: Canonical Ubuntu Desktop Provision.

## How do I fix CVE-2024-6714?

Apply the vendor's patch.

## Is CVE-2024-6714 being exploited?

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

## Other vulnerabilities in Canonical Ltd. Ubuntu Desktop Provision

- [CVE-2025-15480](https://insights.sbomify.com/CVE-2025-15480/): Senstive information disclosure was affecting ubuntu-desktop-provision (low 2.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6714 and fix it if it is affected.

What it is: CVE-2024-6714 is a high-severity vulnerability in Canonical Ltd. Ubuntu Desktop Provision, published on 23 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-6714 in the wild and no public exploit code.

Affected product: Canonical Ltd. Ubuntu Desktop Provision. 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-2024-6714/ (Markdown: https://insights.sbomify.com/CVE-2024-6714/index.md)
```

## Sources

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

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