# CVE-2015-3643: Missing authorization in n/a

> Local attackers can gain privileges in Ubuntu's usb-creator due to a missing authorization check in the KVMTest method.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/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:** 27 Sep 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xg32-vp89-8jq5, UBUNTU-CVE-2015-3643, USN-2576-1

## What is CVE-2015-3643?

CVE-2015-3643 is a high-severity missing authorization vulnerability in n/a, published on 27 Sep 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

usb-creator before 0.2.38.3ubuntu0.1 on Ubuntu 12.04 LTS, before 0.2.56.3ubuntu0.1 on Ubuntu 14.04 LTS, before 0.2.62ubuntu0.3 on Ubuntu 14.10, and before 0.2.67ubuntu0.1 on Ubuntu 15.04 allows local users to gain privileges by leveraging a missing call check_polkit for the KVMTest method.

Weakness: CWE-264

## Which versions are affected by CVE-2015-3643?

It affects 1 product.


Products: Usb-Creator Project Usb-Creator.

## How do I fix CVE-2015-3643?

Apply the vendor's patch.

## Is CVE-2015-3643 being exploited?

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

Public exploit code:

- usb-creator 0.2.x (Ubuntu 12.04/14.04/14.10) - Local Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-3643 and fix it if it is affected.

What it is: CVE-2015-3643 is a high-severity missing authorization vulnerability in n/a, published on 27 Sep 2017. 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-2015-3643 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-2015-3643/ (Markdown: https://insights.sbomify.com/CVE-2015-3643/index.md)
```

## Sources

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

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