Avaya 9601/9608/9608G/9611G/9621G/9641G and B189 Endpoint Command Injection, Memory Modification and Code Execution Vulnerabilities

Original Release Date: February 27, 2014
Last Revised: February 27, 2014
Number: ASA-2014-099
Risk Level: Medium
Advisory Version: 1.0
Advisory Status: Final

1. Overview:

Avaya's IP endpoints retrieve an upgrade and settings files from a configured HTTP server during boot up. The IP address of the HTTP server is set up in the endpoint either via DHCP or manually by entering a special key sequence with a password on the key pad. Modification to the upgrade and settings files require user access and permissions on the HTTP server. The parsing software on the IP endpoints is only executed while reading these files.

A command injection vulnerability exists in the parsing software which could potentially execute arbitrary shell commands as root. This would allow arbitrary changes to the kernel and all applications on the endpoint.

A memory modification and code execution vulnerability exists in the parsing software for SIP endpoints. This vulnerability could potentially cause a buffer overflow on the stack, thus allowing arbitrary changes to memory and execution of code as root.

Avaya would like to thank Ang Cui of Red Balloon Security for reporting these issues.

2. Avaya IP Endpoints affected:

Product: Affected Version(s): Risk Level: Actions:
Avaya 9601/9608/9608G/9611G/9621G/9641G IP Deskphones 6.3.1.21 and earlier SIP software Medium Upgrade to SIP software release 6.3.1.22 or later.
Avaya 9608/9608G/9611G/9621G/9641G IP Deskphones 6.3.1.51 and earlier H.323 software Medium Upgrade to H.323 software release 6.3.1.52 or later.
Avaya B189 IP Conference Phone 1.0.0.22 and earlier H.323.software Medium Upgrade to 1.0.0.23 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, specifically for network traffic between the Avaya endpoints, call server and HTTP server. 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
Command Injection This is rated a Medium risk because of the potential for execution of shell commands as root by a user with access and proper permissions to the configuration server.
Memory Modification and Code This is rated a Medium risk to IP endpoints using SIP software because of the potential to cause a buffer overflow by a user with access and proper permissions to the configuration server.

3. 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.

4. 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.

5. Revision History:

V 1.0 - February 27, 2014 - Initial Statement issued.

Avaya customers or Business Partners should report any security issues found with Avaya products via the standard support process.
Independent security researchers can contact Avaya at securityalerts@avaya.com.

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