Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2016-2531

wireshark: RSL dissector crash (wnpa-sec-2016-10)

Overview

Published
28 Feb 2016
Modified
17 Jun 2026
Medium CVE
0 Registry packages
5 OS packages
4 Linux distributions
Yes Fix available

Description

Off-by-one error 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 allows remote attackers to cause a denial of service (out-of-bounds read and application crash) via a crafted packet that triggers a 0xff tag value, a different vulnerability than CVE-2016-2530.

Source: OX vulnerability database

Severity

5.9 · MEDIUM

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Weakness: CWE-119

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 7 fixes

Red Hat 1 release · 1 package

wont fix 1
wireshark
Red Hat fixes for CVE-2016-2531
ReleasePackageFixed in
7 wireshark +2 wont fix

debian 4 releases · 1 package

fixed 4
wireshark
debian fixes for CVE-2016-2531
ReleasePackageFixed in
11 wireshark 2.0.2+ga16e22e-1
12 wireshark 2.0.2+ga16e22e-1
13 wireshark 2.0.2+ga16e22e-1
14 wireshark 2.0.2+ga16e22e-1

echo 1 release · 1 package

fixed 1
wireshark
echo fixes for CVE-2016-2531
ReleasePackageFixed in
wireshark 2.0.2+ga16e22e-1

openSUSE 1 release · 1 package

fixed 1
wireshark
openSUSE fixes for CVE-2016-2531
ReleasePackageFixed inAdvisory
Tumbleweed wireshark +3 2.2.2-1.1 openSUSE-SU-2024:10199-1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.