# CVE-2017-6964: Privilege escalation in n/a

> A failure to check setuid/setgid return values in dmcrypt-get-device allows local attackers to execute code as root, requiring OS package updates.

- **Severity:** High 7.8 (`CVSS:3.1/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:** 28 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DLA-876-1, DSA-3823-1, GHSA-h47x-xw68-3m46, UBUNTU-CVE-2017-6964, USN-3246-1

## What is CVE-2017-6964?

CVE-2017-6964 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 28 Mar 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

dmcrypt-get-device, as shipped in the eject package of Debian and Ubuntu, does not check the return value of the (1) setuid or (2) setgid function, which might cause dmcrypt-get-device to execute code, which was intended to run as an unprivileged user, as root. This affects eject through 2.1.5+deb1+cvs20081104-13.1 on Debian, eject before 2.1.5+deb1+cvs20081104-13.1ubuntu0.16.10.1 on Ubuntu 16.10, eject before 2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1 on Ubuntu 16.04 LTS, eject before 2.1.5+deb1+cvs20081104-13.1ubuntu0.14.04.1 on Ubuntu 14.04 LTS, and eject before 2.1.5+deb1+cvs20081104-9ubuntu0.1 on Ubuntu 12.04 LTS.

Weakness: CWE-252 (Unchecked Return Value)

## Which versions are affected by CVE-2017-6964?

It affects 2 products.


Products: Canonical Ubuntu Linux, Debian Debian Linux.

## How do I fix CVE-2017-6964?

Apply the vendor's patch.

## Is CVE-2017-6964 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6964 and fix it if it is affected.

What it is: CVE-2017-6964 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 28 Mar 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-2017-6964 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. 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-2017-6964/ (Markdown: https://insights.sbomify.com/CVE-2017-6964/index.md)
```

## Sources

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

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