Security:
An integer overflow flaw, leading to a heap-based buffer overflow, was found in the way the Intel i915 driver in the Linux kernel handled the allocation of the buffer used for relocation copies. A local user with console access could use this flaw to cause a denial of service or escalate their privileges. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-0913 to this issue.
A buffer overflow flaw was found in the way UTF-8 characters were converted to UTF-16 in the utf8s_to_utf16s() function of the Linux kernel's FAT file system implementation. A local user able to mount a FAT file system with the "utf8=1" option could use this flaw to crash the system or, potentially, to escalate their privileges. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-1773 to this issue.
A flaw was found in the way KVM handled guest time updates when the buffer the guest registered by writing to the MSR_KVM_SYSTEM_TIME machine state register (MSR) crossed a page boundary. A privileged guest user could use this flaw to crash the host or, potentially, escalate their privileges, allowing them to execute arbitrary code at the host kernel level. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-1796 to this issue.
A potential use-after-free flaw was found in the way KVM handled guest time updates when the GPA (guest physical address) the guest registered by writing to the MSR_KVM_SYSTEM_TIME machine state register (MSR) fell into a movable or removable memory region of the hosting user-space process (by default, QEMU-KVM) on the host. If that memory region is deregistered from KVM using KVM_SET_USER_MEMORY_REGION and the allocated virtual memory reused, a privileged guest user could potentially use this flaw to escalate their privileges on the host. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-1797 to this issue.
A flaw was found in the way KVM emulated IOAPIC (I/O Advanced Programmable Interrupt Controller). A missing validation check in the ioapic_read_indirect() function could allow a privileged guest user to crash the host, or read a substantial portion of host kernel memory. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-1798 to this issue.
A race condition in install_user_keyrings(), leading to a NULL pointer dereference, was found in the key management facility. A local, unprivileged user could use this flaw to cause a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-1792 to this issue.
A NULL pointer dereference in the XFRM implementation could allow a local user who has the CAP_NET_ADMIN capability to cause a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-1826 to this issue.
A NULL pointer dereference in the Datagram Congestion Control Protocol (DCCP) implementation could allow a local user to cause a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-1827 to this issue.
Information leak flaws in the XFRM implementation could allow a local user who has the CAP_NET_ADMIN capability to leak kernel stack memory to user-space. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-6537 to this issue.
Two information leak flaws in the Asynchronous Transfer Mode (ATM) subsystem could allow a local, unprivileged user to leak kernel stack memory to user-space. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-6546 to this issue.
An information leak was found in the TUN/TAP device driver in the networking implementation. A local user with access to a TUN/TAP virtual interface could use this flaw to leak kernel stack memory to user-space. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-6547 to this issue.
An information leak in the Bluetooth implementation could allow a local user who has the CAP_NET_ADMIN capability to leak kernel stack memory to user-space. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-0349 to this issue.
A use-after-free flaw was found in the tmpfs implementation. A local user able to mount and unmount a tmpfs file system could use this flaw to cause a denial of service or, potentially, escalate their privileges. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-1767 to this issue.
A NULL pointer dereference was found in the Linux kernel's USB Inside Out Edgeport Serial Driver implementation. An attacker with physical access to a system could use this flaw to cause a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-1774 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 IP Office Server Edition | 8.1, 9.0 thru 9.0 SP2 | Medium | Upgrade to 9.0 SP3 or later. |
| Avaya Aura® Experience Portal | 6.x | Medium | Upgrade to EP 7.0, Avaya Linux 7.0 and install Security Updates for 7.0 or later. |
| Avaya Aura® Session Manager | 6.0 thru 6.3.3 | Low | Upgrade to 6.3.4 or later. |
| Avaya CMS | R17.0 through R17.3 | Medium | Upgrade to R17.4 or later. |
| Avaya one-X® Client Enablement Services | 6.1 thru 6.2 | Medium | Upgrade to 6.2 SP1 or later. |
Recommended Actions for System Products:
Avaya strongly recommends following the
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-2012-6546 CVE-2012-6547 |
The risk is rated None for all products because ATM and TUN/TAP are not used by default. |
|
CVE-2013-1826 CVE-2012-6537 CVE-2013-0349 |
The risk is rated None for all products because XFRM or Bluetooth is not used by default. |
|
CVE-2013-1792 |
The risk is rated Medium for all products except Session Manager due to the potential for a local unprivileged user to cause a Denial of Service. The risk is rated Low for Session Manager because only administrators have local user access to the server and no additional capabilities would be gained by this exploit. |
|
CVE-2013-1767 |
The risk is rated Low for all products because mounting or unmounting filesystem would require administrative privileges and no additional capabilities would be gained by this exploit. |
|
CVE-2013-0913 |
The risk is rated Low for all products because the affected driver is not loaded or used by default. |
|
CVE-2013-1773 |
The risk is rated None for all products because FAT filesystem is not used by default. |
|
CVE-2013-1774 |
The risk is rated None for all products because USB is not used by default. |
|
CVE-2013-1796 CVE-2013-1797 CVE-2013-1798 |
The risk is rated None for all products because KVM based virtualization is not used by default. |
|
CVE-2013-1827 |
The risk is rated None for all products because Datagram Congestion Control Protocol is not used by default. |
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 4.x/5.x | 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. |
| Avaya Aura® System Manager 1.0 | Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the SMGR application. |
| Avaya Voice Portal | Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the VP application. |
Recommended Actions for Software-Only Products:
In the event that the affected package is installed, Avaya recommends following the 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 13, 2013 - Initial Statement issued.
V 2.0 - June 8, 2015 - Update affected versions and actions for CMS, IP Office, SM and One-X CES and actions for EP, and set advisory status to Final.
Send information regarding any discovered security problems with Avaya products to either the contact noted in the product's documentation or [email protected].
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
© 2013 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.