CVE-2017-5596Not scoredCWE-190

CVE-2017-5596

Vendor not named in the CVE record

Vendor fix available · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

2.9%probability of exploitation in the next 30 days

87th percentile

050100

Higher than 87% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

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.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Integer Overflow · Memory Corruption
Published: January 2017
Band: Possible (1 to 10%), January 2017

CoverageNo articles yet

No CyberSIXT article names CVE-2017-5596 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.