Red Hat Enterprise Linux 6 kernel update (RHSA-2013-1645)

Original Release Date: December 9, 2013
Last Revised: October 12, 2015
Number: ASA-2013-560
Risk Level: Medium
Advisory Version: 3.0
Advisory Status: Final

1. Overview:

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

A flaw was found in the way the Linux kernel's IPv6 implementation handled certain UDP packets when the UDP Fragmentation Offload (UFO) feature was enabled. A remote attacker could use this flaw to crash the system or, potentially, escalate their privileges on the system. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-4387 to this issue.

A flaw was found in the way the Linux kernel handled the creation of temporary IPv6 addresses. If the IPv6 privacy extension was enabled (/proc/sys/net/ipv6/conf/eth0/use_tempaddr set to '2'), an attacker on the local network could disable IPv6 temporary address generation, leading to a potential information disclosure. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-0343 to this issue.

A flaw was found in the way the Linux kernel handled HID (Human Interface Device) reports with an out-of-bounds Report ID. An attacker with physical access to the system could use this flaw to crash the system or, potentially, escalate their privileges on the system. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-2888 to this issue.

An off-by-one flaw was found in the way the ANSI CPRNG implementation in the Linux kernel processed non-block size aligned requests. This could lead to random numbers being generated with less bits of entropy than expected when ANSI CPRNG was used. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-4345 to this issue.

It was found that the fix for CVE-2012-2375 released via RHSA-2012:1580 accidentally removed a check for small-sized result buffers. A local, unprivileged user with access to an NFSv4 mount with ACL support could use this flaw to crash the system or, potentially, escalate their privileges on the system . The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-4591 to this issue.

A flaw was found in the way IOMMU memory mappings were handled when moving memory slots. A malicious user on a KVM host who has the ability to assign a device to a guest could use this flaw to crash the host. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-4592 to this issue.

Heap-based buffer overflow flaws were found in the way the Zeroplus and Pantherlord/GreenAsia game controllers handled HID reports. An attacker with physical access to the system could use these flaws to crash the system or, potentially, escalate their privileges on the system. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2013-2889 and CVE-2013-2892 to these issues.

Two information leak flaws were found in the logical link control (LLC) implementation in the Linux kernel. A local, unprivileged user could use these flaws to leak kernel stack memory to user space. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2012-6542 and CVE-2013-3231 to these issues.

A heap-based buffer overflow in the way the tg3 Ethernet driver parsed the vital product data (VPD) of devices could allow an attacker with physical access to a system to cause a denial of service or, potentially, escalate their privileges. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-1929 to this issue.

Information leak flaws in the Linux kernel could allow a privileged, local user to leak kernel memory to user space. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2012-6545, CVE-2013-1928, CVE-2013-2164 and CVE-2013-2234 to these issues.

A format string flaw was found in the Linux kernel's block layer. A privileged, local user could potentially use this flaw to escalate their privileges to kernel level (ring0). The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-2851 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 R2 Medium Upgrade to R17 R3 or later.
Avaya Aura® Collaboration Environment 2.x Medium Upgrade to 3.0 or later.
Avaya Aura® Experience Portal 7.0.x, 6.0 including SP1 thru SP3 Medium For 6.0 SP1 and SP2, upgrade to 6.0 SP3 and Avaya Linux for 6.0 SP3, and install 6.0 SP3 Security Updates.
For 6.0 SP3, install 6.0 SP3 Security Updates.
Refer to the Security Updates page for details.

For 7.0, install 7.0 Security Updates.
Refer to the Security Updates page for details.

For 7.0.1, install 7.0.1 Security Updates.
Refer to the Security Updates page for details.
Avaya IP Office Server Edition 8.1 thru 9.1.3 Medium Upgrade to 9.1.4 or later.
Avaya IP Office Application Server 9.0 thru 9.1.3 Medium Upgrade to 9.1.4 or later.
Avaya one-X® Client Enablement Services 6.2 including SP1 Medium Upgrade to 6.2 SP2 or later.
Avaya Aura® Session Manager 6.3.0 thru 6.3.7 Low Upgrade to 6.3.8 or later.

Recommended Actions for System Products:
Avaya strongly recommends following the 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-2013-0343
CVE-2013-4387
These are a Low risk for all products because IPv6 is not used or supported by default.
CVE-2013-2888
CVE-2013-2889
CVE-2013-2892
This is a Low risk for all products because Human Interface Device reports are not used or support by default.
CVE-2013-4345 This is a Low risk for all products because the ANSI CPRNG is not used by default.
CVE-2013-4591 This is a Low risk for all products because NFSv4 mounts with ACL support are not used by default.
CVE-2013-4592
This is a Low risk for all products because these products are not used as a KVM host.
CVE-2012-6542
CVE-2013-3231
These are a Low risk for all products because no critical or sensitive information is exposed.
CVE-2013-1929 This is a Low risk for all products because exploit requires privileged user permissions which would not provide additional capability.
CVE-2012-6545
CVE-2013-1928
CVE-2013-2164
CVE-2013-2234
These are a Low risk for all products because exploit requires privileged user permissions which would not provide additional capability.
CVE-2013-2851 This is a Low risk for Session Manager because it would not provide privilege users additional capability.
This is a Medium risk for all other products due to the potential for privilege escalation.

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.
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.
Avaya Secure Access Link Gateway Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the SAL Gateway application.

Recommended Actions for Software-Only Products:
In the event that the affected package is installed, Avaya recommends following the 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 - December 9, 2013 - Initial Statement issued.
V 2.0 - February 13, 2015 - Changed CMS, CE, EP, one-X CES and SM affected versions and actions.
V 3.0 - October 12, 2015 - Changed IPOSE and IPOAS affected versions and 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 securityalerts@avaya.com.

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

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