CWE
119 120
Advisory Published
Updated

CVE-2016-6559: The BSD libc library's link_ntoa() function may be vulnerable to a classic buffer overflow

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 SoftwareAffected VersionHow to fix
FreeBSD Kernel=9.3
FreeBSD Kernel=10.1
FreeBSD Kernel=10.2
FreeBSD Kernel=10.3
FreeBSD Kernel=11.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2016-6559?

    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.

  • How do I fix CVE-2016-6559?

    To fix CVE-2016-6559, upgrade to the patched versions of FreeBSD, specifically 9.3, 10.1, 10.2, 10.3, or 11.0.

  • What versions of FreeBSD are affected by CVE-2016-6559?

    CVE-2016-6559 affects FreeBSD versions 9.3, 10.1, 10.2, 10.3, and 11.0.

  • What is the impact of exploiting CVE-2016-6559?

    Exploiting CVE-2016-6559 can lead to unauthorized memory reading or writing, potentially resulting in application crashes or data corruption.

  • Is CVE-2016-6559 a remote or local vulnerability?

    CVE-2016-6559 can potentially be exploited locally, but the actual impact depends on how applications interface with the flawed BSD libc library.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203