Breaking News: Hijacked Releases of Microsoft’s Official agent-framework Steals Azure and CI Credentials
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-9374

wireshark: AllJoyn crash (wnpa-sec-2016-59)

Overview

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

Description

In Wireshark 2.2.0 to 2.2.1 and 2.0.0 to 2.0.7, the AllJoyn dissector could crash with a buffer over-read, triggered by network traffic or a capture file. This was addressed in epan/dissectors/packet-alljoyn.c by ensuring that a length variable properly tracked the state of a signature variable.

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, CWE-399

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-9374
ReleasePackageFixed in
7 wireshark +2 wont fix

debian 4 releases · 1 package

fixed 4
wireshark
debian fixes for CVE-2016-9374
ReleasePackageFixed in
11 wireshark 2.2.2+g9c5aae3-1
12 wireshark 2.2.2+g9c5aae3-1
13 wireshark 2.2.2+g9c5aae3-1
14 wireshark 2.2.2+g9c5aae3-1

echo 1 release · 1 package

fixed 1
wireshark
echo fixes for CVE-2016-9374
ReleasePackageFixed in
wireshark 2.2.2+g9c5aae3-1

openSUSE 1 release · 1 package

fixed 1
wireshark
openSUSE fixes for CVE-2016-9374
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.