kernel security, bug fix, and enhancement update (RHSA-2011-1479)

Original Release Date: January 6, 2012
Last Revised: December 16, 2013
Number: ASA-2011-422
Risk Level: Medium
Advisory Version: 5.0
Advisory Status: Interim

1. Overview:

The kernel packages contain the Linux kernel, the core of any Linux operating system.

This update fixes the following security issues:

Using PCI passthrough without interrupt remapping support allowed Xen hypervisor guests to generate MSI interrupts and thus potentially inject traps. A privileged guest user could use this flaw to crash the host or possibly escalate their privileges on the host. The fix for this issue can prevent PCI passthrough working and guests starting. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1898 to this issue.

A flaw was found in the way CIFS (Common Internet File System) shares with DFS referrals at their root were handled. An attacker on the local network who is able to deploy a malicious CIFS server could create a CIFS network share that, when mounted, would cause the client system to crash. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-3363 to this issue.

A NULL pointer dereference flaw was found in the way the Linux kernel's key management facility handled user-defined key types. A local, unprivileged user could use the keyctl utility to cause a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-4110 to this issue.

A flaw in the way memory containing security-related data was handled in tpm_read() could allow a local, unprivileged user to read the results of a previously run TPM command. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1162 to this issue.

A NULL pointer dereference flaw was found in the Linux kernel's HFS file system implementation. A local attacker could use this flaw to cause a denial of service by mounting a disk that contains a specially-crafted HFS file system with a corrupted MDB extent record. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-2203 to this issue.

The I/O statistics from the taskstats subsystem could be read without any restrictions. A local, unprivileged user could use this flaw to gather confidential information, such as the length of a password used in a process. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-2494 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 components/packages installed:
Product: Affected Version(s): Risk Level: Actions:
Avaya Aura® Application Enablement Services 5.2 thru 5.2.3, 6.1 thru 6.1.1 Medium For 5.2 thru 5.2.3, upgrade to 5.2.4 or later, or upgrade to 6.1.2 or later.
For 6.1 thru 6.1.1 upgrade to 6.1.2 or later.
Avaya Aura® Application Server 5300:
  • SIP Core
2.0 thru 2.0 PB19 Medium Upgrade to 2.0 PB26 or later.
Avaya Aura® Communication Manager 5.2.x, 6.0 thru 6.2.x Low Upgrade to CM 6.3 or later.
Avaya Communication Server 1000:
  • CS1000E
  • CS1000M
  • CS1000E/CS1000M Signaling Server
6.0, 7.0, 7.5 Medium Upgrade to 7.6 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 6.x, 7.x, 8.x Medium Upgrade to 9.0 or later.
Avaya IQ 5.x Medium See recommended actions below.  This issue will be addressed in accordance with section five of Avaya's Product Security Vulnerability Response Policy
Avaya Aura® Messaging 6.0.x Low See recommended actions below.  This issue will be addressed in accordance with section five of Avaya's Product Security Vulnerability Response Policy
Avaya Aura® Presence Services 6.0, 6.1.x Medium Upgrade to 6.2 or later.
Avaya Proactive Contact 5.0.x Medium Upgrade to 5.1 or later.
Avaya Aura® Session Manager 1.x, 5.x, 6.0 thru 6.2.1 Low Upgrade to 6.2.2 or later.
Avaya Aura® SIP Enablement Services 5.2.x Low See recommended actions below. This advisory will not be addressed as no further releases are planned.
Avaya Aura® System Manager 5.x, 6.x thru 6.2.2 Medium Upgrade to 6.2.3 or later.
Avaya Aura® System Platform 1.1, 6.0, 6.2 Medium For 1.1 and 6.0, upgrade to 6.2 with patch 6.2.1.0.9 or later.
For 6.2, apply patch 6.2.1.0.9 or later.
Avaya Aura® Communication Manager Utility Services 6.0, 6.1, 6.2 Low For 6.0 and 6.1, upgrade to 6.1 with patch 6.1.0.9.8 or later.
For 6.2, upgrade to 6.2 with patch 6.2.5.0.15 or later.
Avaya Voice Portal 5.x thru 5.1.2 Medium Upgrade to Avaya Enterprise Linux 5.1 Service Pack 3 and Voice Portal 5.1 Service Pack 3 or later.

Recommended Actions for System Products:
Avaya strongly recommends that customers follow 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 customers should not modify the System Product operating system or application 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-2011-1898
CVE-2011-3363
These are rated None for CM, Messaging and Utility Services since the affected components are not installed.
These are rated Low for SM since the affected components are not used.
These are rated Medium for AES, AS5300, CS1000, Conferencing, IP Office, IQ, Presence Services, PC, SM, SP
and VP since a local attacker could crash the host OS or cause a Denial-of-Service of critical applications.
CVE-2011-4110
This is rated Low for SM since the affected components are not used.
This is rated Low for CM, Messaging and Utility Services since only root-level users could perform this attack.
These are rated Medium for AES, AS5300, CS1000, Conferencing, IP Office, IQ, Presence Services, PC, SM, SP
and VP since a local attacker could crash the host OS or cause a Denial-of-Service of critical applications.
CVE-2011-1162
CVE-2011-2203
CVE-2011-2494
These are a low for all products as no critical system applications would be affected.

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 4.x/5.x Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the AES application.
CVLAN Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the CVLAN application.
Avaya Aura® Experience Portal Depending on the Operating System provided by customers, 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 provided by customers, the affected package may be installed on the underlying Operating System supporting the IMS application.
Avaya Aura® Presence Services Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the PS application.
Avaya Aura® System Manager 1.0 Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the SMGR application.
Avaya Voice Portal Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the VP application.

Recommended Actions for Software-Only Products:
In the event that the affected package is installed, Avaya recommends that customers follow 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 6, 2012 - Initial Statement issued.
V 2.0 - April 2, 2013 - Updated AES, AS5300, PC, SMGR, SP, US and VP affected versions and actions.
V 3.0 - April 23, 2013 - Updated AES and SP affected versions and actions.
V 4.0 - August 20, 2013 - Updated CM, CS1000, Conferencing, SM and SP affected versions and actions.
V 5.0 - December 16, 2013 - Updated IPO affected versions and actions.

Send information regarding any discovered security problems with Avaya products to either the contact noted in the product's documentation or securityalerts@avaya.com.

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

© 2011 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.