Kerberos is a networked authentication system which allows clients and servers to authenticate to each other with the help of a trusted third party, the Kerberos KDC.
It was found that if a KDC served multiple realms, certain requests could cause the setup_server_realm() function to dereference a NULL pointer. A remote, unauthenticated attacker could use this flaw to crash the KDC using a specially crafted request. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2013-1418 and CVE-2013-6800 to these issues.
A NULL pointer dereference flaw was found in the MIT Kerberos SPNEGO acceptor for continuation tokens. A remote, unauthenticated attacker could use this flaw to crash a GSSAPI-enabled server application. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-4344 to this issue.
A buffer overflow was found in the KADM5 administration server (kadmind) when it was used with an LDAP back end for the KDC database. A remote, authenticated attacker could potentially use this flaw to execute arbitrary code on the system running kadmind. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-4345 to this issue.
Two buffer over-read flaws were found in the way MIT Kerberos handled certain requests. A remote, unauthenticated attacker who is able to inject packets into a client or server application's GSSAPI session could use either of these flaws to crash the application. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2014-4341 and CVE-2014-4342 to these issues.
A double-free flaw was found in the MIT Kerberos SPNEGO initiators. An attacker able to spoof packets to appear as though they are from an GSSAPI acceptor could use this flaw to crash a client application that uses MIT Kerberos. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-4343 to this issue.
More information about these vulnerabilities can be found in the security advisory issued by Red Hat:
| Product: | Affected Version(s): | Risk Level: | Actions: |
|---|---|---|---|
| Avaya CMS | R17.x | None | See Mitigating Factors table below. |
| Avaya Aura® Collaboration Environment | 2.x, 3.x | None | See Mitigating Factors table below. |
| Avaya Aura® Conferencing | 8.x | None | See Mitigating Factors table below. |
| Avaya Aura® Experience Portal | 6.0 thru 6.0.3, 7.0 thru 7.0.1 | Low | For 6.0, upgrade to 6.0.3 and Avaya Linux for 6.0.3 and install Security Updates for 6.0.3. For 6.0.3, install Security Updates for 6.0.3. For 7.0, install Security Updates for 7.0. For 7.0.1, install Security Updates for 7.0.1. |
| Avaya IP Office Server Edition | 8.1, 9.x | None | See Mitigating Factors table below. |
| Avaya IP Office Application Server | 9.x | None | See Mitigating Factors table below. |
| Avaya one-X® Client Enablement Services | 6.2 thru 6.2.3 | Low | Upgrade to 6.2.4 or later. |
| Avaya Aura® Session Manager | 6.3.x | None | See Mitigating Factors table below. |
Recommended Actions for System Products:
Avaya strongly recommends following 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 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.
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-2014-4341 CVE-2014-4342 CVE-2014-4343 |
These are a Low risk for Experience Portal and one-X CES because the
kerberos client is not used or configured by default. There is no risk for all other products listed as only the krb5-libs and/or krb5-devel packages are installed by default. |
|
CVE-2013-1418 CVE-2013-6800 CVE-2014-4344 CVE-2014-4345 |
There is no risk for all products listed because the krb5 server is not installed, only the krb5-libs, krb5-devel and/or krb5-workstation package(s) are 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: |
|---|---|
| Avaya Aura® Experience Portal | Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the EP application. |
Recommended Actions for Software-Only Products:
In the event that the affected package is installed, Avaya recommends following recommended actions supplied by Red Hat regarding their Enterprise 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 - November 14, 2014 - Initial Statement issued.
V 2.0 - February 27, 2015 - Updated EP affected versions and actions.
V 3.0 - September 18, 2015 - Updated CES affected versions and actions and set advisory status to Final.
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.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
© 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.