The kernel packages contain the Linux kernel, the core of any Linux operating system.
A flaw was found in the way the Linux kernel's floppy driver handled user space provided data in certain error code paths while processing FDRAWCMD IOCTL commands. A local user with write access to /dev/fdX could use this flaw to free (using the kfree() function) arbitrary kernel memory. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-1737 to this issue.
It was found that the Linux kernel's floppy driver leaked internal kernel memory addresses to user space during the processing of the FDRAWCMD IOCTL command. A local user with write access to /dev/fdX could use this flaw to obtain information about the kernel heap arrangement. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-1738 to this issue.
Note: A local user with write access to /dev/fdX could use these two flaws The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-1737 in combination with CVE-2014-1738 to this issue. to escalate their privileges on the system.
A NULL pointer dereference flaw was found in the rds_ib_laddr_check() function in the Linux kernel's implementation of Reliable Datagram Sockets (RDS). A local, unprivileged user could use this flaw to crash the system. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-7339 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 Aura® Application Enablement Services | 5.x thru 6.3.3 | Low | For versions prior to 6.3.3, upgrade to 6.3.3 and install Security Update
Patch 1 or later. For 6.3.3, install Security Update Patch 1 or later. |
Avaya Aura® Application Server 5300:
|
2.x, 3.0 including PB1 thru SP9 | Low | Upgrade to 3.0 SP10 or later. |
| Avaya IQ | 5.0 thru 5.2.5 | Low | Upgrade to 5.2.6 and install Patch 2 or later. |
| Avaya Aura® Communication Manager | 5.x thru 6.3 including Kernel Service Pack 1 and 2 | Low | For versions prior to 6.3, upgrade to 6.3 and install Kernel Service Pack 3
or later. For 6.3, install Kernel Service Pack 3 or later. |
Avaya Communication Server 1000:
|
6.x, 7.x | Low | See recommended actions and Mitigating Factors table below. This advisory will not be addressed as no further releases are planned. |
| Avaya Aura® Conferencing | 7.2 including SP1 thru SP5 | Low | Upgrade to 7.2 SP6 or later. |
| Avaya Aura® Conferencing Standard Edition | 6.x | Low | See recommended actions and Mitigating Factors table below. This advisory will not be addressed as no further releases are planned. It is recommended that customers migrate to one of Avaya's conferencing solutions including Aura® Conferencing 7.0 or later. |
| Avaya IP Office Application Server | 8.x | Low | Upgrade to 9.1.4 or later. |
| Avaya Meeting Exchange | 6.2 thru 6.2 SP2 | Low | Upgrade to 6.2 SP3 or later. |
| Avaya Aura® Messaging | 6.0.x thru 6.3.2 | Low | Upgrade to 6.3.3 or later. |
| Avaya one-X® Client Enablement Services | 6.1.x | Low | Upgrade to 6.2 SP4 or later. |
| Avaya Aura® Presence Services | 6.x | Low | Upgrade to Aura Presence Services 7.0 or later. Further information about this version, as well as the overall Aura 7.0 release, is available on support.avaya.com. |
| Avaya Proactive Contact | 5.0 thru 5.1.1 | Low | Upgrade to 5.1.2 or later. |
| Avaya Aura® Session Manager | 5.x thru 6.2.x | Low | Upgrade to 6.3.10 or later. |
| Avaya Aura® System Manager | 5.x thru 6.3.9 | Low | Upgrade to 6.3.10 or later. |
| Avaya Aura® System Platform | 1.x thru 6.3 including SP1 thru SP4 | Low | Upgrade to 6.3 SP5 or later. |
| Avaya Aura® Communication Manager Utility Services | 6.0 thru 6.3 including SP1 thru SP6 | Low | Upgrade to 6.3 SP7 or later. |
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-1737 CVE-2014-1738 |
There is no risk to all products listed as Avaya common servers do not have a floppy disk drive. |
| CVE-2013-7339 | This is a Low risk to all products listed as Reliable Datagram Sockets are not used or supported. |
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® Application Enablement Services | Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the AES application. |
| CVLAN | Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the CVLAN application. |
| 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. |
| Avaya Integrated Management Suite (IMS) | Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the IMS application. |
| Avaya Aura® Presence Services | Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the PS application. |
| Avaya Secure Access Link Gateway | Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the SAL Gateway 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 - August 1, 2014 - Initial Statement issued.
V 2.0 - September 15, 2015 - Updated AES, AS5300, CM, Conferencing, IQ,
Messaging, PS, SM, SMGR, SP and US affected versions and actions.
V 3.0 - October 15, 2015 - Updated IPOAS and one-X CES actions.
V 4.0 - July 21, 2016 - Updated Meeting Exchange and PC affected versions and actions,
and 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.