Advisories ยป MGASA-2016-0414

Updated ntp packages fix security vulnerabilities

Publication date: 08 Dec 2016
Modification date: 08 Dec 2016
Type: security
Affected Mageia releases : 5
CVE: CVE-2016-7426 , CVE-2016-7429 , CVE-2016-9310 , CVE-2016-9311

Description

When ntpd is configured with rate limiting for all associations (restrict
default limited in ntp.conf), the limits are applied also to responses
received from its configured sources. An attacker who knows the sources
(e.g., from an IPv4 refid in server response) and knows the system is
(mis)configured in this way can periodically send packets with spoofed
source address to keep the rate limiting activated and prevent ntpd from
accepting valid responses from its sources (CVE-2016-7426).

When ntpd receives a server response on a socket that corresponds to a
different interface than was used for the request, the peer structure is
updated to use the interface for new requests. If ntpd is running on a
host with multiple interfaces in separate networks and the operating
system doesn't check source address in received packets (e.g. rp_filter
on Linux is set to 0), an attacker that knows the address of the source
can send a packet with spoofed source address which will cause ntpd to
select wrong interface for the source and prevent it from sending new
requests until the list of interfaces is refreshed, which happens on
routing changes or every 5 minutes by default. If the attack is repeated
often enough (once per second), ntpd will not be able to synchronize
with the source (CVE-2016-7429).

An exploitable configuration modification vulnerability exists in the
control mode (mode 6) functionality of ntpd. If, against long-standing
BCP recommendations, "restrict default noquery ..." is not specified,
a specially crafted control mode packet can set ntpd traps, providing
information disclosure and DDoS amplification, and unset ntpd traps,
disabling legitimate monitoring. A remote, unauthenticated, network
attacker can trigger this vulnerability (CVE-2016-9310).

If trap service, disabled by default, has been explicitly enabled, an
attacker can send a specially crafted packet to cause a null pointer
dereference that will crash ntpd, resulting in a denial of service
(CVE-2016-9311).

References

SRPMS

5/core