CVE-2019-9214
published 2019-02-28CVE-2019-9214: In Wireshark 2.4.0 to 2.4.12 and 2.6.0 to 2.6.6, the RPCAP dissector could crash. This was addressed in epan/dissectors/packet-rpcap.c by avoiding an attempted…
PriorityP337high7.5CVSS 3.0
AVNACLPRNUINSUCNINAH
EPSS
3.74%
88.7th percentile
In Wireshark 2.4.0 to 2.4.12 and 2.6.0 to 2.6.6, the RPCAP dissector could crash. This was addressed in epan/dissectors/packet-rpcap.c by avoiding an attempted dereference of a NULL conversation.
Affected
8 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | wireshark | < wireshark 2.6.7-1 (bookworm) | wireshark 2.6.7-1 (bookworm) |
| wireshark | wireshark | >= 0 < 2.6.7-1 | 2.6.7-1 |
| wireshark | wireshark | >= 0 < 2.6.7-1 | 2.6.7-1 |
| wireshark | wireshark | >= 0 < 2.6.7-1 | 2.6.7-1 |
| wireshark | wireshark | >= 0 < 2.6.7-1 | 2.6.7-1 |
| wireshark | wireshark | 2.4.0 – 2.4.12 | — |
| wireshark | wireshark | 2.6.0 – 2.6.6 | — |
CVSS provenance
nvdv3.07.5HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:N/A:P
osv7.5HIGH
vendor_debian7.5HIGH
vendor_redhat7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-87vf-6frx-g3h2: In Wireshark 2
ghsa_unreviewed·2022-05-14
CVE-2019-9214 [HIGH] CWE-476 GHSA-87vf-6frx-g3h2: In Wireshark 2
In Wireshark 2.4.0 to 2.4.12 and 2.6.0 to 2.6.6, the RPCAP dissector could crash. This was addressed in epan/dissectors/packet-rpcap.c by avoiding an attempted dereference of a NULL conversation.
OSV
CVE-2019-9214: In Wireshark 2
osv·2019-02-28·CVSS 7.5
CVE-2019-9214 [HIGH] CVE-2019-9214: In Wireshark 2
In Wireshark 2.4.0 to 2.4.12 and 2.6.0 to 2.6.6, the RPCAP dissector could crash. This was addressed in epan/dissectors/packet-rpcap.c by avoiding an attempted dereference of a NULL conversation.
Ubuntu
Wireshark vulnerabilities
vendor_ubuntu·2019-05-16
CVE-2019-10894 Wireshark vulnerabilities
Title: Wireshark vulnerabilities
Summary: Wireshark could be made to crash if it received specially crafted network
traffic or input files.
It was discovered that Wireshark improperly handled certain input. A remote or
local attacker could cause Wireshark to crash by injecting malform packets onto
the wire or convincing someone to read a malformed packet trace file.
Instructions: In general, a standard system update will make all the necessary changes.
Red Hat
wireshark: null-deference read in RPCAP dissector
vendor_redhat·2019-02-27·CVSS 7.5
CVE-2019-9214 [HIGH] CWE-476 wireshark: null-deference read in RPCAP dissector
wireshark: null-deference read in RPCAP dissector
In Wireshark 2.4.0 to 2.4.12 and 2.6.0 to 2.6.6, the RPCAP dissector could crash. This was addressed in epan/dissectors/packet-rpcap.c by avoiding an attempted dereference of a NULL conversation.
Statement: This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5, 6, and 7.
Package: wireshark (Red Hat Enterprise Linux 5) - Not affected
Package: wireshark (Red Hat Enterprise Linux 6) - Not affected
Package: wireshark (Red Hat Enterprise Linux 7) - Not affected
Package: wireshark (Red Hat Enterprise Linux 8) - Not affected
Debian
CVE-2019-9214: wireshark - In Wireshark 2.4.0 to 2.4.12 and 2.6.0 to 2.6.6, the RPCAP dissector could crash...
vendor_debian·2019·CVSS 7.5
CVE-2019-9214 [HIGH] CVE-2019-9214: wireshark - In Wireshark 2.4.0 to 2.4.12 and 2.6.0 to 2.6.6, the RPCAP dissector could crash...
In Wireshark 2.4.0 to 2.4.12 and 2.6.0 to 2.6.6, the RPCAP dissector could crash. This was addressed in epan/dissectors/packet-rpcap.c by avoiding an attempted dereference of a NULL conversation.
Scope: local
bookworm: resolved (fixed in 2.6.7-1)
bullseye: resolved (fixed in 2.6.7-1)
forky: resolved (fixed in 2.6.7-1)
sid: resolved (fixed in 2.6.7-1)
trixie: resolved (fixed in 2.6.7-1)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2019-9214 wireshark: null-deference read in RPCAP dissector [fedora-all]
bugzilla·2019-04-04·CVSS 7.5
CVE-2019-9214 [HIGH] CVE-2019-9214 wireshark: null-deference read in RPCAP dissector [fedora-all]
CVE-2019-9214 wireshark: null-deference read in RPCAP dissector [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions
Bugzilla
CVE-2019-9214 wireshark: null-deference read in RPCAP dissector
bugzilla·2019-02-28·CVSS 7.5
CVE-2019-9214 [HIGH] CVE-2019-9214 wireshark: null-deference read in RPCAP dissector
CVE-2019-9214 wireshark: null-deference read in RPCAP dissector
In Wireshark 2.4.0 to 2.4.12 and 2.6.0 to 2.6.6, the RPCAP dissector could crash. This was addressed in epan/dissectors/packet-rpcap.c by avoiding an attempted dereference of a NULL conversation.
Reference:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15536
Upstream Patch:
https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=c557bb0910be271e49563756411a690a1bc53ce5
Discussion:
External References:
https://www.wireshark.org/security/wnpa-sec-2019-08.html
---
Hrm. Seems like this was introduced via https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commitdiff;h=d58a3ffe4f69366f25fd192e41a89b4769c7d22c
That's a fairly recent commit and contradicts the versions upstream claims to be affected.
http://lists.opensuse.org/opensuse-security-announce/2019-04/msg00007.htmlhttp://lists.opensuse.org/opensuse-security-announce/2019-05/msg00027.htmlhttp://lists.opensuse.org/opensuse-security-announce/2020-03/msg00027.htmlhttp://www.securityfocus.com/bid/107203https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15536https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=c557bb0910be271e49563756411a690a1bc53ce5https://seclists.org/bugtraq/2019/Mar/35https://usn.ubuntu.com/3986-1/https://www.debian.org/security/2019/dsa-4416https://www.wireshark.org/security/wnpa-sec-2019-08.htmlhttp://lists.opensuse.org/opensuse-security-announce/2019-04/msg00007.htmlhttp://lists.opensuse.org/opensuse-security-announce/2019-05/msg00027.htmlhttp://lists.opensuse.org/opensuse-security-announce/2020-03/msg00027.htmlhttp://www.securityfocus.com/bid/107203https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15536https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=c557bb0910be271e49563756411a690a1bc53ce5https://seclists.org/bugtraq/2019/Mar/35https://usn.ubuntu.com/3986-1/https://www.debian.org/security/2019/dsa-4416https://www.wireshark.org/security/wnpa-sec-2019-08.html
2019-02-28
Published