OpenSSH is a suite of tools developed by the OpenBSD team for interoperating with the SSH protocol.
The privilege separation monitor in OpenSSH was found to contain a possible authentication flaw. The unprivileged process of OpenSSH's daemon (when configured for privilege separation) could possibly allow a login without presenting correct authentication. However taking advantage of this issue would require an attacker to be able to influence the behavior of the unprivileged process. There is no known way to do so today. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2006-5794 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 S87XX/S8500/S8300 | CM 2.x and CM 3.x | Low | Upgrade to CM 4.0 or later. |
| Avaya Intuity LX | IALX 1.1 | Low | Upgrade to IALX 2.0 or later. |
| Avaya Messaging Storage Server | MSS 3.0 | Low | Upgrade to MSS 3.1 or later. |
| Avaya Message Networking | All | Low | See recommended actions below. This issue will be addressed in accordance with Avaya's Product Security Vulnerability Response Policy |
| Avaya CCS/SES | SES 4.0 and earlier | Low | Upgrade to SES 5.0 or later |
Recommended Actions:
For all system products which use
vulnerable
versions of OpenSSH, 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: |
|---|---|---|---|
| CVLAN | All | None | Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the CVLAN application. The CVLAN application does not require the software described in this advisory. |
| Avaya Integrated Management Suite(IMS) | All | Low | See recommended actions below. |
Recommended Actions:
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 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 - February 1, 2007 - Initial Statement issued.
V 2.0 - August 26, 2008 - Changed CM and SES recommended actions.
V 3.0 - February 12, 2009 - Changed MSS and IALX affected versions and
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].
© 2007 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.