PostgreSQL is an advanced Object-Relational database management system (DBMS). The PostgreSQL Global Development Group has released security updates for all active branches of the PostgreSQL database system, including versions 9.1.4, 9.0.8, 8.4.12 and 8.3.19.
This update includes security fixes for the following issues:
* A security flaw was found in the way the DES and extended DES based crypt() password encryption functions performed encryption of certain keys, when the key to be encrypted was provided in the Unicode encoding (certain keys were truncated before being DES digested). When the resulting ciphertext for such a previously shortened key was used as a pattern in a password protected resource, intended to be matched against subsequently encrypted value of the password field, retrieved from the user authentication dialog, it could lead to authentication bypass. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-2143 to this issue.
* A security flaw was found in the way PostgreSQL performed inclusion of additional procedural language plug-ins support into PostgreSQL server. Previously, database administrators were allowed to install trusted procedural languages into their databases and the owner of such procedural language function were allowed to execute ALTER FUNCTION statement. If a procedural language plug-in was enabled on the particular database, an authenticated database administrator could use this flaw to cause denial of service (PostgreSQL server crash) by adding SECURITY DEFINER or SET attributes to such a handler function. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-2655 to this issue.
The information about these vulnerabilities may be found in the release notes issued by PostgreSQL:
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.2 thru 6.2 | Low | For 6.1 and earlier upgrade to 6.2 and install Linux Security Update Patch 1 as described in PSN003992u or upgrade to 6.3 or later. For 6.2 install Linux Security Update Patch 1 as described in PSN003992u or upgrade to 6.3 or later. |
Avaya Aura® Experience Portal | 6.0 including 6.0 SP1 | Low | Upgrade to Avaya Enterprise Linux for Experience Portal 6.0 SP2 and Experience Portal 6.0 SP2 or later. |
Avaya Meeting Exchange | 5.x | Low | Upgrade to 6.2 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.1, 5.x, 6.0.x, 6.1.x, 6.2.x | Low | Upgrade to 6.3 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.0.x 5.1 thru 5.1 SP2 | Low | Upgrade to Avaya Enterprise Linux for Voice Portal 5.1 SP3 and Voice Portal 5.1 SP3 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-2012-2143 | There is no Risk for Presence Services, Session Manager and Voice
Portal
since the crypt encryption function is not used. This is a Low Risk for Application Enablement Services, Experience Portal, Meeting Exchange and System Manager because access is restricted to local system administrators only. |
CVE-2012-2655 | This is a Low Risk for all products because only local adminstrators could perform this attack, and doing so would not give them any additional privileges than they already have. |
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 - July 6, 2012 - Initial Statement issued.
V 2.0 - March 22, 2013 - Updated MX actions, and EP, SM and VP affected versions and actions.
V 3.0 - August 1, 2013 - Updated AES affected versions and actions.
V 4.0 - February 04, 2015 - Updated SMGR affected versions and actions.
V 5.0 - September 9, 2015 - Updated PS actions and set advisory 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.
© 2012 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.