It was discovered that ntpd as a client did not correctly check the originate timestamp in received packets. A remote attacker could use this flaw to send a crafted packet to an ntpd client that would effectively disable synchronization with the server, or push arbitrary offset/delay measurements to modify the time on the client. A NULL pointer dereference flaw was found in the way ntpd processed "ntpdc reslist" commands that queried restriction lists with a large amount of entries. A remote attacker could use this flaw to crash the ntpd process. It was found that NTP does not verify peer associations of symmetric keys when authenticating packets, which might allow remote attackers to conduct impersonation attacks via an arbitrary trusted key. A stack-based buffer overflow was found in the way ntpd processed "ntpdc reslist" commands that queried restriction lists with a large amount of entries. A remote attacker could use this flaw to crash the ntpd process. It was found that when NTP is configured in broadcast mode, an off-path attacker could broadcast packets with bad authentication to all clients. The clients, upon receiving the malformed packets, would break the association with the broadcast server. This could cause the time on affected clients to become out of sync over a longer period of time. A flaw was found in the way the ntpq client certain processed incoming packets in a loop in the getresponse function. A remote attacker could potentially use this flaw to crash an ntpq client instance