cve.bz

CVE-2017-5596 wireshark wireshark: Year 2038 problem, Y2K38, Y2038, Epochalypse

7.5 highEPSS 2.9%Fix available

High (7.5) in wireshark wireshark. EPSS 2.9% estimated probability of exploitation activity in the next 30 days.

On this page
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

CVSS 3.0

7.5 high
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
2.9% (unchanged from 2.9% a week ago; 2.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 87th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
CWE-835 Loop with Unreachable Exit Condition (Infinite Loop)
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2017-5596 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-5596?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-5596?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-5596 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
wireshark:wireshark2.0.0
wireshark:wireshark2.0.1
wireshark:wireshark2.0.2
wireshark:wireshark2.0.3
wireshark:wireshark2.0.4
wireshark:wireshark2.0.5
wireshark:wireshark2.0.6
wireshark:wireshark2.0.7
wireshark:wireshark2.0.8
wireshark:wireshark2.0.9
wireshark:wireshark2.2.0
wireshark:wireshark2.2.1
wireshark:wireshark2.2.2
wireshark:wireshark2.2.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian7wireshark1.12.1+g01b65bf-4+deb8u6~deb7u7DLA-858-1
Debian8wireshark1.12.1+g01b65bf-4+deb8u11DSA-3811-1
Debian12, 13, 14wireshark2.2.4+gcc3dc1b-1DEBIAN-CVE-2017-5596
Ubuntu14.04:LTSwireshark1.12.1+g01b65bf-4+deb8u11ubuntu0.14.04.1UBUNTU-CVE-2017-5596
Ubuntu16.04:LTSwireshark2.2.6+g32dac6a-2ubuntu0.16.04UBUNTU-CVE-2017-5596
SUSELinux Enterprise Desktop 12 SP1, Linux Enterprise Desktop 12 SP2, Linux Enterprise Server 12 SP1 and 6 morewireshark2.2.6-44.3SUSE-SU-2017:1442-1
SUSELinux Enterprise Server 11 SP4, Linux Enterprise Server for SAP Applications 11 SP4, Linux Enterprise Software Development Kit 11 SP4wireshark2.0.12-36.1SUSE-SU-2017:1174-1
openSUSETumbleweedwireshark3.4.8-1.2openSUSE-SU-2024:11513-1
Alpinev3.5wireshark2.2.4-r0ALPINE-CVE-2017-5596

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpine.

Red Hat

Red Hat rates this Moderate.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 5wiresharkWill not fix
Red Hat Enterprise Linux 6wiresharkWill not fix
Red Hat Enterprise Linux 7wiresharkWill not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2017-5596.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON