5
CVSSv2

CVE-2017-10986

Published: 17/07/2017 Updated: 03/10/2019
CVSS v2 Base Score: 5 | Impact Score: 2.9 | Exploitability Score: 10
CVSS v3 Base Score: 7.5 | Impact Score: 3.6 | Exploitability Score: 3.9
VMScore: 445
Vector: AV:N/AC:L/Au:N/C:N/I:N/A:P

Vulnerability Summary

An FR-GV-303 issue in FreeRADIUS 3.x prior to 3.0.15 allows "DHCP - Infinite read in dhcp_attr2vp()" and a denial of service.

Vulnerability Trend

Vulnerable Product Search on Vulmon Subscribe to Product

freeradius freeradius 3.0.10

freeradius freeradius 3.0.9

freeradius freeradius 3.0.2

freeradius freeradius 3.0.1

freeradius freeradius 3.0.0

freeradius freeradius 3.0.8

freeradius freeradius 3.0.7

freeradius freeradius 3.0.14

freeradius freeradius 3.0.13

freeradius freeradius 3.0.6

freeradius freeradius 3.0.5

freeradius freeradius 3.0.12

freeradius freeradius 3.0.11

freeradius freeradius 3.0.4

freeradius freeradius 3.0.3

Vendor Advisories

Debian Bug report logs - #868765 freeradius: New upstream version 3015 fixing security critical bugs Package: freeradius; Maintainer for freeradius is Debian FreeRADIUS Packaging Team <pkg-freeradius-maintainers@listsaliothdebianorg>; Source for freeradius is src:freeradius (PTS, buildd, popcon) Reported by: Karsten Hey ...
Several security issues were fixed in FreeRADIUS ...
Guido Vranken discovered that FreeRADIUS, an open source implementation of RADIUS, the IETF protocol for AAA (Authorisation, Authentication, and Accounting), did not properly handle memory when processing packets This would allow a remote attacker to cause a denial-of-service by application crash, or potentially execute arbitrary code All those i ...
An out-of-bounds read flaw was found in the way FreeRADIUS server handled decoding of DHCP packets A remote attacker could use this flaw to crash the FreeRADIUS server by sending a specially crafted DHCP request ...
A security issue has been found in freeradius <= 3015, where the dhcp_attr2vp() function, when decoding "string" options in an array, could be convinced to call memchr() with a length argument of -1 This could result in an over-read until the first zero octet was found, or a page fault occurred ...