The remote Scientific Linux host is missing one or more security
Two 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.
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. (CVE-2012-2392,
CVE-2012-3825, CVE-2012-4285, CVE-2012-4288, CVE-2012-4289,
CVE-2012-4290, CVE-2012-4291, CVE-2012-4292, CVE-2012-5595,
CVE-2012-5597, CVE-2012-5598, CVE-2012-5599, CVE-2012-5600,
CVE-2012-6056, CVE-2012-6059, CVE-2012-6060, CVE-2012-6061,
CVE-2012-6062, CVE-2013-3557, CVE-2013-3561, CVE-2013-4081,
CVE-2013-4927, CVE-2013-4931, CVE-2013-4932, CVE-2013-4933,
CVE-2013-4934, CVE-2013-4935, CVE-2013-4936, CVE-2013-5721)
The wireshark packages have been upgraded to upstream version 1.8.10,
which provides a number of bug fixes and enhancements over the
previous versions. For more information on the bugs fixed,
enhancements included, and supported protocols introduced, refer to
the Wireshark Release Notes.
This update also fixes the following bugs :
- Previously, Wireshark did not parse the RECLAIM-COMPLETE
opcode when inspecting traffic generated by NFSv4.1. A
patch has been provided to enable the parsing of the
RECLAIM_COMPLETE opcode, and Wireshark is now able to
properly dissect and handle NFSv4.1 traffic.
- Prior to this update, frame arrival times in a text file
were reported one hour ahead from the timestamps in the
packet capture file. This resulted in various failures
being reported by the dfilter-test.py test suite. To fix
this bug, frame arrival timestamps have been shifted by
one hour, thus fixing this bug.
- The 'tshark -D' command returned output to STDERR
instead of STDOUT, which could break scripts that are
parsing the 'tshark -D' output. This bug has been fixed,
and the 'tshark -D' command now writes output data to a
correct standard stream.
- Due to an array overrun, Wireshark could experience
undefined program behavior or could unexpectedly
terminate. With this update, proper array handling
ensures Wireshark no longer crashes in the described
- Previously, the dftest and randpkt command line
utilities lacked manual pages. This update adds proper
manual pages for both utilities.
In addition, this update adds the following enhancements :
- With this update, Wireshark is able to properly dissect
and handle InfiniBand and GlusterFS traffic.
All running instances of Wireshark must be restarted for the update to
See also :
Update the affected packages.
Risk factor :
High / CVSS Base Score : 7.8