ntpd in ntp 4.2.8p10, 4.2.8p11, 4.2.8p12 and 4.2.8p13 allow remote attackers to prevent a broadcast client from synchronizing its clock with a broadcast NTP server via soofed mode 3 and mode 5 packets. The attacker must either be a part of the same broadcast network or control a slave in that broadcast network that can capture certain required packets on the attacker's behalf and send them to the attacker.
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.ntp.org/ | vendor advisory |
| https://tools.ietf.org/html/rfc5905 | third party advisory |
| https://nikhiltripathi.in/NTP_attack.pdf | third party advisory |
| https://arxiv.org/abs/2005.01783 | third party advisory |
| https://security.netapp.com/advisory/ntap-20200518-0006/ | |
| http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00005.html | vendor advisory |
| http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00044.html | vendor advisory |