kernel security and bug fix update (RHSA-2012-0107 RHSA-2012-0517)

Original Release Date: April 5, 2012
Last Revised: September 30, 2015
Number: ASA-2012-143
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:

Using the SG_IO ioctl to issue SCSI requests to partitions or LVM volumes resulted in the requests being passed to the underlying block device. If a privileged user only had access to a single partition or LVM volume, they could use this flaw to bypass those restrictions and gain read and write access (and be able to issue other SCSI commands) to the entire block device. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-4127 to this issue.

A flaw was found in the way the Linux kernel handled robust list pointers of user-space held futexes across exec() calls. A local, unprivileged user could use this flaw to cause a denial of service or, eventually, escalate their privileges. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-0028 to this issue.

A flaw was found in the Linux kernel in the way splitting two extents in ext4_ext_convert_to_initialized() worked. A local, unprivileged user with the ability to mount and unmount ext4 file systems could use this flaw to cause a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-3638 to this issue.

A flaw was found in the way the Linux kernel's journal_unmap_buffer() function handled buffer head states. On systems that have an ext4 file system with a journal mounted, 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-2011-4086 to this issue.

A divide-by-zero flaw was found in the Linux kernel's igmp_heard_query() function. An attacker able to send certain IGMP (Internet Group Management Protocol) packets to a target system could use this flaw to cause a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-0207 to this issue.

More information about these vulnerabilities can be found in these security advisories 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 6.2 and earlier Medium Upgrade to 6.3 or later.
Avaya Aura® Application Server 5300:
  • SIP Core
2.0 without Patch Bundle 28, 3.0 including Patch Bundle 1 and 2 Medium For 2.0 install Patch Bundle 28 or upgrade to 3.0 and install Patch Bundle 3 or later.
For 3.0 install Patch Bundle 3 or later.
Avaya Aura® Communication Manager 6.0 thru 6.2.x Low Upgrade to 6.3 or later.
Avaya Communication Server 1000:
  • CS1000E
  • CS1000M
  • CS1000E/CS1000M Signaling Server
6.x, 7.x Low See recommended actions and Mitigating Factors table below. This advisory will not be addressed as no further releases are planned.
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 8.0 or later.
Avaya IP Office Application Server 6.x, 7.x, 8.x Medium Upgrade to 9.0 or later
Avaya IQ 5.2 thru 5.2.5 Medium Upgrade to 5.2.6 and install Patch 2 or later.
Avaya Aura® Presence Services 6.x Low Upgrade to Aura Presence Services 7.0 or later. Further information about this version, as well as the overall Aura 7.0 release, is available on support.avaya.com.
Avaya Proactive Contact 5.0.x Medium Upgrade to 5.1 or later.
Avaya Aura® Messaging 6.0 thru 6.2 SP4 Low Upgrade to 6.3 or later.
Avaya Aura® Session Manager 1.x, 5.x, 6.0.x, 6.1.x, 6.2.x Low Upgrade to 6.3 or later.
Avaya Aura® System Manager 5.2.x, 6.0 thru 6.3.3 Medium Upgrade to 6.3.4 or later.
Avaya Aura® System Platform 6.2.x and earlier Low Upgrade to 6.3 or later
Avaya Aura® Communication Manager Utility Services 6.0.x, 6.1.x, 6.2 Medium For 6.0 and 6.1, upgrade to 6.2 and install Service Pack 6.2.5.0.15 or later.
For 6.2, install Service Pack 6.2.5.0.15 or later
Avaya Voice Portal 5.x Medium Upgrade to Experience Portal 7.0 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-3638
CVE-2011-4086
These are rated a Low Risk for CM, Messaging, CS1000, PS, SP and SM since the ext4 filesystem is either not used or escalated privileges would be required to manipulate the filesystem.
These are rated a Medium Risk for all other products since an unprivileged user could use this flaw to cause a denial of service or possibly escalate their privileges
CVE-2011-4127
This is rated a Low Risk for CM and Messaging since LVM is not used, and rated Low for CS1000, PS, SP and SM since privileges users would be required to exploit.
This is rated a Medium Risk for all other products since an unprivileged user could use this flaw to cause a denial of service or possibly escalate their privileges
CVE-2012-0028
This is rated a Low Risk for CM, Messaging, CS1000, PS, SP and SM since only privileged users can upload/run a program.
This is rated a Medium Risk for all other products since an unprivileged user could use this flaw to cause a denial of service or possibly escalate their privileges
CVE-2012-0207
This is rated a Low Risk for CM, Messaging, CS1000, PS, SP and SM since IGMP is either blocked by firewall rules or is not used.
This is rated a Medium Risk for all other products since an unprivileged user could use this flaw to cause a denial of service or possibly escalate their privileges

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 Secure Access Link Gateway Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the SAL Gateway 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 - April 5, 2012 - Initial Statement issued.
V 2.0 - July 3, 2012 - Added RHSA-2012-0517 to this Advisory.
V 3.0 - July 22, 2015 - Updated AES, AS5300, CS1000, CSE, IQ, CM, IPOAS, Messaging, PC, Session Manager, System Manager, SP, Utility Services, and VP affected versions and actions.
V 4.0 - September 3, 2015 - Added Messaging affected versions and actions.
V 5.0 - September 30, 2015 - Added PS actions, and set advisory status to Final.

Send information regarding any discovered security problems with Avaya products to either the contact noted in the product's documentation or [email protected].

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

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