CVE-2016-6559
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.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (3.70%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
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.
- CVSS 3.0
- 9.8 CRITICALCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 3.70% probability · 89th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-120, CWE-119
- Affected
- freebsd/freebsd
- Source
- cret@cert.org
References
- http://www.securitytracker.com/id/1037398Third Party Advisory, VDB Entry
- https://www.freebsd.org/security/advisories/FreeBSD-SA-16:37.libc.ascVendor Advisory
- https://www.kb.cert.org/vuls/id/548487Third Party Advisory, US Government Resource
- https://www.securityfocus.com/bid/94694Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1037398Third Party Advisory, VDB Entry
- https://www.freebsd.org/security/advisories/FreeBSD-SA-16:37.libc.ascVendor Advisory
- https://www.kb.cert.org/vuls/id/548487Third Party Advisory, US Government Resource
- https://www.securityfocus.com/bid/94694Third Party Advisory, VDB Entry
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.