CVE intelligence and bounded remediation
CVE-2017-5596 — Wireshark Wireshark security vulnerability
High
CVSS 7.5
In Wireshark 2.2.0 to 2.2.3 and 2.0.0 to 2.0.9, the ASTERIX dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-asterix.c by changing a data type to avoid an integer overflow.
- Severity
- High
- CVSS
- 7.5 (3.0)
- Published
- 2017-01-25
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-190, CWE-835
Affected products
- wireshark / wireshark / 2.0.0
- wireshark / wireshark / 2.0.1
- wireshark / wireshark / 2.0.2
- wireshark / wireshark / 2.0.3
- wireshark / wireshark / 2.0.4
- wireshark / wireshark / 2.0.5
Matched remediation archetype
Buffer bounds, memory safety, and memory corruption
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Identify affected native-code versions, build flags, architectures, parsers, codecs, drivers, and input paths in all shipped artifacts.
- Determine whether untrusted data reaches the affected routine and the process privilege, sandbox, and network exposure.
- Confirm statically linked, vendored, firmware, and platform-provided copies, not only package-manager records.
Remediate safely
- Apply the maintained upstream correction or replace the affected component, then rebuild every dependent artifact from clean inputs.
- Adopt bounds-checked interfaces, validated sizes and integer conversions, clear ownership, and memory-safe components where practical.
- Enable supported compiler and runtime hardening and add sanitized tests and fuzz regression seeds derived from non-weaponized fixtures.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.