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

Original Release Date: February 1, 2011
Last Revised: October 10, 2013
Number: ASA-2011-020
Risk Level: Medium
Advisory Version: 5.0
Advisory Status: Final

1. Overview:

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

This update fixes the following security issues:

* A flaw was found in sctp_packet_config() in the Linux kernel's Stream Control Transmission Protocol (SCTP) implementation. A remote attacker could use this flaw to cause a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3432 to this issue.

* A missing integer overflow check was found in snd_ctl_new() in the Linux kernel's sound subsystem. A local, unprivileged user on a 32-bit system could use this flaw to cause a denial of service or escalate their privileges. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3442 to this issue.

* A heap overflow flaw in the Linux kernel's Transparent Inter-Process Communication protocol (TIPC) implementation could allow a local, unprivileged user to escalate their privileges. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3859 to this issue.

* An integer overflow flaw was found in the Linux kernel's Reliable Datagram Sockets (RDS) protocol implementation. A local, unprivileged user could use this flaw to cause a denial of service or escalate their privileges. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3865 to this issue.

* A flaw was found in the Xenbus code for the unified block-device I/O interface back end. A privileged guest user could use this flaw to cause a denial of service on the host system running the Xen hypervisor. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3699 to this issue.

* Missing sanity checks were found in setup_arg_pages() in the Linux kernel. When making the size of the argument and environment area on the stack very large, it could trigger a BUG_ON(), resulting in a local denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3858 to this issue.

* A flaw was found in inet_csk_diag_dump() in the Linux kernel's module for monitoring the sockets of INET transport protocols. By sending a netlink message with certain bytecode, a local, unprivileged user could cause a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3880 to this issue.

* Missing sanity checks were found in gdth_ioctl_alloc() in the gdth driver in the Linux kernel. A local user with access to "/dev/gdth" on a 64-bit system could use this flaw to cause a denial of service or escalate their privileges. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-4157 to this issue.

* The fix for Red Hat Bugzilla bug 484590 as provided in RHSA-2009:1243 introduced a regression. A local, unprivileged user could use this flaw to cause a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-4161 to this issue.

* A NULL pointer dereference flaw was found in the Bluetooth HCI UART driver in the Linux kernel. A local, unprivileged user could use this flaw to cause a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-4242 to this issue.

* It was found that a malicious guest running on the Xen hypervisor could place invalid data in the memory that the guest shared with the blkback and blktap back-end drivers, resulting in a denial of service on the host system. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-4247 to this issue.

* A flaw was found in the Linux kernel's CPU time clocks implementation for the POSIX clock interface. A local, unprivileged user could use this flaw to cause a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-4248 to this issue.

* Missing initialization flaws in the Linux kernel could lead to information leaks. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2010-3876 and CVE-2010-4083 to these issues.

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.x, 6.1 Low Upgrade to AES 6.1.1 or later.
Avaya Aura® Application Server 5300:
  • SIP Core
2.0 Medium Upgrade to AS5300 2.0 PB12 or later.
Avaya Aura® Communication Manager 5.2.x, 6.0.x Low Upgrade to CM 6.2 or later.
Avaya Communication Server 1000:
  • CS1000E
  • CS1000M
  • CS1000E/CS1000M Signaling Server
6.0, 7.0, 7.5 Low See mitigating factors table below. There are no current plans to resolve this issue.
Avaya Aura® Conferencing Standard Edition 6.0 Medium See Recommended Actions 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.1 Medium Upgrade to IP Office 7.0 or later
Avaya IQ 5.0, 5.1 Medium Upgrade to 5.2 or later.
Avaya Aura® Presence Services 6.0 Medium Upgrade to PS 6.1.2 or later.
Avaya Aura® Session Manager 1.1, 5.2, 6.0, 6.1 including 6.1 SP1 Medium Upgrade to SM 6.1 with SP2 or later.
Avaya Aura® System Manager 5.2, 6.0, 6.1 including 6.1 SP1 Medium Upgrade to SMGR 6.1 with SP2 or later.
Avaya Aura® System Platform 1.1, 6.0, 6.0.1, 6.0.2 Medium Upgrade to SP 6.0.3 or later.
Avaya Voice Portal 5.x Medium Upgrade to VP 5.1.2 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's product and the surrounding network from this potential vulnerability may be mitigated by ensuring these practices are implemented until such time as a product update is available or the recommended action is applied. Further restrictions as deemed necessary based on the customer's security policies may be required during this interim period.

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-2010-3858
CVE-2010-3880
CVE-2010-4161
CVE-2010-4248
These are rated Low for CM and AES since they do not use the affected kernel modules or protocols involved.
These are rated Low for the remaining products since local users, privileged or not, cannot adversely affect any critical system processes or applications.
CVE-2010-3432
This is rated Low for CM and AES since they do not use the affected kernel modules or protocols involved.
This is rated Low for Communication Server 1000 since SCTP is not used.
This is rated Low for the remaining products since local users, privileged or not, cannot adversely affect any critical system processes or applications.
CVE-2010-3442
CVE-2010-3699
CVE-2010-3859
CVE-2010-3865
CVE-2010-3876
CVE-2010-4083
CVE-2010-4157
CVE-2010-4242
CVE-2010-4247
These are rated Low for CM since only privileged users can upload and run the custom programs affected.
These are rated Low for AES since AES does not use the affected kernel modules or protocols involved.
These are rated Low for the remaining products since local users, privileged or not, cannot adversely affect any critical system processes or applications.

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 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.
Voice Portal Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the Voice Portal 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 - February 1, 2011 - Initial Statement issued.
V 2.0 - April 20, 2011 - Updated IP Office actions.
V 3.0 - July 12, 2011 - Updated SM, SMGR, and SP Actions.
V 4.0 - April 12, 2012 - Updated PS, CM and VP actions.
V 5.0 - October 10, 2013 - Updated Conferencing SE and Avaya IQ 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.