First published: Fri Jul 13 2018(Updated: )
Improper bounds checking of the obuf variable in the link_ntoa() function in linkaddr.c of the BSD libc library may allow an attacker to read or write from memory. The full impact and severity depends on the method of exploit and how the library is used by applications. According to analysis by FreeBSD developers, it is very unlikely that applications exist that utilize link_ntoa() in an exploitable manner, and the CERT/CC is not aware of any proof of concept. A blog post describes the functionality of link_ntoa() and points out that none of the base utilities use this function in an exploitable manner. For more information, please see FreeBSD Security Advisory SA-16:37.
Credit: cret@cert.org
Affected Software | Affected Version | How to fix |
---|---|---|
FreeBSD Kernel | =9.3 | |
FreeBSD Kernel | =10.1 | |
FreeBSD Kernel | =10.2 | |
FreeBSD Kernel | =10.3 | |
FreeBSD Kernel | =11.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-6559 has a severity that varies based on how the vulnerability is exploited and the context in which the affected BSD libc library is used.
To fix CVE-2016-6559, upgrade to the patched versions of FreeBSD, specifically 9.3, 10.1, 10.2, 10.3, or 11.0.
CVE-2016-6559 affects FreeBSD versions 9.3, 10.1, 10.2, 10.3, and 11.0.
Exploiting CVE-2016-6559 can lead to unauthorized memory reading or writing, potentially resulting in application crashes or data corruption.
CVE-2016-6559 can potentially be exploited locally, but the actual impact depends on how applications interface with the flawed BSD libc library.