Skip to content
Fencer Intel
high 7.5

CVE-2018-7332 json

In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, epan/dissectors/packet-reload.c had an infinite loop that was addressed by validating a le…

published 8y ago modified 4mo ago also EUVD-2018-19064

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.3%
EPSS 2.3% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, epan/dissectors/packet-reload.c had an infinite loop that was addressed by validating a length.

Patch / fix

  • wireshark Debian 14, Debian 13, Debian 12 2.4.5-1

debian advisories DEBIAN-CVE-2018-7332

  • wireshark Ubuntu 14.04 LTS 2.6.3-1~ubuntu14.04.1
  • wireshark Ubuntu 16.04 LTS 2.6.3-1~ubuntu16.04.1
  • wireshark Ubuntu 18.04 LTS 2.6.3-1~ubuntu18.04.1

ubuntu advisories UBUNTU-CVE-2018-7332

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • wireshark SLES for SAP 11 SP4, SLES 11 SP4, SLE Software Development Kit 11 SP4 2.2.13-40.22.1
  • wireshark SLES for SAP 12 SP3, SLES for SAP 12 SP2, SLES for Raspberry Pi 12 SP2 +6 more 2.2.13-48.21.1

suse advisories SUSE-SU-2018:0867-1SUSE-SU-2018:0811-1

  • wireshark Alpine 3.24, Alpine 3.23, Alpine 3.22 +15 more 2.4.5-r0
  • wireshark Alpine 3.6 2.2.15-r0

alpine advisories ALPINE-CVE-2018-7332

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2018-7332 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

2.34% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-835 Loop with Unreachable Exit Condition

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.