CVE-2017-1086: Infoleak
In FreeBSD before 11.1-STABLE, 11.1-RELEASE-p4, 11.0-RELEASE-p15, 10.4-STABLE, 10.4-RELEASE-p3, and 10.3-RELEASE-p24, not all information in the struct ptracelwpinfo is relevant for the state of any thread, and the kernel does not fill the irrelevant bytes or short strings. Since the structure filled by the kernel is allocated on the kernel stack and copied to userspace, a leak of information of the kernel stack of the thread is possible from the debugger. As a result, some bytes from the kernel stack of the thread using ptrace (PTLWPINFO) call can be observed in userspace.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2017-1086?
CVE-2017-1086 has been classified as medium severity due to potential information disclosure risks.
How do I fix CVE-2017-1086?
To fix CVE-2017-1086, you should update your FreeBSD installation to a version that includes the relevant patches.
What versions of FreeBSD are affected by CVE-2017-1086?
CVE-2017-1086 affects FreeBSD versions before 11.1-STABLE, 11.1-RELEASE-p4, 11.0-RELEASE-p15, 10.4-STABLE, 10.4-RELEASE-p3, and 10.3-RELEASE-p24.
What are the potential impacts of CVE-2017-1086?
The potential impacts of CVE-2017-1086 include unauthorized information disclosure from memory leaks in the kernel.
Is CVE-2017-1086 a remote exploit?
CVE-2017-1086 is not classified as a remote exploit, as it requires local access to the affected FreeBSD system.