ntp security update (RHSA-2014-2025)

Original Release Date: January 19, 2015
Last Revised: December 1, 2017
Number: ASA-2015-024
Risk Level: Medium
Advisory Version: 2.0
Advisory Status: Final

1. Overview:

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

Multiple buffer overflow flaws were discovered in ntpd's crypto_recv(), ctl_putdata(), and configure() functions. A remote attacker could use either of these flaws to send a specially crafted request packet that could crash ntpd or, potentially, execute arbitrary code with the privileges of the ntp user. Note: the crypto_recv() flaw requires non-default configurations to be active, while the ctl_putdata() flaw, by default, can only be exploited via local attackers, and the configure() flaw requires additional authentication to exploit. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-9295 to this issue.

It was found that ntpd automatically generated weak keys for its internal use if no ntpdc request authentication key was specified in the ntp.conf configuration file. A remote attacker able to match the configured IP restrictions could guess the generated key, and possibly use it to send ntpdc query or configuration requests. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-9293 to this issue.

It was found that ntp-keygen used a weak method for generating MD5 keys. This could possibly allow an attacker to guess generated MD5 keys that could then be used to spoof an NTP client or server. Note: it is recommended to regenerate any MD5 keys that had explicitly been generated with ntp-keygen; the default installation does not contain such keys). The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-9294 to this issue.

More information about these vulnerabilities can be found in the security advisory issued by Red Hat:

2. Avaya System Products using a modified version of RHEL5 with affected packages installed:

Product: Affected Version(s): Risk Level: Actions:
Avaya Aura® Application Enablement Services 6.3 through 6.3.3 Low For versions earlier than 6.3.3, upgrade to 6.3.3 Security Update Patch 3 or later.
For 6.3.3, install Security Update Patch 3 or later.
Avaya Aura® Application Server 5300:
  • SIP Core
2.x through 3.0 SP9 Medium Upgrade to 3.0 SP10 or later.
Avaya IQ 5.2 through 5.2.5 Low Upgrade to 5.2.6 or later.
Avaya Aura® Communication Manager 6.0 through 6.3 Low Upgrade to 6.3 and install Security Service Pack 6 or later.
Avaya Communication Server 1000:
  • CS1000E
  • CS1000M
  • CS1000E/CS1000M Signaling Server
7.0 through 7.5 Medium Upgrade to 7.6 or later.
Avaya Aura® Conferencing 7.0 through 7.2 SP6 Medium Upgrade to 7.2 SP7 or later.
Avaya Aura® Conferencing Standard Edition 6.x Medium See recommended actions and Mitigating Factors table below. This advisory will not be addressed as no further releases are planned. It is recommended that customers migrate to one of Avaya's conferencing solutions including Aura® Conferencing 7.0 or later.
Avaya IP Office Application Server 8.x through 9.1.3 Medium Upgrade to 9.1.4 or later.
Avaya Meeting Exchange 5.x through 6.2 SP3 Low Upgrade to 6.2 SP4 or later.
Avaya Message Networking 6.3 Low Install Patch 3 or later.
Avaya one-X® Client Enablement Services 6.1.x, 6.2 through 6.2 SP3 Medium Upgrade to 6.2 SP4 or later.
Avaya Aura® Presence Services 6.x Low Upgrade to Aura Presence Services 7.1 or later. Further information about this version, as well as the overall Aura 7.1 release, is available on support.avaya.com.
Avaya Proactive Contact 5.1 through 5.1.1 Medium Upgrade to 5.1.2 or later.
Avaya Aura® Session Manager 6.0 through 6.3.18 Low Upgrade to 6.3.19 or later.
Avaya Aura® System Manager 6.0 through 6.3.11 Low Upgrade to 6.3.12 or later.
Avaya Aura® System Platform 6.0 through 6.3.6 Low Upgrade to 6.3.7 or later.

