The read_network_packet function in ntp_io.c in ntpd in NTP 4.x before 4.2.8p1 on Linux and OS X does not properly determine whether a source IP address is an IPv6 loopback address, which makes it easier for remote attackers to spoof restricted packets, and read or write to the runtime state, by leveraging the ability to reach the ntpd machine's network interface with a packet from the ::1 address.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Link | Tags |
---|---|
http://www.kb.cert.org/vuls/id/852879 | third party advisory us government resource |
http://support.ntp.org/bin/view/Main/SecurityNotice#December_2014_NTP_Security_Vulne | vendor advisory |
http://www.oracle.com/technetwork/topics/security/linuxbulletinoct2015-2719645.html | third party advisory |
http://bugs.ntp.org/show_bug.cgi?id=2672 | issue tracking patch vendor advisory |
http://www.debian.org/security/2015/dsa-3388 | third party advisory vendor advisory |
http://www.securityfocus.com/bid/72584 | vdb entry third party advisory |
http://rhn.redhat.com/errata/RHSA-2015-1459.html | third party advisory vendor advisory |
https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbhf03886en_us | third party advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=1184572 | issue tracking third party advisory |