PostgreSQL is an advanced object-relational database management system (DBMS).
The PostgreSQL Global Development Group released security updates for all active branches of PostgreSQL. This update includes a security fix which prevents a buffer overrun in the contrib module intarray's input function for the query_int type which could allow the function's return address to be overwritten by malicious code. The affected contrib module is optional and only databases with the intarray module installed are affected. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-4015 to this issue.
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).
The information about this vulnerability can be found in the security notice issued by PostgreSQL:
| Product: | Affected Version(s): | Risk Level: | Actions: |
|---|---|---|---|
| Avaya Meeting Exchange | 5.x | Low | Upgrade to Meeting Exchange 6.2 or later. |
| Avaya Aura® Presence Services | 6.0, 6.1, 6.1.1 | Low | Upgrade to Presence Services 6.1.2 or later. |
| Avaya Aura® Session Manager | 1.1, 5.2.x, 6.0.x, 6.1, 6.1.1, 6.1.2 | Low | Upgrade to Session Manager 6.1.3 or later. |
| Avaya Aura® System Manager | 5.2, 6.0.x, 6.1.x, 6.2.x | Medium | Upgrade to System Manager 6.3 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-2010-4015 |
Avaya Meeting Exchange, Avaya Aura® Presence Services and Avaya Aura® Session Manager are rated as low risk because either the postgresql-contrib package or intarray module is not installed by default. |
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 4, 2011 - Initial Statement issued.
V 2.0 - April 5, 2012 - Changed PS and SM affected versions and actions.
V 3.0 - December 21, 2012 - Changed SMGR affected versions and actions.
V 4.0 - March 21, 2013 - Changed MX 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 [email protected].
© 2011 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.