Wireshark is a network protocol analyzer. It is used to capture and browse the traffic running on a computer network.
Multiple flaws were found in Wireshark. If Wireshark read a malformed packet off a network or opened a malicious dump file, it could crash or, possibly, execute arbitrary code as the user running Wireshark. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2013-3559, CVE-2013-4083, CVE-2014-2281 and CVE-2014-2299 to these issues.
Several denial of service flaws were found in Wireshark. Wireshark could crash or stop responding if it read a malformed packet off a network, or opened a malicious dump file. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2012-5595, CVE-2012-5598, CVE-2012-5599, CVE-2012-5600, CVE-2012-6056, CVE-2012-6060, CVE-2012-6061, CVE-2012-6062, CVE-2013-3557, CVE-2013-4081, CVE-2013-4927, CVE-2013-4931, CVE-2013-4932, CVE-2013-4933, CVE-2013-4934, CVE-2013-4935, CVE-2013-5721 and CVE-2013-7112 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.x, 6.1.x||Low||Upgrade to 6.2 or later.|
|Avaya Aura® Communication Manager||6.x||Low||For 6.3, install Security Service Pack 3 or later.
For 6.2 and earlier, upgrade to 6.3 and install Security Service Pack 3 or later.
|Avaya Communication Server 1000:
||7.x||Low||See recommended actions and Mitigating Factors table below. This advisory will not be addressed as no further releases are planned.|
|Avaya IP Office Application Server||8.x||Low||Upgrade to 9.1.4 or later.|
|Avaya Aura® Messaging||6.0 thru 6.3||Low||Upgrade to 6.3.1 or later.|
|Avaya one-X® Client Enablement Services||6.1 SP3||Low||Upgrade to 6.2 or later.|
|Avaya Proactive Contact||5.0 thru 5.1.1||Low||Upgrade to 5.1.2 or later.|
|Avaya Aura® Session Manager||5.2.x thru 6.2.x||Low||Upgrade to 6.3.8 or later.|
|Avaya Aura® System Manager||6.0 thru 6.3 SP7||Low||Upgrade to 6.3 SP8 or later.|
|Avaya Aura® System Platform||1.x, 6.0 thru 6.0 SP4||Low||Upgrade to 6.3 SP5 or later.|
Recommended Actions for System Products:
Avaya strongly recommends following 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 the System Product operating system or application should not be modified 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 for all products because only administrative users have privileges to run wireshark and it is used only for debugging. Opening dump files from unknown systems would constitute non-standard user interaction|
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||Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the AES application.|
|CVLAN||Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the CVLAN application.|
|Avaya Aura® Experience Portal||Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the EP application.|
|Avaya Integrated Management Suite (IMS)||Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the IMS application.|
|Avaya Aura® Presence Services||Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the PS application.|
|Avaya Secure Access Link Gateway||Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the SAL Gateway application.|
Recommended Actions for Software-Only Products:
In the event that the affected package is installed, Avaya recommends following 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 - April 25, 2014 - Initial Statement issued.
V 2.0 - September 4, 2014 - Updated AES, CES and SM actions.
V 3.0 - February 23, 2015 - Updated CM, Messaging, SMGR and SP affected versions and actions.
V 4.0 - October 14, 2015 - Updated IPOAS actions.
V 5.0 - June 8, 2016 - Updated PC affected versions and actions, and set advisory status to Final.
Avaya customers or Business Partners should report any security issues found with Avaya products via the standard support process.
Independent security researchers can contact Avaya at email@example.com.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
© 2014 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.