NTP (Network Time Protocol) vulnerabilities

Buffer overflow in the password management functionality in NTP 4.2.x before 4.2.8p4, and 4.3.x before 4.3.77 allows remote authenticated users to cause a denial of service (daemon crash) or possibly execute arbitrary code via a crafted key file.

Use-after-free vulnerability in ntpd in NTP 4.2.x before 4.2.8p4, and 4.3.x before 4.3.77 allows remote authenticated users to possibly execute arbitrary code or cause a denial of service (crash) via crafted packets.

A memory leak in the CRYPTO_ASSOC function in ntpd in NTP 4.2.x before version 4.2.8p4 and 4.3.x before version 4.3.77 allows remote attackers to cause a denial of service through excessive memory consumption.

The crypto_xmit function in ntpd in NTP 4.2.x before 4.2.8p4 and 4.3.x before 4.3.77 allows remote attackers to cause a denial of service (crash).

The ntp_openssl.m4 in ntpd in NTP before version 4.2.7p112 has a vulnerability that allows remote attackers to cause a denial of service (segmentation fault) via a crafted statistics or filegen configuration command that is not enabled during compilation.

Buffer overflow in the legacy Datum Programmable Time Server (DPTS) refclock driver in NTP before version 4.2.8p10 and 4.3.x before 4.3.94 allows local users to have unspecified impact via a crafted /dev/datum device.

A stack-based buffer overflow in the reslist function in ntpq in NTP before version 4.2.8p10 and 4.3.x before 4.3.94 allows remote servers to have unspecified impact via a long flagstr variable in a restriction list response.

Multiple buffer overflows in the ctl_put* functions in NTP before version 4.2.8p10 and 4.3.x before version 4.3.94 allow remote authenticated users to have unspecified impact via a long variable.

There is a stack-based buffer overflow in the Windows installer for NTP before version 4.2.8p10 and 4.3.x before version 4.3.94. This allows local users to have unspecified impact via an application path on the command line.

The mx4200_send function in the legacy MX4200 refclock in NTP before 4.2.8p10 and 4.3.x before 4.3.94 does not properly handle the return value of the snprintf function, allowing local users to execute arbitrary code via unspecified vectors, leading to an out-of-bounds memory write.

NTP versions before 4.2.8p6 and 4.3.x before 4.3.90 are vulnerable to an attack that can lead to denial of service by tearing down client-server associations. Attackers can achieve this by sending broadcast packets with invalid authentication to a broadcast client.

NTP versions before 4.2.8p6 and 4.3.0 before 4.3.90 allow remote attackers to cause a denial of service (stack exhaustion) via an ntpdc relist command, which triggers recursive traversal of the restriction list.

NTP versions before 4.2.8p9 rate limit responses received from configured sources when rate limiting for all associations is enabled. This allows remote attackers to cause a denial of service by sending responses with a spoofed source address.

The ntp-keygen in NTP before version 4.2.7p230 uses a weak RNG seed, making it easier for remote attackers to defeat cryptographic protection mechanisms via a brute-force attack.

The config_auth function in ntpd in NTP before version 4.2.7p11 improperly generates a key when an auth key is not configured. This makes it easier for remote attackers to defeat cryptographic protection mechanisms via a brute-force attack.

The rate limiting feature in NTP versions 4.x before 4.2.8p4 and 4.3.x before 4.3.77 is vulnerable. Remote attackers can exploit this vulnerability by sending a large number of crafted requests.