Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2014-9750, CVE-2014-9751. Reason: this ID was intended for one issue, but was associated with two issues. Notes: All CVE users should consult CVE-2014-9750 and CVE-2014-9751 to identify the ID or IDs of interest. All references and descriptions in this candidate have been removed to prevent accidental usage

The remote host is running a version of Mac OS X 10.10.x that is prior to 10.10.3. It is, therefore, affected by multiple vulnerabilities in the following components :

 - Admin Framework
 - Apache
 - ATS
 - Certificate Trust Policy
 - CFNetwork HTTPProtocol
 - CFNetwork Session
 - CFURL
 - CoreAnimation
 - FontParser
 - Graphics Driver
 - Hypervisor
 - ImageIO
 - IOHIDFamily
 - Kernel
 - LaunchServices
 - libnetcore
 - ntp
 - Open Directory Client
 - OpenLDAP
 - OpenSSL
 - PHP
 - QuickLook
 - SceneKit
 - ScreenSharing
 - Security - Code SIgning
 - UniformTypeIdentifiers
 - WebKit

Note that successful exploitation of the most serious issues can result in arbitrary code execution.

It was found that because NTP's access control was based on a source IP address, an attacker could bypass source IP restrictions and send malicious control and configuration packets by spoofing ::1 addresses.
(CVE-2014-9298, CVE-2014-9751)

A denial of service flaw was found in the way NTP 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-1799)

A flaw was found in the way the ntp-keygen utility generated MD5 symmetric keys on big-endian systems. An attacker could possibly use this flaw to guess generated MD5 keys, which could then be used to spoof an NTP client or server. (CVE-2015-3405)

A stack-based buffer overflow was found in the way the NTP autokey protocol was implemented. When an NTP client decrypted a secret received from an NTP server, it could cause that client to crash.
(CVE-2014-9297, CVE-2014-9750)

It was found that ntpd did not check whether a Message Authentication Code (MAC) was present in a received packet when ntpd was configured to use symmetric cryptographic keys. A man-in-the-middle attacker could use this flaw to send crafted packets that would be accepted by a client or a peer without the attacker knowing the symmetric key.
(CVE-2015-1798)

Bug fixes :

  - The ntpd service truncated symmetric keys specified in     the key file to 20 bytes. As a consequence, it was     impossible to configure NTP authentication to work with     peers that use longer keys. With this update, the     maximum key length has been changed to 32 bytes.

  - The ntpd service could previously join multicast groups     only when starting, which caused problems if ntpd was     started during system boot before network was     configured. With this update, ntpd attempts to join     multicast groups every time network configuration is     changed.

  - Previously, the ntp-keygen utility used the exponent of     3 when generating RSA keys. Consequently, generating RSA     keys failed when FIPS mode was enabled. With this     update, ntp-keygen has been modified to use the exponent     of 65537, and generating keys in FIPS mode now works as     expected.

  - The ntpd service dropped incoming NTP packets if their     source port was lower than 123 (the NTP port). With this     update, ntpd no longer checks the source port number,     and clients behind NAT are now able to correctly     synchronize with the server.

Enhancements :

  - This update adds support for configurable Differentiated     Services Code Points (DSCP) in NTP packets, simplifying     configuration in large networks where different NTP     implementations or versions are using different DSCP     values.

  - This update adds the ability to configure separate clock     stepping thresholds for each direction (backward and     forward). Use the 'stepback' and 'stepfwd' options to     configure each threshold.

  - Support for nanosecond resolution has been added to the     Structural Health Monitoring (SHM) reference clock.
    Prior to this update, when a Precision Time Protocol     (PTP) hardware clock was used as a time source to     synchronize the system clock, the accuracy of the     synchronization was limited due to the microsecond     resolution of the SHM protocol. The nanosecond extension     in the SHM protocol now allows sub-microsecond     synchronization of the system clock.

Updated ntp packages that fix multiple security issues, several bugs, and add various enhancements are now available for Red Hat Enterprise Linux 7.

