CVE-2017-6964: High severity Canonical Ubuntu Linux vulnerability
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/ejectto a version that resolves this vulnerability.Fixed in 2.1.5+deb1+cvs20081104-13.2
Event History
Frequently Asked Questions
What is the severity of CVE-2017-6964?
CVE-2017-6964 is considered to be of medium severity due to the potential for privilege escalation.
How do I fix CVE-2017-6964?
To fix CVE-2017-6964, update the eject package to version 2.1.5+deb1+cvs20081104-13.2 or later.
Which operating systems are affected by CVE-2017-6964?
CVE-2017-6964 affects Debian 8.0 and Ubuntu LTS versions 12.04, 14.04, 16.04, and 16.10.
What can attackers do with CVE-2017-6964?
Attackers can exploit CVE-2017-6964 to execute code as root while running dmcrypt-get-device.
Is there a workaround for CVE-2017-6964?
The recommended approach is to upgrade the affected packages since no specific workaround is available.