Wind River has released a security advisory pertaining to their embedded version of Linux. This advisory contains vulnerabilities that may affect Avaya systems.
The remote_glob function in sftp-glob.c and the process_put function in sftp.c in OpenSSH 5.8 and earlier, as used in FreeBSD 7.3 and 8.1, NetBSD 5.0.2, OpenBSD 4.7, and other products, allow remote authenticated users to cause a denial of service via crafted glob expressions that do not match any pathnames, as demonstrated by glob expressions in SSH_FXP_STAT requests to an sftp daemon, a different vulnerability than CVE-2010-2632. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-4755 to this issue.
Integer overflow in the agp_generic_insert_memory function in drivers/char/agp/generic.c in the Linux kernel before 2.6.38.5 allows local users to gain privileges or cause a denial of service (system crash) via a crafted AGPIOC_BIND agp_ioctl ioctl call. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1745 to this issue.
The bcm_release function in net/can/bcm.c in the Linux kernel before 2.6.39-rc6 does not properly validate a socket data structure, which allows local users to cause a denial of service or possibly have unspecified other impact via a crafted release operation. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1598 to this issue.
Multiple integer overflows in the next_pidmap function in kernel/pid.c in the Linux kernel before 2.6.38.4 allow local users to cause a denial of service via a crafted getdents or readdir system call. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1593 to this issue.
Multiple integer overflows in the agp_allocate_memory and agp_create_user_memory functions in drivers/char/agp/generic.c in the Linux kernel before 2.6.38.5 allow local users to trigger buffer overflows, and consequently cause a denial of service or possibly have unspecified other impact, via vectors related to calls that specify a large number of memory pages. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1746 to this issue.
The raw_release function in net/can/raw.c in the Linux kernel before 2.6.39-rc6 does not properly validate a socket data structure, which allows local users to cause a denial of service or possibly have unspecified other impact via a crafted release operation. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1748 to this issue.
Heap-based buffer overflow in the ldm_frag_add function in fs/partitions/ldm.c in the Linux kernel 2.6.37.2 and earlier might allow local users to gain privileges or obtain sensitive information via a crafted LDM partition table. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1017 to this issue.
More information about these vulnerabilities can be found in the security advisories issued by Wind River (A login is required):
| Product: | Affected Version(s): | Risk Level: | Actions: |
|---|---|---|---|
| Avaya 96x1 IP Deskphones | 6.0.x thru 6.6.0 | Low | For SIP, upgrade to 7.0 or later. For H.323 and B189, upgrade to 6.6.1 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-2010-4755 CVE-2011-1745 CVE-2011-1598 CVE-2011-1593 CVE-2011-1746 CVE-2011-1748 CVE-2011-1017 |
These are a low risk due to restricted local user access. |
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 - October 25, 2011 - Initial Statement issued.
V 2.0 - March 14, 2016 - Updated Avaya 96x1 IP Deskphones affected versions and actions, and changed 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].
© 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.