Red Hat Product Security has rated this update as having Moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

The Network Time Protocol (NTP) is used to synchronize a computer's time with another referenced time source. These packages include the ntpd service which continuously adjusts system time and utilities used to query and configure the ntpd service.

It was found that because NTP's access control was based on a source IP address, an attacker could bypass source IP restrictions and send malicious control and configuration packets by spoofing ::1 addresses.
(CVE-2014-9298, CVE-2014-9751)

A denial of service flaw was found in the way NTP 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-1799)

A flaw was found in the way the ntp-keygen utility generated MD5 symmetric keys on big-endian systems. An attacker could possibly use this flaw to guess generated MD5 keys, which could then be used to spoof an NTP client or server. (CVE-2015-3405)

A stack-based buffer overflow was found in the way the NTP autokey protocol was implemented. When an NTP client decrypted a secret received from an NTP server, it could cause that client to crash.
(CVE-2014-9297, CVE-2014-9750)

It was found that ntpd did not check whether a Message Authentication Code (MAC) was present in a received packet when ntpd was configured to use symmetric cryptographic keys. A man-in-the-middle attacker could use this flaw to send crafted packets that would be accepted by a client or a peer without the attacker knowing the symmetric key.
(CVE-2015-1798)

The CVE-2015-1798 and CVE-2015-1799 issues were discovered by Miroslav Lichvar of Red Hat.

Bug fixes :

