krb5 security update (RHSA-2015-0794)

Original Release Date: May 5, 2015
Last Revised: November 8, 2016
Number: ASA-2015-175
Risk Level: Medium
Advisory Version: 7.0
Advisory Status: Final

1. Overview:

Kerberos is a networked authentication system which allows clients and servers to authenticate to each other with the help of a trusted third party, the Kerberos KDC.

The following security issues are fixed with this release:

A use-after-free flaw was found in the way the MIT Kerberos libgssapi_krb5 library processed valid context deletion tokens. An attacker able to make an application using the GSS-API library (libgssapi) could call the gss_process_context_token() function and use this flaw to crash that application. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-5352 to this issue.

If kadmind were used with an LDAP back end for the KDC database, a remote, authenticated attacker who has the permissions to set the password policy could crash kadmind by attempting to use a named ticket policy object as a password policy for a principal. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-5353 to this issue.

It was found that the krb5_read_message() function of MIT Kerberos did not correctly sanitize input, and could create invalid krb5_data objects. A remote, unauthenticated attacker could use this flaw to crash a Kerberos child process via a specially crafted request. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-5355 to this issue.

A double-free flaw was found in the way MIT Kerberos handled invalid External Data Representation (XDR) data. An authenticated user could use this flaw to crash the MIT Kerberos administration server (kadmind), or other applications using Kerberos libraries, via specially crafted XDR packets. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-9421 to this issue.

It was found that the MIT Kerberos administration server (kadmind) incorrectly accepted certain authentication requests for two-component server principal names. A remote attacker able to acquire a key with a particularly named principal (such as "kad/x") could use this flaw to impersonate any user to kadmind, and perform administrative actions as that user. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-9422 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 RHEL6 with affected packages installed:

Product: Affected Version(s): Risk Level: Actions:
Avaya CMS R17 thru R17 R4 Low Upgrade to R17 R5 or later.
Avaya Breeze™ Platform 2.x, 3.0 thru 3.0 SP3 Low Upgrade to 3.0 SP4 or later.
Avaya Aura® Conferencing 8.0 thru 8.0 SP4 Medium Upgrade to 8.0 SP5 or later.
Avaya Aura® Experience Portal 6.0 thru 7.0.2 Low For 6.0, upgrade to 7.0.2 and Avaya Linux for 7.0.2 and install Linux Patch 2015-10 or later.
For 7.0 to 7.0.2, install Linux Patch 2015-10 or later.
Avaya IP Office Server Edition 8.1, 9.x Low Upgrade to 10.0 or later.
Avaya IP Office Application Server 9.x Low Upgrade to 10.0 or later.
Avaya one-X® Client Enablement Services 6.2 thru 6.2.4 Low Upgrade to 6.2.5 or later.
Avaya Aura® Session Manager 6.3.x thru 7.0.0.1 Low Upgrade to 7.0.1.0 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-5352
This is a Medium risk for Conferencing due to the potential to create a Denials of Service (DoS).
This is a Low risk for all other products as the libgssapi_krb5 is not used by default.
CVE-2014-5353
CVE-2014-5355
CVE-2014-9421
CVE-2014-9422
These are a None for all products as kadmind is not installed by default.

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® Experience Portal Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the EP 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, IS PROVIDED "AS IS", AND IS APPLICABLE ONLY TO PRODUCT VERSIONS ELIGIBLE FOR MANUFACTURER SUPPORT IN ACCORDANCE WITH AVAYA PRODUCT LIFE CYCLE POLICY. 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 - May 5, 2015 - Initial Statement issued.
V 2.0 - October 20, 2015 - Updated CMS, CE and EP affected versions and actions.
V 3.0 - November 19, 2015 - Updated CMS affected versions and actions.
V 4.0 - February 9, 2016 - Updated Conferencing affected versions and actions.
V 5.0 - May 9, 2016 - Updated one-X CES affected versions and actions.
V 6.0 - July 27, 2016 - Updated Session Manager affected versions and actions.
V 7.0 - November 8, 2016 - Updated IPOSE and IPOAS affected actions, and set 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 [email protected].

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.