GDB, the GNU debugger, allows debugging of programs written in C, C++, and other languages by executing them in a controlled fashion, then printing their data.
Several integer overflow bugs were found in gdb. If a user is tricked into processing a specially crafted executable file, it may allow the execution of arbitrary code as the user running gdb. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CAN-2005-1704 to this issue.
A bug was found in the way gdb loads .gdbinit files. When a user executes gdb, the local directory is searched for a .gdbinit file which is then loaded. It is possible for a local user to execute arbitrary commands as the user running gdb by placing a malicious .gdbinit file in a location where gdb may be run. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CAN-2005-1705 to this issue.
Several Avaya System products utilize gdb, however only Avaya services personnel have access to gdb, therefore lowering the risk of exploitation.
More information about these vulnerabilities can be found in the security advisory issued by RedHat Linux:
| Product: | Affected Version(s): | Risk Level: | Actions: |
|---|---|---|---|
| Avaya S87XX/S8500/S8300 | 1.x - 3.0 | Low | Upgrade to CM 3.1 or later |
| Avaya Sip Enablement Services (SES) |
All | Low | See recommended actions below. An update is being considered for a future release. |
| Avaya Intuity LX | All | Low | See recommended actions below. An update is being considered for a future release. |
| Avaya Messaging Storage Server | 1.x - 2.x | Low | Update to MSS 3.0 or later. |
| Avaya Message Networking | All | Low | See recommended actions below. An update is being considered for a future release. |
Recommended Actions:
For all system products which use
vulnerable
versions of gdb, Avaya recommends that customers restrict local and
network access to the server. This restriction should be enforced
through the
use of physical security, firewalls, ACLs, VPNs, and other
generally-accepted
networking practices until such time as an update becomes available
and can
be installed.
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 vendors guidance:
| Product: | Affected Version(s): | Risk Level: | Actions: |
|---|---|---|---|
| Avaya Interactive Response(IR) | All | None | Depending on the Operating System provided by customers, the affected packages may be installed on the underlying Operating System supporting the IR application. The IR application does not require the software described in this advisory. |
| CVLAN | all? | Low | See recommended actions below. |
| Avaya Integrated Management Suite(IMS) | All | None | Depending on the Operating System provided by customers, the affected packages may be installed on the underlying Operating System supporting the IMS application. The IMS application does not require the software described in this advisory. |
Recommended Actions:
Avaya recommends that customers follow
recommended actions supplied by the Operating System vendor (e.g. Red
Hat).
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 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, 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 - January 16, 2006 - Initial Statement issued.
V 2.0 - February 17, 2006 - Minor formatting changes made and added
SES to
Products table.
V 3.0 - August 28, 2006 - Updated impact for MSS.
V 4.0 - November 8, 2006 - Updated impact for Avaya
S87XX/S8500/S8300.
Send information regarding any discovered security problems with Avaya products to either the contact noted in the product's documentation or [email protected].
(c) 2006 Avaya Inc. All Rights Reserved. All trademarks identified by the (r) or ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.