PostgreSQL is an advanced object-relational database management system (DBMS).
Multiple stack-based buffer overflow flaws were found in the date/time implementation of PostgreSQL. An authenticated database user could provide a specially crafted date/time value that, when processed, could cause PostgreSQL to crash or, potentially, execute arbitrary code with the permissions of the user running PostgreSQL. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-0063 to this issue.
Multiple integer overflow flaws, leading to heap-based buffer overflows, were found in various type input functions in PostgreSQL. An authenticated database user could possibly use these flaws to crash PostgreSQL or, potentially, execute arbitrary code with the permissions of the user running PostgreSQL. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-0064 to this issue.
Multiple potential buffer overflow flaws were found in PostgreSQL. An authenticated database user could possibly use these flaws to crash PostgreSQL or, potentially, execute arbitrary code with the permissions of the user running PostgreSQL. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-0065 to this issue.
It was found that granting an SQL role to a database user in a PostgreSQL database without specifying the "ADMIN" option allowed the grantee to remove other users from their granted role. An authenticated database user could use this flaw to remove a user from an SQL role which they were granted access to. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-0060 to this issue.
A flaw was found in the validator functions provided by PostgreSQL's procedural languages (PLs). An authenticated database user could possibly use this flaw to escalate their privileges. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-0061 to this issue.
A race condition was found in the way the CREATE INDEX command performed multiple independent lookups of a table that had to be indexed. An authenticated database user could possibly use this flaw to escalate their privileges. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-0062 to this issue.
It was found that the chkpass extension of PostgreSQL did not check the return value of the crypt() function. An authenticated database user could possibly use this flaw to crash PostgreSQL via a null pointer dereference. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-0066 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, 6.0.x through 6.3.2 | Low | Upgrade to 6.3.3 or later. |
Avaya Aura® Communication Manager | 5.x, 6.x | None | See Mitigating Factors table below. |
Avaya Aura® Conferencing | 7.0.x through 7.2 SP5 | Low | For 7.0.x, upgrade to 7.2 and install SP6 or later. For 7.2.x, install SP6 or later. |
Avaya Aura® Conferencing Standard Edition | 6.0 | Low | Upgrade to 6.0 SP1 or later. |
Avaya IP Office Application Server | 8.1 | Medium | Upgrade to 9.0 or later. |
Avaya Aura® Messaging | 6.3 through 6.3.2 SP1 | None | See Mitigating Factors table below. Upgrade to 6.3.2 SP2 or later. |
Avaya Aura® Utility Services | 6.2.x, 6.3.x specifically prior to 6.3 SP7 | Medium | For versions earlier than 6.3, upgrade to 6.3 and install SP7 or later. For 6.3.x, install 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-0060 CVE-2014-0061 CVE-2014-0062 CVE-2014-0063 CVE-2014-0064 CVE-2014-0065 CVE-2014-0066 |
The risk is rated None for CM, Messaging because only postgresql-libs is installed. The risk is rated Low for AES, Conferencing and Conferencing Standard Edition because local users cannot access database. The risk is rated Medium for IP Office Application Server and Utility Services because of the potential to crash the application, execute arbitrary code or to escalate privileges. |
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 - May 1, 2014 - Initial Statement issued.
V 2.0 - April 20, 2015 - Updated affected versions and actions for AES, Conferencing, Conferencing SE, Messaging and US.
V 3.0 - May 31, 2017 - Updated affected versions and actions for IP Office, 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.