PHP is an HTML-embedded scripting language commonly used with the Apache HTTP Server. PHP's fileinfo module provides functions used to identify a particular file according to the type of data contained by the file.
It was found that the fix for CVE-2012-1571 was incomplete; the File Information (fileinfo) extension did not correctly parse certain Composite Document Format (CDF) files. A remote attacker could use this flaw to crash a PHP application using fileinfo via a specially crafted CDF file. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-3587 to this issue.
A NULL pointer dereference flaw was found in the gdImageCreateFromXpm() function of PHP's gd extension. A remote attacker could use this flaw to crash a PHP application using gd via a specially crafted X PixMap (XPM) file. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-2497 to this issue.
Multiple buffer over-read flaws were found in the php_parserr() function of PHP. A malicious DNS server or a man-in-the-middle attacker could possibly use this flaw to execute arbitrary code as the PHP interpreter if a PHP application used the dns_get_record() function to perform a DNS query. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-3597 to this issue.
Two use-after-free flaws were found in the way PHP handled certain Standard PHP Library (SPL) Iterators and ArrayIterators. A malicious script author could possibly use either of these flaws to disclose certain portions of server memory. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2014-4670 and CVE-2014-4698 to these issues.
Note: these issues impact php53 packages on RHEL5 and php packages on RHEL6.
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® Conferencing||8.0 including SP1||Low||Upgrade to 8.0 SP2 or later.|
|Avaya Aura® Experience Portal||6.x, 7.x||Low||For 6.0 SP1 and SP2, upgrade to 6.0 SP3 and Avaya Linux for 6.0 SP3, and install
6.0 SP3 Security Updates.
For 6.0 SP3, install 6.0 SP3 Security Updates.
For 7.0, install 7.0 Security Updates.
For 7.0.1, install 7.0.1 Security Updates.
|Avaya IP Office Server Edition||8.1 thru 9.1.3||Low||Upgrade to 9.1.4 or later.|
|Avaya IP Office Application Server||9.0 thru 9.1.3||Low||Upgrade to 9.1.4 or later.|
|Avaya Aura® Session Manager||5.x||Low||Upgrade to 6.0 or later.|
|Avaya Aura® 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:
|These are a Low risk for all listed products because the vulnerable functions are 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.
|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.|
|Avaya IQ||Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the Avaya IQ 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.|
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 - October 31, 2014 - Initial Statement issued.
V 2.0 - February 27, 2015 - Updated AAC, AAEP and AAUS affected versions and actions.
V 3.0 - October 15, 2015 - Updated IPOSE and IPOAS 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 firstname.lastname@example.org.
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.