Strix
26.1K

CVE-2016-2530

UnknownEPSS 2.74%

Last modified

CVE-2016-2530 is a vulnerability of currently unknown severity. The dissct_rsl_ipaccess_msg function in epan/dissectors/packet-rsl.c in the RSL dissector in Wireshark 1.12.x before 1.12.10 and 2.0.x before 2.0.2 mishandles the case of an unrecognized TLV type, which allows remote attackers to cause a denial of service (out-of-bounds read and application crash) via a crafted packet, a different vulnerability than CVE-2016-2531.. EPSS estimates a 2.74% chance of exploitation in the next 30 days.

Description

The dissct_rsl_ipaccess_msg function in epan/dissectors/packet-rsl.c in the RSL dissector in Wireshark 1.12.x before 1.12.10 and 2.0.x before 2.0.2 mishandles the case of an unrecognized TLV type, which allows remote attackers to cause a denial of service (out-of-bounds read and application crash) via a crafted packet, a different vulnerability than CVE-2016-2531.

Metrics

EPSS Probability
2.74%

84.3th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
WiresharkWireshark1.12.0
WiresharkWireshark1.12.1
WiresharkWireshark1.12.2
WiresharkWireshark1.12.3
WiresharkWireshark1.12.4
WiresharkWireshark1.12.5
WiresharkWireshark1.12.6
WiresharkWireshark1.12.7
WiresharkWireshark1.12.8
WiresharkWireshark1.12.9
WiresharkWireshark2.0.0
WiresharkWireshark2.0.1

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-2530?
The dissct_rsl_ipaccess_msg function in epan/dissectors/packet-rsl.c in the RSL dissector in Wireshark 1.12.x before 1.12.10 and 2.0.x before 2.0.2 mishandles the case of an unrecognized TLV type, which allows remote attackers to cause a denial of service (out-of-bounds read and application crash) via a crafted packet, a different vulnerability than CVE-2016-2531.
How severe is CVE-2016-2530?
Severity scoring for CVE-2016-2530 is pending analysis. The EPSS model estimates a 2.74% probability of exploitation in the next 30 days.
How do I fix CVE-2016-2530?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2016-2530?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST