The kernel packages contain the Linux kernel, the core of any Linux operating system.
This update addresses the following security issues:
* a buffer overflow was found in the Linux kernel Partial Reliable Stream Control Transmission Protocol (PR-SCTP) implementation. This could, potentially, lead to a denial of service if a Forward-TSN chunk is received with a large stream ID. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2009-0065 to this issue.
* a memory leak was found in keyctl handling. A local, unprivileged user could use this flaw to deplete kernel memory, eventually leading to a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2009-0031 to this issue.
* a deficiency was found in the Remote BIOS Update (RBU) driver for Dell systems. This could allow a local, unprivileged user to cause a denial of service by reading zero bytes from the image_type or packet_size file in "/sys/devices/platform/dell_rbu/". The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2009-0322 to this issue.
* a deficiency was found in the libATA implementation. This could, potentially, lead to a denial of service. Note: by default, "/dev/sg*" devices are accessible only to the root user. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2008-5700 to this issue.
More information about these vulnerabilities can be found in the security advisory issued by RedHat Linux:
| Product: | Affected Version(s): | Risk Level: | Actions: |
|---|---|---|---|
| Avaya Communication Manager | CM 5.1 | Low | CM is only affected by CVE-2009-0322
which impacts S8510 servers. The Remote BIOS Update capability is currently
available but not being utilized on Avaya's S8510 servers. Upgrade to CM 5.2 or later. |
| Avaya Intuity AUDIX LX | IALX 2.0, 2.0 SP1, 2.0 SP2 | Low | See recommended actions below. This issue will be addressed in accordance with section five of Avaya's Product Security Vulnerability Response Policy |
| Avaya Message Storage Server | MSS 3.x, 4.x, 5.x | Low | See recommended actions below. This issue will be addressed in accordance with section five of Avaya's Product Security Vulnerability Response Policy |
| Avaya Message Networking | MN 3.1 | Low | See recommended actions below. This issue will be addressed in accordance with section five of Avaya's Product Security Vulnerability Response Policy |
| Avaya SIP Enablement Services | SES 5.1 | Low | SES is only affected by CVE-2009-0322
which impacts S8510 servers. The Remote BIOS Update capability is currently
available but not being utilized on Avaya's S8510 servers. Upgrade to CM 5.2 or later. |
| Avaya Voice Portal | VP 4.x | Low | See recommended actions below. This issue will be addressed in accordance with section five of Avaya's Product Security Vulnerability Response Policy |
| Avaya Meeting Exchange | MX 5.0 GA, 5.0 SP1, 5.0 SP2, 5.1 GA, 5.1 SP1 | Low | See recommended actions below. This issue will be addressed in accordance with section five of Avaya's Product Security Vulnerability Response Policy |
| Avaya Proactive Contact | PC 4.0, 4.1 | Low | See recommended actions below. This issue will be addressed in accordance with section five of Avaya's Product Security Vulnerability Response Policy |
| Avaya AES | AES 4.x to 4.2.2 | Low | See recommended actions below. This issue will be addressed in accordance with section five of Avaya's Product Security Vulnerability Response Policy |
Recommended Actions:
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. Further restrictions as deemed
necessary based on the customer's security policies
may be required during this interim period.
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: |
|---|---|
| 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. |
| 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. |
| AES 4.x | Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the AES application. |
Recommended Actions:
In the event that the affected package is installed, Avaya recommends that customers follow recommended actions supplied by RedHat 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 - April 15, 2009 - Initial Statement issued.
V 2.0 - May 12, 2009 - Changed CM and SES recommended actions.
Send information regarding any discovered security problems with Avaya products to either the contact noted in the product's documentation or [email protected].
© 2009 Avaya Inc. All Rights Reserved. All trademarks identified by the ® or ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.