* The ntpd service truncated symmetric keys specified in the key file to 20 bytes. As a consequence, it was impossible to configure NTP authentication to work with peers that use longer keys. With this update, the maximum key length has been changed to 32 bytes.
(BZ#1191111)

* The ntpd service could previously join multicast groups only when starting, which caused problems if ntpd was started during system boot before network was configured. With this update, ntpd attempts to join multicast groups every time network configuration is changed.
(BZ#1207014)

* Previously, the ntp-keygen utility used the exponent of 3 when generating RSA keys. Consequently, generating RSA keys failed when FIPS mode was enabled. With this update, ntp-keygen has been modified to use the exponent of 65537, and generating keys in FIPS mode now works as expected. (BZ#1191116)

* The ntpd service dropped incoming NTP packets if their source port was lower than 123 (the NTP port). With this update, ntpd no longer checks the source port number, and clients behind NAT are now able to correctly synchronize with the server. (BZ#1171640)

Enhancements :

* This update adds support for configurable Differentiated Services Code Points (DSCP) in NTP packets, simplifying configuration in large networks where different NTP implementations or versions are using different DSCP values. (BZ#1202828)

* This update adds the ability to configure separate clock stepping thresholds for each direction (backward and forward). Use the 'stepback' and 'stepfwd' options to configure each threshold.
(BZ#1193154)

* Support for nanosecond resolution has been added to the Structural Health Monitoring (SHM) reference clock. Prior to this update, when a Precision Time Protocol (PTP) hardware clock was used as a time source to synchronize the system clock, the accuracy of the synchronization was limited due to the microsecond resolution of the SHM protocol. The nanosecond extension in the SHM protocol now allows sub-microsecond synchronization of the system clock. (BZ#1117702)

All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements.

From Red Hat Security Advisory 2015:2231 :

Updated ntp packages that fix multiple security issues, several bugs, and add various enhancements are now available for Red Hat Enterprise Linux 7.

Red Hat Product Security has rated this update as having Moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

The Network Time Protocol (NTP) is used to synchronize a computer's time with another referenced time source. These packages include the ntpd service which continuously adjusts system time and utilities used to query and configure the ntpd service.

It was found that because NTP's access control was based on a source IP address, an attacker could bypass source IP restrictions and send malicious control and configuration packets by spoofing ::1 addresses.
(CVE-2014-9298, CVE-2014-9751)

A denial of service flaw was found in the way NTP 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-1799)

A flaw was found in the way the ntp-keygen utility generated MD5 symmetric keys on big-endian systems. An attacker could possibly use this flaw to guess generated MD5 keys, which could then be used to spoof an NTP client or server. (CVE-2015-3405)

A stack-based buffer overflow was found in the way the NTP autokey protocol was implemented. When an NTP client decrypted a secret received from an NTP server, it could cause that client to crash.
(CVE-2014-9297, CVE-2014-9750)

It was found that ntpd did not check whether a Message Authentication Code (MAC) was present in a received packet when ntpd was configured to use symmetric cryptographic keys. A man-in-the-middle attacker could use this flaw to send crafted packets that would be accepted by a client or a peer without the attacker knowing the symmetric key.
(CVE-2015-1798)

The CVE-2015-1798 and CVE-2015-1799 issues were discovered by Miroslav Lichvar of Red Hat.

Bug fixes :

* The ntpd service truncated symmetric keys specified in the key file to 20 bytes. As a consequence, it was impossible to configure NTP authentication to work with peers that use longer keys. With this update, the maximum key length has been changed to 32 bytes.
(BZ#1191111)

* The ntpd service could previously join multicast groups only when starting, which caused problems if ntpd was started during system boot before network was configured. With this update, ntpd attempts to join multicast groups every time network configuration is changed.
(BZ#1207014)

* Previously, the ntp-keygen utility used the exponent of 3 when generating RSA keys. Consequently, generating RSA keys failed when FIPS mode was enabled. With this update, ntp-keygen has been modified to use the exponent of 65537, and generating keys in FIPS mode now works as expected. (BZ#1191116)

* The ntpd service dropped incoming NTP packets if their source port was lower than 123 (the NTP port). With this update, ntpd no longer checks the source port number, and clients behind NAT are now able to correctly synchronize with the server. (BZ#1171640)

Enhancements :

* This update adds support for configurable Differentiated Services Code Points (DSCP) in NTP packets, simplifying configuration in large networks where different NTP implementations or versions are using different DSCP values. (BZ#1202828)

* This update adds the ability to configure separate clock stepping thresholds for each direction (backward and forward). Use the 'stepback' and 'stepfwd' options to configure each threshold.
(BZ#1193154)

* Support for nanosecond resolution has been added to the Structural Health Monitoring (SHM) reference clock. Prior to this update, when a Precision Time Protocol (PTP) hardware clock was used as a time source to synchronize the system clock, the accuracy of the synchronization was limited due to the microsecond resolution of the SHM protocol. The nanosecond extension in the SHM protocol now allows sub-microsecond synchronization of the system clock. (BZ#1117702)

All ntp users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements.

Some kernels do not offer protection for ::1 source addresses on IPv6 interfaces. Since NTP's access control mechanism is based on source address and localhost addresses generally have no restrictions, an attacker may be able to send malicious control and configuration packets by spoofing ::1 addresses from the outside. (CVE-2014-9751)

Note: The candidate number originally referenced in this article, CVE-2014-9298, was rejected because it was associated with two different issues.

It was found that because NTP's access control was based on a source IP address, an attacker could bypass source IP restrictions and send malicious control and configuration packets by spoofing ::1 addresses.
(CVE-2014-9298)

A denial of service flaw was found in the way NTP 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-1799)

A flaw was found in the way the ntp-keygen utility generated MD5 symmetric keys on big-endian systems. An attacker could possibly use this flaw to guess generated MD5 keys, which could then be used to spoof an NTP client or server. (CVE-2015-3405)

A stack-based buffer overflow was found in the way the NTP autokey protocol was implemented. When an NTP client decrypted a secret received from an NTP server, it could cause that client to crash.
(CVE-2014-9297)

It was found that ntpd did not check whether a Message Authentication Code (MAC) was present in a received packet when ntpd was configured to use symmetric cryptographic keys. A man-in-the-middle attacker could use this flaw to send crafted packets that would be accepted by a client or a peer without the attacker knowing the symmetric key.
(CVE-2015-1798)

The CVE-2015-1798 and CVE-2015-1799 issues were discovered by Miroslav Lichvr of Red Hat.

Bug fixes :

  - The ntpd daemon truncated symmetric keys specified in     the key file to 20 bytes. As a consequence, it was     impossible to configure NTP authentication to work with     peers that use longer keys. The maximum length of keys     has now been changed to 32 bytes.

  - The ntp-keygen utility used the exponent of 3 when     generating RSA keys, and generating RSA keys failed when     FIPS mode was enabled. ntp-keygen has been modified to     use the exponent of 65537, and generating keys in FIPS     mode now works as expected.

  - The ntpd daemon included a root delay when calculating     its root dispersion. Consequently, the NTP server     reported larger root dispersion than it should have and     clients could reject the source when its distance     reached the maximum synchronization distance (1.5     seconds by default). Calculation of root dispersion has     been fixed, the root dispersion is now reported     correctly, and clients no longer reject the server due     to a large synchronization distance.

  - The ntpd daemon dropped incoming NTP packets if their     source port was lower than 123 (the NTP port). Clients     behind Network Address Translation (NAT) were unable to     synchronize with the server if their source port was     translated to ports below 123. With this update, ntpd no     longer checks the source port number.

Enhancements :

  - This update introduces configurable access of memory     segments used for Shared Memory Driver (SHM) reference     clocks. Previously, only the first two memory segments     were created with owner-only access, allowing just two     SHM reference clocks to be used securely on a system.
    Now, the owner-only access to SHM is configurable with     the 'mode' option, and it is therefore possible to use     more SHM reference clocks securely.

  - Support for nanosecond resolution has been added to the     SHM reference clock. Prior to this update, when a     Precision Time Protocol (PTP) hardware clock was used as     a time source to synchronize the system clock (for     example, with the timemaster service from the linuxptp     package), the accuracy of the synchronization was     limited due to the microsecond resolution of the SHM     protocol. The nanosecond extension in the SHM protocol     now enables sub-microsecond synchronization of the     system clock.

The remote OracleVM system is missing necessary patches to address critical security updates :

  - reject packets without MAC when authentication is     enabled (CVE-2015-1798)

  - protect symmetric associations with symmetric key     against DoS attack (CVE-2015-1799)

  - fix generation of MD5 keys with ntp-keygen on big-endian     systems (CVE-2015-3405)

  - log when stepping clock for leap second or ignoring it     with -x (#1204625)

  - fix typos in ntpd man page (#1194463)

  - validate lengths of values in extension fields     (CVE-2014-9297)

  - drop packets with spoofed source address ::1     (CVE-2014-9298)

  - add nanosecond support to SHM refclock (#1117704)

  - allow creating all SHM segments with owner-only access     (#1122015)

  - allow symmetric keys up to 32 bytes again (#1053551)

  - fix calculation of root dispersion (#1045376)

  - fix crash in ntpq mreadvar command (#1165141)

  - don't step clock for leap second with -x option     (#1190619)

  - don't drop packets with source port below 123 (#1171630)

  - use larger RSA exponent in ntp-keygen (#1184421)

  - refresh peers on routing updates (#1193850)

  - increase memlock limit again (#1053568)

  - warn when monitor can't be disabled due to limited     restrict (#1166596)

  - improve documentation of restrict command (#1069019)

  - update logconfig documentation for patched default     (#1193849)

  - don't build ntpsnmpd (#995134)

From Red Hat Security Advisory 2015:1459 :

Updated ntp packages that fix multiple security issues, several bugs, and add two enhancements are now available for Red Hat Enterprise Linux 6.

Red Hat Product Security has rated this update as having Moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

The Network Time Protocol (NTP) is used to synchronize a computer's time with another referenced time source.

It was found that because NTP's access control was based on a source IP address, an attacker could bypass source IP restrictions and send malicious control and configuration packets by spoofing ::1 addresses.
(CVE-2014-9298)

A denial of service flaw was found in the way NTP 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-1799)

A flaw was found in the way the ntp-keygen utility generated MD5 symmetric keys on big-endian systems. An attacker could possibly use this flaw to guess generated MD5 keys, which could then be used to spoof an NTP client or server. (CVE-2015-3405)

A stack-based buffer overflow was found in the way the NTP autokey protocol was implemented. When an NTP client decrypted a secret received from an NTP server, it could cause that client to crash.
(CVE-2014-9297)

It was found that ntpd did not check whether a Message Authentication Code (MAC) was present in a received packet when ntpd was configured to use symmetric cryptographic keys. A man-in-the-middle attacker could use this flaw to send crafted packets that would be accepted by a client or a peer without the attacker knowing the symmetric key.
(CVE-2015-1798)

The CVE-2015-1798 and CVE-2015-1799 issues were discovered by Miroslav Lichvar of Red Hat.

Bug fixes :

* The ntpd daemon truncated symmetric keys specified in the key file to 20 bytes. As a consequence, it was impossible to configure NTP authentication to work with peers that use longer keys. The maximum length of keys has now been changed to 32 bytes. (BZ#1053551)

* The ntp-keygen utility used the exponent of 3 when generating RSA keys, and generating RSA keys failed when FIPS mode was enabled.
ntp-keygen has been modified to use the exponent of 65537, and generating keys in FIPS mode now works as expected. (BZ#1184421)

* The ntpd daemon included a root delay when calculating its root dispersion. Consequently, the NTP server reported larger root dispersion than it should have and clients could reject the source when its distance reached the maximum synchronization distance (1.5 seconds by default). Calculation of root dispersion has been fixed, the root dispersion is now reported correctly, and clients no longer reject the server due to a large synchronization distance.
(BZ#1045376)

* The ntpd daemon dropped incoming NTP packets if their source port was lower than 123 (the NTP port). Clients behind Network Address Translation (NAT) were unable to synchronize with the server if their source port was translated to ports below 123. With this update, ntpd no longer checks the source port number. (BZ#1171630)

Enhancements :

* This update introduces configurable access of memory segments used for Shared Memory Driver (SHM) reference clocks. Previously, only the first two memory segments were created with owner-only access, allowing just two SHM reference clocks to be used securely on a system. Now, the owner-only access to SHM is configurable with the 'mode' option, and it is therefore possible to use more SHM reference clocks securely. (BZ#1122015)

* Support for nanosecond resolution has been added to the SHM reference clock. Prior to this update, when a Precision Time Protocol (PTP) hardware clock was used as a time source to synchronize the system clock (for example, with the timemaster service from the linuxptp package), the accuracy of the synchronization was limited due to the microsecond resolution of the SHM protocol. The nanosecond extension in the SHM protocol now enables sub-microsecond synchronization of the system clock. (BZ#1117704)

Updated ntp packages that fix multiple security issues, several bugs, and add two enhancements are now available for Red Hat Enterprise Linux 6.

Red Hat Product Security has rated this update as having Moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

The Network Time Protocol (NTP) is used to synchronize a computer's time with another referenced time source.

It was found that because NTP's access control was based on a source IP address, an attacker could bypass source IP restrictions and send malicious control and configuration packets by spoofing ::1 addresses.
(CVE-2014-9298)

A denial of service flaw was found in the way NTP 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-1799)

A flaw was found in the way the ntp-keygen utility generated MD5 symmetric keys on big-endian systems. An attacker could possibly use this flaw to guess generated MD5 keys, which could then be used to spoof an NTP client or server. (CVE-2015-3405)

A stack-based buffer overflow was found in the way the NTP autokey protocol was implemented. When an NTP client decrypted a secret received from an NTP server, it could cause that client to crash.
(CVE-2014-9297)

It was found that ntpd did not check whether a Message Authentication Code (MAC) was present in a received packet when ntpd was configured to use symmetric cryptographic keys. A man-in-the-middle attacker could use this flaw to send crafted packets that would be accepted by a client or a peer without the attacker knowing the symmetric key.
(CVE-2015-1798)

The CVE-2015-1798 and CVE-2015-1799 issues were discovered by Miroslav Lichvar of Red Hat.

Bug fixes :

* The ntpd daemon truncated symmetric keys specified in the key file to 20 bytes. As a consequence, it was impossible to configure NTP authentication to work with peers that use longer keys. The maximum length of keys has now been changed to 32 bytes. (BZ#1053551)

* The ntp-keygen utility used the exponent of 3 when generating RSA keys, and generating RSA keys failed when FIPS mode was enabled.
ntp-keygen has been modified to use the exponent of 65537, and generating keys in FIPS mode now works as expected. (BZ#1184421)

* The ntpd daemon included a root delay when calculating its root dispersion. Consequently, the NTP server reported larger root dispersion than it should have and clients could reject the source when its distance reached the maximum synchronization distance (1.5 seconds by default). Calculation of root dispersion has been fixed, the root dispersion is now reported correctly, and clients no longer reject the server due to a large synchronization distance.
(BZ#1045376)

* The ntpd daemon dropped incoming NTP packets if their source port was lower than 123 (the NTP port). Clients behind Network Address Translation (NAT) were unable to synchronize with the server if their source port was translated to ports below 123. With this update, ntpd no longer checks the source port number. (BZ#1171630)

Enhancements :

* This update introduces configurable access of memory segments used for Shared Memory Driver (SHM) reference clocks. Previously, only the first two memory segments were created with owner-only access, allowing just two SHM reference clocks to be used securely on a system. Now, the owner-only access to SHM is configurable with the 'mode' option, and it is therefore possible to use more SHM reference clocks securely. (BZ#1122015)

* Support for nanosecond resolution has been added to the SHM reference clock. Prior to this update, when a Precision Time Protocol (PTP) hardware clock was used as a time source to synchronize the system clock (for example, with the timemaster service from the linuxptp package), the accuracy of the synchronization was limited due to the microsecond resolution of the SHM protocol. The nanosecond extension in the SHM protocol now enables sub-microsecond synchronization of the system clock. (BZ#1117704)

According to its self-reported version number, the Cisco Prime Data Center Network Manager (DCNM) running on the remote host is affected by multiple vulnerabilities :

  - A security weakness exists due to the config_auth()     function improperly generating default keys when no     authentication key is defined in the 'ntp.conf' file.
    Key size is limited to 31 bits and the insecure     ntp_random() function is used, resulting in     cryptographically weak keys with insufficient entropy.
    This allows a remote attacker to defeat cryptographic     protection mechanisms via a brute-force attack.
    (CVE-2014-9293)

  - A security weakness exists due the use of a weak seed     to prepare a random number generator used to generate     symmetric keys. This allows remote attackers to defeat     cryptographic protection mechanisms via a brute-force     attack. (CVE-2014-9294)

  - Multiple stack-based buffer overflows exist due to     improperly validated user-supplied input when handling     packets in the crypto_recv(), ctl_putdata(), and     configure() functions when using autokey authentication.
    This allows a remote attacker, via a specially crafted     packet, to cause a denial of service condition or     execute arbitrary code. (CVE-2014-9295)

  - A unspecified vulnerability exists due to missing return     statements in the receive() function, resulting in     continued processing even when an authentication error     is encountered. This allows a remote attacker, via     crafted packets, to trigger unintended association     changes. (CVE-2014-9296)

  - A security bypass vulnerability exists in the function     read_network_packet() due to a failure to restrict ::1     source addresses on IPv6 interfaces. This allows a     remote attacker to bypass configured ACLs based on ::1.
    (CVE-2014-9298)

This plugin determines if DCNM is vulnerable by checking the version number displayed in the web interface. The web interface is not available in older versions of DCNM.

xntp has been updated to fix two security issues :

  - CVE-2014-9298: ::1 can be spoofed on some OSes, so ACLs     based on IPv6 ::1 addresses can be bypassed     (bnc#911792).

  - CVE-2014-9297: vallen is not validated in several places     in ntp_crypto.c, leading to potential info leak     (bnc#911792).

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote host is running a version of Mac OS X 10.10.x that is prior to 10.10.3. It is, therefore, affected multiple vulnerabilities in the following components :

  - Admin Framework
  - Apache
  - ATS
  - Certificate Trust Policy
  - CFNetwork HTTPProtocol
  - CFNetwork Session
  - CFURL
  - CoreAnimation
  - FontParser
  - Graphics Driver
  - Hypervisor
  - ImageIO
  - IOHIDFamily
  - Kernel
  - LaunchServices
  - libnetcore
  - ntp
  - Open Directory Client
  - OpenLDAP
  - OpenSSL
  - PHP
  - QuickLook
  - SceneKit
  - ScreenSharing
  - Security - Code SIgning
  - UniformTypeIdentifiers
  - WebKit

Note that successful exploitation of the most serious issues can result in arbitrary code execution.

Updated ntp packages fix security vulnerabilities :

If no authentication key is defined in the ntp.conf file, a cryptographically-weak default key is generated (CVE-2014-9293).

ntp-keygen before 4.2.7p230 uses a non-cryptographic random number generator with a weak seed to generate symmetric keys (CVE-2014-9294).

A remote unauthenticated attacker may craft special packets that trigger buffer overflows in the ntpd functions crypto_recv() (when using autokey authentication), ctl_putdata(), and configure(). The resulting buffer overflows may be exploited to allow arbitrary malicious code to be executed with the privilege of the ntpd process (CVE-2014-9295).

A section of code in ntpd handling a rare error is missing a return statement, therefore processing did not stop when the error was encountered. This situation may be exploitable by an attacker (CVE-2014-9296).

Stephen Roettger of the Google Security Team, Sebastian Krahmer of the SUSE Security Team and Harlan Stenn of Network Time Foundation discovered that the length value in extension fields is not properly validated in several code paths in ntp_crypto.c, which could lead to information leakage or denial of service (CVE-2014-9297).

Stephen Roettger of the Google Security Team reported that ACLs based on IPv6 ::1 (localhost) addresses can be bypassed (CVE-2014-9298).

The ntp package has been patched to fix these issues.

Several vulnerabilities were discovered in the ntp package, an implementation of the Network Time Protocol. The Common Vulnerabilities and Exposures project identifies the following problems :

CVE-2014-9297

Stephen Roettger of the Google Security Team, Sebastian Krahmer of the SUSE Security Team and Harlan Stenn of Network Time Foundation discovered that the length value in extension fields is not properly validated in several code paths in ntp_crypto.c, which could lead to information leakage or denial of service (ntpd crash).

CVE-2014-9298

Stephen Roettger of the Google Security Team reported that ACLs based on IPv6 ::1 addresses can be bypassed.

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

It was reported that ntp misses validation of vallen value, leading to various information leaks. See for more details. (CVE-2014-9297)

It was reported that ntp allows bypassing source IP ACLs on some OSes when ::1 spoofed. (CVE-2014-9298)

Security fix for CVE-2014-9297, CVE-2014-9298

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Updated ntp packages fix security vulnerabilities :

Stephen Roettger of the Google Security Team, Sebastian Krahmer of the SUSE Security Team and Harlan Stenn of Network Time Foundation discovered that the length value in extension fields is not properly validated in several code paths in ntp_crypto.c, which could lead to information leakage or denial of service (CVE-2014-9297).

Stephen Roettger of the Google Security Team reported that ACLs based on IPv6 ::1 (localhost) addresses can be bypassed (CVE-2014-9298).

ntp has been updated to fix four security issues :

  - ntp-keygen used a weak RNG seed, which made it easier     for remote attackers to defeat cryptographic protection     mechanisms via a brute-force attack. (bsc#910764).
    (CVE-2014-9294)

  - The config_auth function, when an auth key is not     configured, improperly generated a key, which made it     easier for remote attackers to defeat cryptographic     protection mechanisms via a brute-force attack.
    (bsc#910764). (CVE-2014-9293)

  - ::1 can be spoofed on some operating systems, so ACLs     based on IPv6 ::1 addresses could be bypassed.
    (bsc#910764). (CVE-2014-9298)

  - vallen is not validated in several places in     ntp_crypto.c, leading to potential information leak.
    (bsc#910764). (CVE-2014-9297)

Stephen Roettger, Sebastian Krahmer, and Harlan Stenn discovered that NTP incorrectly handled the length value in extension fields. A remote attacker could use this issue to possibly obtain leaked information, or cause the NTP daemon to crash, resulting in a denial of service.
(CVE-2014-9297)

Stephen Roettger discovered that NTP incorrectly handled ACLs based on certain IPv6 addresses. (CVE-2014-9298).

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Severity
700510	Mac OS X 10.10.x < 10.10.3 Multiple Vulnerabilities	Nessus Network Monitor	Operating System Detection	critical
87564	Scientific Linux Security Update : ntp on SL7.x x86_64 (20151119)	Nessus	Scientific Linux Local Security Checks	high
87143	CentOS 7 : ntp (CESA-2015:2231)	Nessus	CentOS Local Security Checks	high
87030	Oracle Linux 7 : ntp (ELSA-2015-2231)	Nessus	Oracle Linux Local Security Checks	high
86975	RHEL 7 : ntp (RHSA-2015:2231)	Nessus	Red Hat Local Security Checks	high
86257	F5 Networks BIG-IP : NTP vulnerability (K16393)	Nessus	F5 Networks Local Security Checks	medium
85203	Scientific Linux Security Update : ntp on SL6.x i386/x86_64 (20150722)	Nessus	Scientific Linux Local Security Checks	high
85143	OracleVM 3.3 : ntp (OVMSA-2015-0102)	Nessus	OracleVM Local Security Checks	high
85111	Oracle Linux 6 : ntp (ELSA-2015-1459)	Nessus	Oracle Linux Local Security Checks	high
85025	CentOS 6 : ntp (CESA-2015:1459)	Nessus	CentOS Local Security Checks	high
84951	RHEL 6 : ntp (RHSA-2015:1459)	Nessus	Red Hat Local Security Checks	high
83876	Cisco Prime Data Center Network Manager ntpd Multiple Vulnerabilities (uncredentialed check)	Nessus	CISCO	high
83685	SUSE SLES10 Security Update : xntp (SUSE-SU-2015:0322-1)	Nessus	SuSE Local Security Checks	high
82699	Mac OS X 10.10.x < 10.10.3 Multiple Vulnerabilities (FREAK)	Nessus	MacOS X Local Security Checks	critical
82393	Mandriva Linux Security Advisory : ntp (MDVSA-2015:140)	Nessus	Mandriva Local Security Checks	high
82132	Debian DLA-149-1 : ntp security update	Nessus	Debian Local Security Checks	high
82045	Amazon Linux AMI : ntp (ALAS-2015-496)	Nessus	Amazon Linux Local Security Checks	high
81361	Fedora 20 : ntp-4.2.6p5-20.fc20 (2015-1759)	Nessus	Fedora Local Security Checks	medium
81359	Fedora 21 : ntp-4.2.6p5-27.fc21 (2015-1736)	Nessus	Fedora Local Security Checks	medium
81335	Mandriva Linux Security Advisory : ntp (MDVSA-2015:046)	Nessus	Mandriva Local Security Checks	high
81313	SuSE 11.3 Security Update : ntp (SAT Patch Number 10293)	Nessus	SuSE Local Security Checks	high
81256	Ubuntu 14.04 LTS : NTP vulnerabilities (USN-2497-1)	Nessus	Ubuntu Local Security Checks	high

Detections

Analytics

CVE-2014-9298

No Score

Tenable Plugins

critical

high

high

high

high

medium

high

high

high

high

high

high

high

critical

high

high

high

medium

medium

high

high

high