Debian Package Tracker

general

source: wireshark (main)
version: 3.4.2-1
maintainer: Balint Reczey (DMD)
arch: all any
std-ver: 3.9.8
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 1.12.1+g01b65bf-4+deb8u14
o-o-sec: 1.12.1+g01b65bf-4+deb8u19
oldstable: 2.6.7-1~deb9u1
old-sec: 2.6.8-1.1~deb9u1
stable: 2.6.8-1.1
testing: 3.4.2-1
unstable: 3.4.2-1

versioned links

1.12.1+g01b65bf-4+deb8u14: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.12.1+g01b65bf-4+deb8u19: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.2.6+g32dac6a-2+deb9u3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.6.7-1~deb9u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.6.8-1.1~deb9u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.6.8-1.1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.4.2-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

libwireshark-data
libwireshark-dev
libwireshark14
libwiretap-dev
libwiretap11
libwsutil-dev
libwsutil12
tshark (8 bugs: 0, 3, 5, 0)
wireshark (27 bugs: 0, 9, 18, 0)
wireshark-common (2 bugs: 0, 2, 0, 0)
wireshark-dev (1 bugs: 0, 1, 0, 0)
wireshark-doc
wireshark-gtk
wireshark-qt (1 bugs: 0, 1, 0, 0)

action needed

Standards version of the package is outdated. high

The package is severely out of date with respect to the Debian Policy. The package should be updated to follow the last version of Debian Policy (Standards-Version 4.5.1 instead of 3.9.8).

Created: 2017-06-27 Last update: 2020-12-26 23:38

lintian reports 13 warnings high

Lintian reports 13 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2020-07-29 Last update: 2020-08-22 06:06

Multiarch hinter reports 4 issue(s) normal

There are issues with the multiarch metadata for this package.

libwiretap-dev could be marked Multi-Arch: same
libwsutil-dev could be marked Multi-Arch: same
wireshark could be marked Multi-Arch: same
wireshark-gtk could be marked Multi-Arch: same

Created: 2020-12-23 Last update: 2021-01-18 15:32

Depends on packages which need a new maintainer normal

The packages that wireshark depends on which need a new maintainer are:

