Updated ntp packages fix security vulnerabilitiesPublication date: 13 May 2016
Affected Mageia releases : 5
CVE: CVE-2016-1548 , CVE-2016-1550 , CVE-2016-2516 , CVE-2016-2518
Updated ntp packages fix security vulnerabilities: It is possible to change the time of an ntpd client or deny service to an ntpd client by forcing it to change from basic client/server mode to interleaved symmetric mode. An attacker can spoof a packet from a legitimate ntpd server with an origin timestamp that matches the peer->dst timestamp recorded for that server. After making this switch, the client will reject all future legitimate server responses. It is possible to force the victim client to move time after the mode has been changed. ntpq gives no indication that the mode has been switched (CVE-2016-1548). An exploitable vulnerability exists in the message authentication functionality of Network Time Protocol libntp. An attacker can send a series of crafted messages to attempt to recover the message digest key (CVE-2016-1550). If ntpd was expressly configured to allow for remote configuration, a malicious user who knows the controlkey for ntpq or the requestkey for ntpdc (if mode7 is expressly enabled) can create a session with ntpd and if an existing association is unconfigured using the same IP twice on the unconfig directive line, ntpd will abort (CVE-2016-2516). Using a crafted packet to create a peer association with hmode > 7 causes the MATCH_ASSOC() lookup to make an out-of-bounds reference (CVE-2016-2518). Note that CVE-2016-2516, as well as other known but unfixed vulnerabilities in ntpd, are also mitigated by not allowing remote configuration, which is the default in Mageia.