Bug 1441970 – CVE-2017-7702 CVE-2017-11410 wireshark: WBXML dissector infinite loop (wnpa-sec-2017-13)

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1441970 - (CVE-2017-11410, CVE-2017-7702) CVE-2017-7702 CVE-2017-11410 wireshark: WBXML dissector infinite loop (wnpa-sec-2017-13)

Summary:	CVE-2017-7702 CVE-2017-11410 wireshark: WBXML dissector infinite loop (wnpa-s...

Status:	NEW

Aliases:	CVE-2017-11410, CVE-2017-7702

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	impact=moderate,public=20170412,repor...
Keywords:	Security

Depends On:	1441981
Blocks:
	Show dependency tree / graph

Reported:	2017-04-13 04:44 EDT by Adam Mariš
Modified:	2018-06-21 05:18 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:	wireshark 2.2.6, wireshark 2.0.12
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Adam Mariš 2017-04-13 04:44:54 EDT

It was reported that Wireshark's WBXML dissector could loop infinitely. It may be possible to make Wireshark crash by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file.

Upstream bug(s):

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13477

External References:

https://www.wireshark.org/security/wnpa-sec-2017-13.html

Comment 1 Adam Mariš 2017-04-13 04:49:00 EDT

Created wireshark tracking bugs for this issue:

Affects: fedora-all [bug 1441981]

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