Bug 1150080 - CVE-2014-6430 et.al. applies to F21 version of wireshark too
Summary: CVE-2014-6430 et.al. applies to F21 version of wireshark too
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: wireshark
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Hatina
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-07 12:05 UTC by Göran Uddeborg
Modified: 2016-06-01 01:33 UTC (History)
5 users (show)

Fixed In Version: wireshark-1.12.1-1.fc21
Clone Of:
Environment:
Last Closed: 2014-10-12 05:02:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Göran Uddeborg 2014-10-07 12:05:26 UTC
Recently, an update to wireshark for F20 was released; bug 1142613.  Unless I misunderstand the CVE, wireshark in F21, 1.12.0 is also vulnerable.  Doesn't that too need to be updated?

Comment 1 Peter Hatina 2014-10-07 13:02:26 UTC
Yes. An update for wireshark-1.12.1-1.fc21 has been pushed to testing.

https://admin.fedoraproject.org/updates/wireshark-1.12.1-1.fc21

Comment 2 Fedora Update System 2014-10-07 13:04:48 UTC
wireshark-1.12.1-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/wireshark-1.12.1-1.fc21

Comment 3 Fedora Update System 2014-10-08 19:04:13 UTC
Package wireshark-1.12.1-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing wireshark-1.12.1-1.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-12362/wireshark-1.12.1-1.fc21
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2014-10-12 05:02:49 UTC
wireshark-1.12.1-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.