The kernel packages contain the Linux kernel, the core of any Linux operating system.
This update fixes the following security issues:
* A flaw in the dccp_rcv_state_process() function could allow a remote attacker to cause a denial of service, even when the socket was already closed. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1093 to this issue.
* Multiple buffer overflow flaws were found in the Linux kernel's Management Module Support for Message Passing Technology (MPT) based controllers. A local, unprivileged user could use these flaws to cause a denial of service, an information leak, or escalate their privileges. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2011-1494 and CVE-2011-1495 to these issues.
* A missing validation of a null-terminated string data structure element in the bnep_sock_ioctl() function could allow a local user to cause an information leak or a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1079 to this issue.
* Missing error checking in the way page tables were handled in the Xen hypervisor implementation could allow a privileged guest user to cause the host, and the guests, to lock up. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1166 to this issue.
* A flaw was found in the way the Xen hypervisor implementation checked for the upper boundary when getting a new event channel port. A privileged guest 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-2011-1763 to this issue.
* The start_code and end_code values in "/proc/[pid]/stat" were not protected. In certain scenarios, this flaw could be used to defeat Address Space Layout Randomization (ASLR). The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-0726 to this issue.
* A missing initialization flaw in the sco_sock_getsockopt() function could allow a local, unprivileged user to cause an information leak. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1078 to this issue.
* A missing validation of a null-terminated string data structure element in the do_replace() function could allow a local user who has the CAP_NET_ADMIN capability to cause an information leak. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1080 to this issue.
* A buffer overflow flaw in the DEC Alpha OSF partition implementation in the Linux kernel could allow a local attacker to cause an information leak by mounting a disk that contains specially-crafted partition tables. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1163 to this issue.
* Missing validations of null-terminated string data structure elements in the do_replace(), compat_do_replace(), do_ipt_get_ctl(), do_ip6t_get_ctl(), and do_arpt_get_ctl() functions could allow a local user who has the CAP_NET_ADMIN capability to cause an information leak. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2011-1170, CVE-2011-1171 and CVE-2011-1172 to these issues.
* A heap overflow flaw in the Linux kernel's EFI GUID Partition Table (GPT) implementation could allow a local attacker to cause a denial of service by mounting a disk that contains specially-crafted partition tables. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1577 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.2.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 14 or later | Medium | Upgrade to Applicaiton Server 5300 with Patch Bundle 14 or later. |
| Avaya Aura® Communication Manager | 5.2.x, 6.0.x, 6.2.x | Low | Communication Manager 5.2.x: Upgrade to Communication Manager 5.2.1 with Kernel Service Pack #5 or later. Communication Manager 6.0.x: Upgrade to Communication Manager 6.2 or later. |
Avaya Communication Server 1000:
|
6.0 through 7.5 | Low | Upgrade to 7.6 or later. |
| Avaya Aura® Conferencing Standard Edition | 6.0 including 6.0 SP1 | 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 7.0 or later. |
| Avaya IP Office Application Server | 6.1, 7.0 | Medium | Upgrade to IP Office Application Server 8.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.0.x, 6.1, 6.1.1 | Medium | Upgrade to Presence Services 6.1.2 or later. |
| Avaya Aura® Session Manager | 1.1.x, 5.2.x, 6.0.x ,6.1 thru 6.1.4 | Medium | Upgrade to Session Manager 6.1.5 or later. |
| Avaya Aura® System Manager | 5.2.x, 6.0.x, 6.1 thru 6.1.3 | Medium | Upgrade to System Manager 6.1.4 or later. |
| Avaya Aura® System Platform | 1.1, 6.0 thru 6.0.3.5.3 | Medium | Upgrade to System Platform 6.0.3 with patch 6.0.3.6.3 or later. |
| Avaya Aura® Communication Manager Utility Services | 6.x | None | See Mitigating Factors table below. |
| Avaya Voice Portal | 5.0, 5.1, 5.1.1 | Medium | Upgrade to Voice Portal 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
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-2011-0726 CVE-2011-1078 CVE-2011-1079 CVE-2011-1080 CVE-2011-1163 CVE-2011-1170 CVE-2011-1171 CVE-2011-1172 CVE-2011-1577 |
The risk is Low for all products except Utility Services as exploitation
of this vulnerability would require local user access, and exploitation
could only result in an information leak. The risk is None for Utility Services as a local user with permissions to exploit these vulnerabilities is not supported. |
|
CVE-2011-1093 |
The risk is None for all products as DCCP is not used. |
|
CVE-2011-1166 |
The risk is Low for System Platform because it is a Host OS, but would require a privileged user to exploit. The risk is None for all products except except System Platform because they are either running as a guest OS, or do not make use of Xen. |
|
CVE-2011-1494 CVE-2011-1495 |
The risk is Medium for AS5300, IP Office Application Server, IQ,
Presence Services, Session Manager, System Manager, System Platform, and
Voice Portal because of the potential for escalation of privileges. The risk is Low for Aplication Enablement Services, Communication Manager, CS1000, and Conferencing because there are no MPT controllers that would allow this exploit. The risk is None for Utility Services as a local user with permissions to exploit these vulnerabilities is not supported. |
|
CVE-2011-1763 |
The risk is Medium for System Platform because it is a Host OS, and this vulnerability could result in a privilege escalation. The risk is None for all other products because they are either running as a guest OS, or do not make use of Xen. |
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.
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 - July 21, 2011 - Initial Statement issued.
V 2.0 - March 5, 2012 - Updated affected versions and actions for AS5300, IP Office AS, PS, SM, SMGR, and VP.
V 3.0 - April 6, 2012 - Updated affected versions and actions for AES, CM, and SP.
V 4.0 - March 21, 2013 - Updated CM and SM affected versions and actions.
V 5.0 - August 5, 2014 - Updated CS1000 and Conferencing Standard Edition affected versions and actions.
V 6.0 - July 2, 2015 - Updated IQ 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.
© 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.