The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security fixes:
The maximum file offset handling for ext4 file systems could allow a local, unprivileged user to cause a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-2695 to this issue.
IPv6 fragment identification value generation could allow a remote attacker to disrupt a target system's networking, preventing legitimate users from accessing its services. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-2699 to this issue.
A malicious CIFS (Common Internet File System) server could send a specially-crafted response to a directory read request that would result in a denial of service or privilege escalation on a system that has a CIFS share mounted. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-3191 to this issue.
A local attacker could use mount.ecryptfs_private to mount (and then access) a directory they would otherwise not have access to. Note: To correct this issue, the RHSA-2011:1241 ecryptfs-utils update must also be installed. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1833 to this issue.
A flaw in the taskstats subsystem could allow a local, unprivileged user to cause excessive CPU time and memory use. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-2484 to this issue.
Mapping expansion handling could allow a local, unprivileged user to cause a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-2496 to this issue.
GRO (Generic Receive Offload) fields could be left in an inconsistent state. An attacker on the local network could use this flaw to cause a denial of service. GRO is enabled by default in all network drivers that support it. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-2723 to this issue.
RHSA-2011:1065 introduced a regression in the Ethernet bridge implementation. If a system had an interface in a bridge, and an attacker on the local network could send packets to that interface, they could cause a denial of service on that system. Xen hypervisor and KVM (Kernel-based Virtual Machine) hosts often deploy bridge interfaces. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-2942 to this issue.
A flaw in the Xen hypervisor IOMMU error handling implementation could allow a privileged guest user, within a guest operating system that has direct control of a PCI device, to cause performance degradation on the host and possibly cause it to hang. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-3131 to this issue.
IPv4 and IPv6 protocol sequence number and fragment ID generation could allow a man-in-the-middle attacker to inject packets and possibly hijack connections. Protocol sequence number and fragment IDs are now more random. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-3188 to this issue.
A flaw in the kernel's clock implementation could allow a local, unprivileged user to cause a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-3209 to this issue.
Non-member VLAN (virtual LAN) packet handling for interfaces in promiscuous mode and also using the be2net driver could allow an attacker on the local network to cause a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-3347 to this issue.
A flaw in the auerswald USB driver could allow a local, unprivileged user to cause a denial of service or escalate their privileges by inserting a specially-crafted USB device. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2009-4067 to this issue.
A flaw in the Trusted Platform Module (TPM) implementation could allow a local, unprivileged user to leak information to user space. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1160 to this issue.
A local, unprivileged user could possibly mount a CIFS share that requires authentication without knowing the correct password if the mount was already mounted by another local user. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1585 to this issue.
More information about these vulnerabilities can be found in the security advisory issued by Red Hat:
| Product: | Affected Version(s): | Risk Level: | Actions: |
|---|---|---|---|
| Avaya Aura® Application Enablement Services | 5.x, 6.1, 6.1.1 | Low | Upgrade to Application Enablement Services 6.1.2 or later. |
Avaya Aura® Application Server 5300:
|
2.0 without PB 19 | Medium | Upgrade to Application Server 5300 Release 2.0 with Patch Bundle 19 or later. |
| Avaya Aura® Communication Manager | 5.x, 6.x | Medium |
For 6.0.x and earlier, upgrade to 6.3 or later. For 6.2, install Kernel Service Pack 1 or later. |
Avaya Communication Server 1000:
|
6.0 thru 7.5 | Medium | Upgrade to 7.6 or later. |
| Avaya Aura® Conferencing Standard Edition | 6.x | Low | 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.0.x, 8.0.x | Low | Upgrade to 9.0 or later |
| Avaya IQ | 5.2 thru 5.2.5 | Low | Upgrade to 5.2.6 and install Patch 2 or later. |
| Avaya Aura® Messaging | 6.0 thru 6.2 | Low | Upgrade to 6.3 or later. |
| Avaya Aura® Presence Services | 6.0.x, 6.1, 6.1.1 | Low | Upgrade to Presence Services 6.1.2 or later. |
| Avaya Proactive Contact | 5.0.x | Low | Upgrade to 5.1 or later. |
| Avaya Aura® Session Manager | 1.1.x, 5.2.x, 6.0.x, 6.1 thru 6.1.5 | Low | Upgrade to Session Manager 6.1.6 or later |
| Avaya Aura® System Manager | 5.x, 6.0 thru 6.2.2 | Low | Upgrade to 6.2.3 or later. |
| Avaya Aura® System Platform | 1.x, 6.0 thru 6.0.3.5.3, 6.2 | Medium | For System Platform 1.x, 6.0.x, Upgrade to System Platform 6.0.3 with Patch 6.0.3.6.3 or later. For System Platform 6.2, Upgrade to 6.2.1.0.9 or later. |
| Avaya Aura® Communication Manager Utility Services | 6.0, 6.1 | Low | Upgrade to Communication Manager Utility Services 6.2 or later. |
| Avaya Voice Portal | 5.0 thru 5.1.2 | Low | Upgrade to 5.1.3 and Avaya Linux for 5.1.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.
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-2009-4067 | The risk level is None for all products because the Auerswald PBX/System Telephone USB driver is not used. |
| CVE-2011-1160 | The risk is Low for all products because no critical systems would be affected. |
| CVE-2011-1585 | The risk level is None for all products because CIFS shares are not used. |
| CVE-2011-1833 | The risk level is None for all products because ecrypt file systems are not used. |
|
CVE-2011-2484 CVE-2011-2496 |
The risk is Low for all products because an authenticated user able to exploit these vulnerabilities would not gain additional privileges. |
| CVE-2011-2695 | The risk level is None for all products because the ext4 file system is not used. |
| CVE-2011-2699 | The risk is Medium for Communication Manager, AS5300, CS1000, and System Platform when deployed with IPv6 enabled because of the complexity of the exploit. The risk level is None for Communication Manager, AS5300, CS1000, and System Platform when deployed without IPv6 enabled. The risk level is None for all other products because IPv6 is not supported. |
| CVE-2011-2723 | The risk level is None for all products because GRO is either disabled by default, or the Ethernet drivers used do not support GRO. |
| CVE-2011-2942 | The risk level is None for System Platform because the kernel update in RHSA-2011-1065 has not been introduced in a System Platform release. The risk level is None for all other products because bridged interfaces are not used. |
| CVE-2011-3131 | The risk is Low for System Platform because privileged user access is required. The risk level is None for all other products because they don't run Xen. |
| CVE-2011-3188 | The risk is Low for all products because of the complexity of the brute force attack, the need to gain man-in-the-middle access, and the fact that TLS can be used to secure connections. |
| CVE-2011-3191 | The risk level is None for all products because CIFS shares are not used. |
| CVE-2011-3209 | The risk is Low for all products because an authenticated user able to exploit these vulnerabilities would not gain additional privileges. |
| CVE-2011-3347 | The risk level is None for all products because the be2net driver is not used. |
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.
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.
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.
V 1.0 - December 5, 2011 - Initial Statement issued.
V 2.0 - March 6, 2012 - Updated AS 5300, PS, and SM affected versions and actions.
V 3.0 - April 9, 2012 - Updated AES, CM US, and SP affected versions and actions.
V 4.0 - August 13, 2015 - Updated affected versions and actions of IQ, Messaging, Proactive Contact, SMGR, VP and actions for CM, CES, IPOAS, SP, 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.
© 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.