Python is an interpreted, interactive, object-oriented programming language.
It was found that many applications embedding the Python interpreter did not specify a valid full path to the script or application when calling the PySys_SetArgv API function, which could result in the addition of the current working directory to the module search path (sys.path). A local attacker able to trick a victim into running such an application in an attacker-controlled directory could use this flaw to execute code with the victim's privileges. This update adds the PySys_SetArgvEx API. Developers can modify their applications to use this new API, which sets sys.argv without modifying sys.path. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2008-5983 to this issue.
Multiple flaws were found in the Python rgbimg module. If an application written in Python was using the rgbimg module and loaded a specially-crafted SGI image file, it could cause the application to crash or, possibly, execute arbitrary code with the privileges of the user running the application. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2009-4134, CVE-2010-1449 and CVE-2010-1450 to these issues.
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.
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.2.x, 6.1||Low||Upgrade to Application Enablement Services 6.1.1 or later.|
|Avaya Aura® Application Server 5300:
||2.0||Low||Install Application Server 5300 Release 2.0 mcp_core_linux_ple2-13.0.24.patches.r1 or later.|
|Avaya Aura® Communication Manager||6.0.x||Low||Upgrade to Communication Manager 6.2 or later.|
|Avaya Communication Server 1000:
||6.0, 7.x||Low||See recommended actions and mitigating factors table below. This advisory will not be addressed as no further releases are planned.|
|Avaya Aura® Conferencing Standard Edition||6.0.x||Low||See recommended actions and mitigating factors table below. This advisory will not be addressed as no further releases are planned. It is recommended that customers migrate to one of Avaya's conferencing solutions including Avaya Aura® Conferencing 7.0 or later.|
|Avaya IP Office Application Server||6.1, 7.0||Low||Upgrade to IP Office Application Server 8.0 or later.|
|Avaya IQ||5.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 Aura® Presence Services||6.0, 6.1, 6.1.1||Low||Upgrade to Presence Services 6.1.2 or later.|
|Avaya Aura® Session Manager||5.2.x, 6.0.x, 6.1.x||Low||Upgrade to Session Manager 6.2 or later.|
|Avaya Aura® System Manager||5.2, 6.0.x, 6.1, 6.1.1, 6.1.2, 6.1.3||Low||Upgrade to System Manager 6.1.4 or later.|
|Avaya Aura® System Platform||1.1 6.0.x||Low||Upgrade to System Platform 6.2 or later.|
|Avaya Voice Portal||5.0, 5.1, 5.1.1||Low||Upgrade to VP 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 as the affected functions are not used by default.|
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 - February 24, 2011 - Initial Statement issued.
V 2.0 - June 24, 2011 - Changed AES and AS 5300 actions and IP Office application Server affected versions.
V 3.0 - December 13, 2011 - Changed SMGR and VP affected versions and actions.
V 4.0 - March 7, 2012 - Changed IP Office Application Server actions and PS affected versions and actions.
V 5.0 - March 28, 2012 - Changed CM and SM affected versions and actions.
V 6.0 - April 6, 2012 - Changed SP affected versions and actions.
V 7.0 - June 4, 2013 - Changed CS1000 affected versions and actions.
V 8.0 - June 27, 2013 - Changed CSE 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.