Aanchal Malhotra

The issue allows remote attackers to set or unset traps via a crafted control mode packet, which can lead to a denial of service caused by a NULL pointer dereference when the trap service has been enabled. By sending specially crafted packets, a remote attacker could exploit this to cause the application to crash.

The issue allows remote attackers to bypass the origin timestamp protection mechanism via an origin timestamp of zero. This is due to a regression of a previous issue. Multiple vulnerabilities could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition or modify the time being advertised by a device acting as a Network Time Protocol (NTP) server. These vulnerabilities include issues with the Network Time Protocol Trap Service, Broadcast Mode, Insufficient Resource Pool, Configuration Modification, mrulist Query Requests, Multiple Binds to the Same Port, and Rate Limiting.

The issue is related to the initial sync calculations in NTP, which could allow remote attackers to have an unspecified impact via unknown vectors. This is due to a "root distance that did not include the peer dispersion." Multiple vulnerabilities in the NTP daemon package could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition or modify the time being advertised by a device acting as an NTP server.

The issue allows remote attackers to cause a denial of service by sending broadcast packets with invalid authentication to a broadcast client, resulting in a client-server association tear down.

The issue allows man-in-the-middle attackers to conduct replay attacks by sniffing the network when NTP is configured in broadcast mode.

The issue allows remote attackers to bypass security restrictions by exploiting the failure to correctly implement the threshold limitation for the '-g' option. This can be achieved by responding to an unspecified number of requests from trusted sources, potentially allowing an attacker to set NTP to an arbitrary time or alter the time by up to 900 seconds, and leveraging a resulting denial of service. An attacker could exploit this using man-in-the-middle techniques to intercept NTP traffic and make multiple steps larger than the panic threshold.

The rate limiting feature in NTP allows remote attackers to have unspecified impact via a large number of crafted requests. This issue exists due to insufficient input validation, which may allow a remote attacker to cause partial disruption of confidentiality, integrity, and availability of protected information by sending a large number of reverse requests.

The issue allows remote attackers to cause a denial of service via a number of crafted "KOD" messages.