Lucene search

K
redhatRedHatRHSA-2015:2241
HistoryNov 19, 2015 - 2:42 p.m.

(RHSA-2015:2241) Moderate: chrony security, bug fix, and enhancement update

2015-11-1914:42:40
access.redhat.com
10

6.5 Medium

CVSS3

Attack Vector

NETWORK

Attack Complexity

LOW

Privileges Required

LOW

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

NONE

Integrity Impact

NONE

Availability Impact

HIGH

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

6.5 Medium

CVSS2

Access Vector

NETWORK

Access Complexity

LOW

Authentication

SINGLE

Confidentiality Impact

PARTIAL

Integrity Impact

PARTIAL

Availability Impact

PARTIAL

AV:N/AC:L/Au:S/C:P/I:P/A:P

0.027 Low

EPSS

Percentile

89.2%

The chrony suite, chronyd and chronyc, is an advanced implementation of the
Network Time Protocol (NTP), 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 (RFC 5905) 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 (only localhost is allowed by
default) could use this flaw to crash chronyd or, possibly, execute
arbitrary code with the privileges of the chronyd process. (CVE-2015-1821)

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 (only localhost is
allowed by default) could use this flaw to crash chronyd or, possibly,
execute arbitrary code with the privileges of the chronyd process.
(CVE-2015-1822)

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. (CVE-2015-1853)

These issues were discovered by Miroslav LichvΓ‘r of Red Hat.

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 (RFC 5905)

  • 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 (next NTP era)

  • Improved clock control

  • Networking code reworked to open separate client sockets for each NTP
    server

(BZ#1117882)

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. (BZ#1169353)

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 (the default β€œsystem” mode), stepped by chronyd (β€œstep”
    mode), slowly adjusted by slewing (β€œslew” mode), or the leap second can be
    ignored and corrected later in normal operation (β€œignore” mode). 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. (BZ#1206504)

All chrony users are advised to upgrade to these updated packages, which
correct these issues and add these enhancements.

6.5 Medium

CVSS3

Attack Vector

NETWORK

Attack Complexity

LOW

Privileges Required

LOW

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

NONE

Integrity Impact

NONE

Availability Impact

HIGH

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

6.5 Medium

CVSS2

Access Vector

NETWORK

Access Complexity

LOW

Authentication

SINGLE

Confidentiality Impact

PARTIAL

Integrity Impact

PARTIAL

Availability Impact

PARTIAL

AV:N/AC:L/Au:S/C:P/I:P/A:P

0.027 Low

EPSS

Percentile

89.2%