Recommended Actions for System Products:
Avaya strongly recommends following networking and security best practices by implementing firewalls, ACLs, physical security or other appropriate access restrictions. Though Avaya believes such restrictions should always be in place, risk to Avaya products and the surrounding network from this potential vulnerability may be mitigated by ensuring these practices are implemented until such time as an Avaya provided product update or the recommended Avaya action is applied. Further restrictions as deemed necessary based on the customer's security policies may be required during this interim period, but the System Product operating system or application should not be modified unless the change is approved by Avaya. Making changes that are not approved may void the Avaya product service contract.

Mitigating Factors:

When determining risk, Avaya takes into account many factors as outlined by Avaya's Security Vulnerability Classification Policy. The following table describes factors that mitigate the risk of specific vulnerabilities for affected Avaya products:

Vulnerability Mitigating Factors
CVE-2014-9294
The risk is rated None for all listed products because MD5 keys are not used by default.
CVE-2014-9293
CVE-2014-9295
The risk is rated Low for AES, IQ, CM, MN, MX, PS, SM, SMGR and SP because the ntp configuration restricts control and query requests to only local host.
The risk is rated Medium for all other listed products because ntpd is a non-critical process, running as a non-privileged user and the configuration restricts control and query requests to specific hosts within an enterprise network.

3. Avaya Software-Only Products:

Avaya software-only products operate on general-purpose operating systems. Occasionally vulnerabilities may be discovered in the underlying operating system or applications that come with the operating system. These vulnerabilities often do not impact the software-only product directly but may threaten the integrity of the underlying platform.

In the case of this advisory Avaya software-only products are not affected by the vulnerability directly but the underlying Linux platform may be. Customers should determine on which Linux operating system the product was installed and then follow that vendor's guidance.

Product: Actions:
Avaya Aura® Application Enablement Services Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the AES application.
Avaya IQ Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the Avaya IQ application.
CVLAN Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the CVLAN application.
Avaya Aura® Experience Portal Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the EP application.
Avaya Integrated Management Suite (IMS) Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the IMS application.
Avaya Aura® Presence Services Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the PS application.

Recommended Actions for Software-Only Products:
In the event that the affected package is installed, Avaya recommends following recommended actions supplied by Red Hat regarding their Enterprise Linux.

4. Additional Information:

Additional information may also be available via the Avaya support website and through your Avaya account representative. Please contact your Avaya product support representative, or dial 1-800-242-2121, with any questions.

5. Disclaimer:

ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED "AS IS". AVAYA INC., ON BEHALF ITSELF AND ITS SUBSIDIARIES AND AFFILIATES (HEREINAFTER COLLECTIVELY REFERRED TO AS "AVAYA"), DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND FURTHERMORE, AVAYA MAKES NO REPRESENTATIONS OR WARRANTIES THAT THE STEPS RECOMMENDED WILL ELIMINATE SECURITY OR VIRUS THREATS TO CUSTOMERS' SYSTEMS. IN NO EVENT SHALL AVAYA BE LIABLE FOR ANY DAMAGES WHATSOEVER ARISING OUT OF OR IN CONNECTION WITH THE INFORMATION OR RECOMMENDED ACTIONS PROVIDED HEREIN, INCLUDING DIRECT, INDIRECT, INCIDENTAL, STATUTORY, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF AVAYA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

THE INFORMATION PROVIDED HERE DOES NOT AFFECT THE SUPPORT AGREEMENTS IN PLACE FOR AVAYA PRODUCTS. SUPPORT FOR AVAYA PRODUCTS CONTINUES TO BE EXECUTED AS PER EXISTING AGREEMENTS WITH AVAYA.

6. Revision History:

V 1.0 - January 19, 2015 - Initial Statement issued.
V 2.0 - December 1, 2017 - Updated affected versions and actions for all products and set the advisory status to Final.

Avaya customers or Business Partners should report any security issues found with Avaya products via the standard support process.
Independent security researchers can contact Avaya at securityalerts@avaya.com.

Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.

© 2015 Avaya Inc. All Rights Reserved. All trademarks identifying Avaya products by the ® or ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.