PostgreSQL is an advanced Object-Relational database management system (DBMS). The PostgreSQL Global Development Group has released a security update to all current versions of the PostgreSQL database system, including versions 9.2.3, 9.1.8, 9.0.12, 8.4.16, and 8.3.23.
A flaw was found in PostgreSQL where it does not properly declare the enum_recv function in backend/utils/adt/enum.c, which causes it to be invoked with incorrect arguments and allows remote authenticated users to cause a denial of service (server crash) or read sensitive process memory via a crafted SQL command, which triggers an array index error and an out-of-bounds read. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-0255 to this issue.
The information about these vulnerabilities may be found in the release notes issued by PostgreSQL.org:
Note: This advisory targets only Avaya products with postgresql packages provided by postgresql.org. Products with postgresql packages provided by Red Hat will be covered by advisories associated with Red Hat Security Advisories (RHSA).
| Product: | Affected Version(s): | Risk Level: | Actions: |
|---|---|---|---|
| Avaya Aura® Application Enablement Services | 5.x, 6.x | None | See Mitigating Factors table below. |
| Avaya Aura® Experience Portal | 6.x | Low | Upgrade to 7.0 or later. |
| Avaya Meeting Exchange | 5.x, 6.2 thru 6.2 SP2 | Low | Upgrade to 6.2 SP3 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 Aura® Session Manager | 1.x, 5.x, 6.0 thru 6.3.7 | Low | Upgrade to 6.3.8 or later. |
| Avaya Aura® System Manager | 5.x, 6.1 thru 6.3.7 | Low | Upgrade to 6.3.8 or later. |
| Avaya Voice Portal | 5.x | Low | Upgrade to Experience Portal 7.0 or later. |
Recommended Actions for System Products:
Avaya strongly recommends that customers follow
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 customers should not modify the System Product
operating system or application 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-2013-0255 | There is no risk to Application Enablement Services as the affected package versions are not installed. This is a Low risk to Experience Portal, Meeting Exchange, Presence Services, Session Manager, System Manager and Voice Portal as remote access to the PostgreSQL database is not allowed by default or requires local administrative access to exploit and would not provide additional capabilities. |
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 - March 4, 2013 - Initial Statement issued.
V 2.0 - May 22, 2013 - Updated SMGR risk to Low.
V 3.0 - May 22, 2013 - Updated PS risk to Low and overall risk level to Low.
V 4.0 - January 10, 2014 - Updated EP and VP actions.
V 5.0 - August 1, 2014 - Updated SM and SMGR affected versions and actions.
V 6.0 - September 10, 2015 - Updated PS actions.
V 7.0 - July 25, 2016 - Changed Meeting Exchange affected versions and actions, and 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 securityalerts@avaya.com.
© 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.