The chrony suite, chronyd and chronyc, is an advanced implementation of the Network Time Protocol , specially designed to support systems with intermittent connections. It can synchronize the system clock with NTP servers, hardware reference clocks, and manual input. It can also operate as an NTPv4 server or peer to provide a time service to other computers in the network. An out-of-bounds write flaw was found in the way chrony stored certain addresses when configuring NTP or cmdmon access. An attacker that has the command key and is allowed to access cmdmon could use this flaw to crash chronyd or, possibly, execute arbitrary code with the privileges of the chronyd process. An uninitialized pointer use flaw was found when allocating memory to save unacknowledged replies to authenticated command requests. An attacker that has the command key and is allowed to access cmdmon could use this flaw to crash chronyd or, possibly, execute arbitrary code with the privileges of the chronyd process. A denial of service flaw was found in the way chrony hosts that were peering with each other authenticated themselves before updating their internal state variables. An attacker could send packets to one peer host, which could cascade to other peers, and stop the synchronization process among the reached peers. These issues were discovered by Red Hat team. The chrony packages have been upgraded to upstream version 2.1.1, which provides a number of bug fixes and enhancements over the previous version. Notable enhancements include: * Updated to NTP version 4 * Added pool directive to specify pool of NTP servers * Added leapsecmode directive to select how to correct clock for leap second * Added smoothtime directive to smooth served time and enable leap smear * Added asynchronous name resolving with POSIX threads * Ready for year 2036 * Improved clock control * Networking code reworked to open separate client sockets for each NTP server This update also fixes the following bug: * The chronyd service previously assumed that network interfaces specified with the "bindaddress" directive were ready when the service was started. This could cause chronyd to fail to bind an NTP server socket to the interface if the interface was not ready. With this update, chronyd uses the IP_FREEBIND socket option, enabling it to bind to an interface later, not only when the service starts. In addition, this update adds the following enhancement: * The chronyd service now supports four modes of handling leap seconds, configured using the "leapsecmode" option. The clock can be either stepped by the kernel , stepped by chronyd , slowly adjusted by slewing , or the leap second can be ignored and corrected later in normal operation . If you select slewing, the correction will always start at 00:00:00 UTC and will be applied at a rate specified in the "maxslewrate" option. All chrony users are advised to upgrade to these updated packages, which correct these issues and add these enhancements. 4. Solution: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 5. Bugs fixed : 1117882 - rebase chrony to 2.1.1 1169353 - Chronyd not starting with bindaddress option set to bond interface 1206504 - RFE: option to correct clock for leap second by slewing 1209568 - RFE: add option for leap smear 1209572 - CVE-2015-1853 chrony: authentication doesn"t protect symmetric associations against DoS attacks 1209631 - CVE-2015-1821 chrony: Heap out of bound write in address filter 1209632 - CVE-2015-1822 chrony: uninitialized pointer in cmdmon reply slots