Python is an interpreted, interactive, object-oriented programming language.
A flaw was found in the Python urllib and urllib2 libraries where they would not differentiate between different target URLs when handling automatic redirects. This caused Python applications using these modules to follow any new URL that they understood, including the "file://" URL type. This could allow a remote server to force a local Python application to read a local file instead of the remote one, possibly exposing local files that were not meant to be exposed. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1521 to this issue.
Multiple flaws were found in the Python audioop module. Supplying certain inputs could cause the audioop module to crash or, possibly, execute arbitrary code. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2010-1634 and CVE-2010-2089 to these issues.
A race condition was found in the way the Python smtpd module handled new connections. A remote user could use this flaw to cause a Python script using the smtpd module to terminate. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3493 to this issue.
An information disclosure flaw was found in the way the Python CGIHTTPServer module processed certain HTTP GET requests. A remote attacker could use a specially-crafted request to obtain the CGI script's source code. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1015 to this issue.
A buffer over-read flaw was found in the way the Python Expat parser handled malformed UTF-8 sequences when processing XML files. A specially-crafted XML file could cause Python applications using the Python Expat parser to crash while parsing the file. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2009-3720 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 IQ||4.x||Low||See recommended actions below. This issue will be addressed in accordance with section five of Avaya's Product Security Vulnerability Response Policy|
|Avaya Meeting Exchange||5.x||Low||Upgrade to Meeting Exchange 6.2 or later.|
|Avaya Message Networking||3.1, 5.2 through 5.2.3||Low||Upgrade to Message Networking 5.2.4 or later.|
|Avaya Messaging Storage Server||4.x, 5.2 through 5.2.8||Low||Upgrade to Messaging Storage Server 5.2.9 or later.|
|Avaya Proactive Contact||4.0, 4.1.x, 4.2, 4.2.1||Low||Upgrade to Proactive Contact 4.2.2 or later 4.x version.|
|Avaya Voice Portal||4.x||Low||Upgrade to Voice Portal 5.1.2 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:
|These are a Low risk as no critical system applications or processes would be affected.|
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 4.x/5.x||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the AES application.|
|CVLAN||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the CVLAN application.|
|Avaya Integrated Management Suite (IMS)||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the IMS application.|
|Avaya Aura® Presence Services||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the PS application.|
|Avaya Aura® System Manager 1.0||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the SMGR application.|
|Voice Portal||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the Voice Portal application.|
Recommended Actions for Software-Only Products:
In the event that the affected package is installed, Avaya recommends that customers follow 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 - June 13, 2011 - Initial Statement issued.
V 2.0 - April 5, 2012 - Changed MN, MSS, PC and VP affected versions and actions.
V 3.0 - March 25, 2013 - Changed MX actions.
Send information regarding any discovered security problems with Avaya products to either the contact noted in the product's documentation or firstname.lastname@example.org.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
© 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.