Kerberos is a network authentication system which allows clients and servers to authenticate to each other through use of symmetric encryption and a trusted third party, the KDC.
A flaw was found in the way the Kerberos Authentication Service and Key Distribution Center server (krb5kdc) handled Kerberos v4 protocol packets. An unauthenticated remote attacker could use this flaw to crash the krb5kdc daemon, disclose portions of its memory, or possibly execute arbitrary code using malformed or truncated Kerberos v4 protocol requests. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2008-0062 and CVE-2008-0063 to these issues.
This issue only affected krb5kdc with Kerberos v4 protocol compatibility enabled, which is the default setting on Red Hat Enterprise Linux 4. Kerberos v4 protocol support can be disabled by adding "v4_mode=none" (without the quotes) to the "[kdcdefaults]" section of /var/kerberos/krb5kdc/kdc.conf.
A double-free flaw was discovered in the GSSAPI library used by Kerberos. This flaw could possibly cause a crash of the application using the GSSAPI library. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2007-5971 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 3.1.x, 4.0, 5.0 | Low | Upgrade to CM 5.1 or later. |
| Avaya Intuity AUDIX LX | IALX 2.0 | Low | See recommended actions below. This issue will be addressed in accordance with Avaya's Product Security Vulnerability Response Policy |
| Avaya EMMC | 1.0.21 | Low | Will not be addressed since no further releases of EMMC are planned. |
| Avaya Messaging Storage Server | MSS 3.x and 4.0 | Low | Upgrade to MSS 5.0 or later. |
| Avaya Message Networking | MN 3.1 | Low | See recommended actions below. This issue will be addressed in accordance with Avaya's Product Security Vulnerability Response Policy |
| Avaya SIP Enablement Services | SES 3.1.x, 4.0, 5.0 | Low | Upgrade to SES 5.1 or later. |
| Avaya Voice Portal | VP 3.x, 4.x | Low | See recommended actions below. This issue will be addressed in accordance with Avaya's Product Security Vulnerability Response Policy |
| Avaya Meeting Exchange | 5.0.0.0.52 | Low | See recommended actions below. This issue will be addressed in accordance with Avaya's Product Security Vulnerability Response Policy |
| Avaya AES | AES 4.0, 4.1, 4.2 | Low | See recommended actions below. This issue will be addressed in accordance with Avaya's Product Security Vulnerability Response Policy |
| Avaya Proactive Contact | PC 4.0 | Low | See recommended actions below. This issue will be addressed in accordance with Avaya's Product Security Vulnerability Response Policy |
Recommended Actions:
For all vulnerable system products,
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 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. |
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 - May 5, 2008 - Initial Statement issued.
V 2.0 - November 25, 2008 - Changed CM and SES recommended actions, added 4.2 to AES affected versions.
V 3.0 - January 20, 2009 - Updated MSS and EMMC 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.