docbook-xml (#802368)
- Build-Depends: docbook-xml
docbook-xsl (#802370)
- Build-Depends: docbook-xsl
omniorb-dfsg (#955300)
- Depends: omniidl

Created: 2019-11-22 Last update: 2021-01-18 15:03

AppStream hints: 1 warning normal

AppStream found metadata issues for packages:

wireshark-qt: 1 warning

You should get rid of them to provide more metadata about this software.

Created: 2020-06-01 Last update: 2020-06-01 01:13

16 ignored security issues in stretch low

There are 16 open security issues in stretch.

16 issues skipped by the security teams:

CVE-2019-13619: In Wireshark 3.0.0 to 3.0.2, 2.6.0 to 2.6.9, and 2.4.0 to 2.4.15, the ASN.1 BER dissector and related dissectors could crash. This was addressed in epan/asn1.c by properly restricting buffer increments.
CVE-2019-16319: In Wireshark 3.0.0 to 3.0.3 and 2.6.0 to 2.6.10, the Gryphon dissector could go into an infinite loop. This was addressed in plugins/epan/gryphon/packet-gryphon.c by checking for a message length of zero.
CVE-2019-19553: In Wireshark 3.0.0 to 3.0.6 and 2.6.0 to 2.6.12, the CMS dissector could crash. This was addressed in epan/dissectors/asn1/cms/packet-cms-template.c by ensuring that an object identifier is set to NULL after a ContentInfo dissection.
CVE-2020-11647: In Wireshark 3.2.0 to 3.2.2, 3.0.0 to 3.0.9, and 2.6.0 to 2.6.15, the BACapp dissector could crash. This was addressed in epan/dissectors/packet-bacapp.c by limiting the amount of recursion.
CVE-2020-13164: In Wireshark 3.2.0 to 3.2.3, 3.0.0 to 3.0.10, and 2.6.0 to 2.6.16, the NFS dissector could crash. This was addressed in epan/dissectors/packet-nfs.c by preventing excessive recursion, such as for a cycle in the directory graph on a filesystem.
CVE-2020-15466: In Wireshark 3.2.0 to 3.2.4, the GVCP dissector could go into an infinite loop. This was addressed in epan/dissectors/packet-gvcp.c by ensuring that an offset increases in all situations.
CVE-2020-25862: In Wireshark 3.2.0 to 3.2.6, 3.0.0 to 3.0.13, and 2.6.0 to 2.6.20, the TCP dissector could crash. This was addressed in epan/dissectors/packet-tcp.c by changing the handling of the invalid 0xFFFF checksum.
CVE-2020-25863: In Wireshark 3.2.0 to 3.2.6, 3.0.0 to 3.0.13, and 2.6.0 to 2.6.20, the MIME Multipart dissector could crash. This was addressed in epan/dissectors/packet-multipart.c by correcting the deallocation of invalid MIME parts.
CVE-2020-26418: Memory leak in Kafka protocol dissector in Wireshark 3.4.0 and 3.2.0 to 3.2.8 allows denial of service via packet injection or crafted capture file.
CVE-2020-26421: Crash in USB HID protocol dissector and possibly other dissectors in Wireshark 3.4.0 and 3.2.0 to 3.2.8 allows denial of service via packet injection or crafted capture file.
CVE-2020-26575: In Wireshark through 3.2.7, the Facebook Zero Protocol (aka FBZERO) dissector could enter an infinite loop. This was addressed in epan/dissectors/packet-fbzero.c by correcting the implementation of offset advancement.
CVE-2020-28030: In Wireshark 3.2.0 to 3.2.7, the GQUIC dissector could crash. This was addressed in epan/dissectors/packet-gquic.c by correcting the implementation of offset advancement.
CVE-2020-7045: In Wireshark 3.0.x before 3.0.8, the BT ATT dissector could crash. This was addressed in epan/dissectors/packet-btatt.c by validating opcodes.
CVE-2020-9428: In Wireshark 3.2.0 to 3.2.1, 3.0.0 to 3.0.8, and 2.6.0 to 2.6.14, the EAP dissector could crash. This was addressed in epan/dissectors/packet-eap.c by using more careful sscanf parsing.
CVE-2020-9430: In Wireshark 3.2.0 to 3.2.1, 3.0.0 to 3.0.8, and 2.6.0 to 2.6.14, the WiMax DLMAP dissector could crash. This was addressed in plugins/epan/wimax/msg_dlmap.c by validating a length field.
CVE-2020-9431: In Wireshark 3.2.0 to 3.2.1, 3.0.0 to 3.0.8, and 2.6.0 to 2.6.14, the LTE RRC dissector could leak memory. This was addressed in epan/dissectors/packet-lte-rrc.c by adjusting certain append operations.

Please fix them.

Created: 2019-04-09 Last update: 2021-01-06 08:05

16 ignored security issues in buster low

There are 16 open security issues in buster.

16 issues skipped by the security teams:

CVE-2019-13619: In Wireshark 3.0.0 to 3.0.2, 2.6.0 to 2.6.9, and 2.4.0 to 2.4.15, the ASN.1 BER dissector and related dissectors could crash. This was addressed in epan/asn1.c by properly restricting buffer increments.
CVE-2019-16319: In Wireshark 3.0.0 to 3.0.3 and 2.6.0 to 2.6.10, the Gryphon dissector could go into an infinite loop. This was addressed in plugins/epan/gryphon/packet-gryphon.c by checking for a message length of zero.
CVE-2019-19553: In Wireshark 3.0.0 to 3.0.6 and 2.6.0 to 2.6.12, the CMS dissector could crash. This was addressed in epan/dissectors/asn1/cms/packet-cms-template.c by ensuring that an object identifier is set to NULL after a ContentInfo dissection.
CVE-2020-11647: In Wireshark 3.2.0 to 3.2.2, 3.0.0 to 3.0.9, and 2.6.0 to 2.6.15, the BACapp dissector could crash. This was addressed in epan/dissectors/packet-bacapp.c by limiting the amount of recursion.
CVE-2020-13164: In Wireshark 3.2.0 to 3.2.3, 3.0.0 to 3.0.10, and 2.6.0 to 2.6.16, the NFS dissector could crash. This was addressed in epan/dissectors/packet-nfs.c by preventing excessive recursion, such as for a cycle in the directory graph on a filesystem.
CVE-2020-15466: In Wireshark 3.2.0 to 3.2.4, the GVCP dissector could go into an infinite loop. This was addressed in epan/dissectors/packet-gvcp.c by ensuring that an offset increases in all situations.
CVE-2020-25862: In Wireshark 3.2.0 to 3.2.6, 3.0.0 to 3.0.13, and 2.6.0 to 2.6.20, the TCP dissector could crash. This was addressed in epan/dissectors/packet-tcp.c by changing the handling of the invalid 0xFFFF checksum.
CVE-2020-25863: In Wireshark 3.2.0 to 3.2.6, 3.0.0 to 3.0.13, and 2.6.0 to 2.6.20, the MIME Multipart dissector could crash. This was addressed in epan/dissectors/packet-multipart.c by correcting the deallocation of invalid MIME parts.
CVE-2020-26418: Memory leak in Kafka protocol dissector in Wireshark 3.4.0 and 3.2.0 to 3.2.8 allows denial of service via packet injection or crafted capture file.
CVE-2020-26421: Crash in USB HID protocol dissector and possibly other dissectors in Wireshark 3.4.0 and 3.2.0 to 3.2.8 allows denial of service via packet injection or crafted capture file.
CVE-2020-26575: In Wireshark through 3.2.7, the Facebook Zero Protocol (aka FBZERO) dissector could enter an infinite loop. This was addressed in epan/dissectors/packet-fbzero.c by correcting the implementation of offset advancement.
CVE-2020-28030: In Wireshark 3.2.0 to 3.2.7, the GQUIC dissector could crash. This was addressed in epan/dissectors/packet-gquic.c by correcting the implementation of offset advancement.
CVE-2020-7045: In Wireshark 3.0.x before 3.0.8, the BT ATT dissector could crash. This was addressed in epan/dissectors/packet-btatt.c by validating opcodes.
CVE-2020-9428: In Wireshark 3.2.0 to 3.2.1, 3.0.0 to 3.0.8, and 2.6.0 to 2.6.14, the EAP dissector could crash. This was addressed in epan/dissectors/packet-eap.c by using more careful sscanf parsing.
CVE-2020-9430: In Wireshark 3.2.0 to 3.2.1, 3.0.0 to 3.0.8, and 2.6.0 to 2.6.14, the WiMax DLMAP dissector could crash. This was addressed in plugins/epan/wimax/msg_dlmap.c by validating a length field.
CVE-2020-9431: In Wireshark 3.2.0 to 3.2.1, 3.0.0 to 3.0.8, and 2.6.0 to 2.6.14, the LTE RRC dissector could leak memory. This was addressed in epan/dissectors/packet-lte-rrc.c by adjusting certain append operations.

Please fix them.

Created: 2019-07-18 Last update: 2021-01-06 08:05

Build log checks report 2 warnings low

Build log checks report 2 warnings

Created: 2018-06-28 Last update: 2020-08-14 10:34

Issues found with some translations low

Automatic checks made by the Debian l10n team found some issues with the translations contained in this package. You should check the l10n status report for more information.

Issues can be things such as missing translations, problematic translated strings, outdated PO files, unknown languages, etc.

Created: 2020-02-26 Last update: 2020-02-26 10:50

news

[rss feed]

[2021-01-06] wireshark 3.4.2-1 MIGRATED to testing (Debian testing watch)
[2020-12-26] Accepted wireshark 3.4.2-1 (source) into unstable (Balint Reczey)
[2020-12-13] Accepted wireshark 3.4.1-1 (source) into unstable (Balint Reczey)
[2020-12-09] wireshark 3.4.0-1 MIGRATED to testing (Debian testing watch)
[2020-12-06] Accepted wireshark 3.4.0-1 (source) into unstable (Balint Reczey)
[2020-12-06] Accepted wireshark 3.4.0-0exp1 (source all amd64) into experimental, experimental (Debian FTP Masters) (signed by: Balint Reczey)
[2020-11-27] wireshark 3.2.8-0.1 MIGRATED to testing (Debian testing watch)
[2020-11-27] wireshark 3.2.8-0.1 MIGRATED to testing (Debian testing watch)
[2020-11-24] Accepted wireshark 3.2.8-0.1 (source) into unstable (Adrian Bunk)
[2020-10-31] Accepted wireshark 2.6.8-1.1~deb9u1 (source) into oldstable (Adrian Bunk)
[2020-09-27] wireshark 3.2.7-1 MIGRATED to testing (Debian testing watch)
[2020-09-24] Accepted wireshark 3.2.7-1 (source) into unstable (Balint Reczey)
[2020-08-16] wireshark 3.2.6-1 MIGRATED to testing (Debian testing watch)
[2020-08-13] Accepted wireshark 3.2.6-1 (source) into unstable (Balint Reczey)
[2020-07-08] wireshark 3.2.5-1 MIGRATED to testing (Debian testing watch)
[2020-07-05] Accepted wireshark 3.2.5-1 (source) into unstable (Balint Reczey)
[2020-05-22] wireshark 3.2.4-1 MIGRATED to testing (Debian testing watch)
[2020-05-20] Accepted wireshark 3.2.4-1 (source) into unstable (Balint Reczey)
[2020-04-23] wireshark 3.2.3-1 MIGRATED to testing (Debian testing watch)
[2020-04-19] Accepted wireshark 3.2.3-1 (source) into unstable (Balint Reczey)
[2020-02-29] wireshark 3.2.2-1 MIGRATED to testing (Debian testing watch)
[2020-02-27] Accepted wireshark 3.2.2-1 (source) into unstable (Balint Reczey)
[2020-01-21] wireshark 3.2.1-1 MIGRATED to testing (Debian testing watch)
[2020-01-19] Accepted wireshark 3.2.1-1 (source) into unstable (Balint Reczey)
[2019-12-24] Accepted wireshark 3.2.0-1 (source) into unstable (Balint Reczey)
[2019-12-23] Accepted wireshark 3.2.0-1~exp0 (source all amd64) into experimental, experimental (Balint Reczey)
[2019-12-10] wireshark 3.0.7-1 MIGRATED to testing (Debian testing watch)
[2019-12-07] Accepted wireshark 3.0.7-1 (source) into unstable (Balint Reczey)
[2019-09-29] wireshark 3.0.5-1 MIGRATED to testing (Debian testing watch)
[2019-09-27] Accepted wireshark 3.0.5-1 (source) into unstable (Balint Reczey)

bugs [bug history graph]

all: 40
RC: 0
I&N: 16
M&W: 24
F&P: 0
patch: 0

links

homepage
lintian (0, 13)
buildd: logs, checks, clang, reproducibility, cross
popcon
browse source code
edit tags
other distros
security tracker
screenshots
l10n (41, -)
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 3.4.2-1
22 bugs