Wireshark up to 1.12.8/2.0.0 DIAMETER Dissector packet-diameter.c dissect_diameter_base_framed_ipv6_prefix input validation

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.1$0-$5k0.00

Summaryinfo

A vulnerability has been found in Wireshark up to 1.12.8/2.0.0 and classified as critical. Affected by this vulnerability is the function dissect_diameter_base_framed_ipv6_prefix of the file epan/dissectors/packet-diameter.c of the component DIAMETER Dissector. The manipulation leads to input validation. This vulnerability is traded as CVE-2015-8725. Furthermore, there is an exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Wireshark up to 1.12.8/2.0.0 (Packet Analyzer Software) and classified as critical. This issue affects the function dissect_diameter_base_framed_ipv6_prefix of the file epan/dissectors/packet-diameter.c of the component DIAMETER Dissector. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

The dissect_diameter_base_framed_ipv6_prefix function in epan/dissectors/packet-diameter.c in the DIAMETER dissector in Wireshark 1.12.x before 1.12.9 and 2.0.x before 2.0.1 does not validate the IPv6 prefix length, which allows remote attackers to cause a denial of service (stack-based buffer overflow and application crash) via a crafted packet.

The weakness was shared 01/04/2016 with Google (Website). The advisory is shared at code.wireshark.org. The identification of this vulnerability is CVE-2015-8725 since 01/03/2016. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known.

The exploit is available at exploit-db.com. It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 87824 (Wireshark 1.12.x < 1.12.9 Multiple DoS), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Windows and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 175659 (Debian Security Update for wireshark (DSA 3505-1)).

Upgrading to version 1.12.9 or 2.0.1 eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (87824) and SecurityFocus (BID 79382†). The entries VDB-78868, VDB-80055, VDB-80056 and VDB-80057 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.4
VulDB Meta Temp Score: 6.1

VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Input validation
CWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 87824
Nessus Name: Wireshark 1.12.x < 1.12.9 Multiple DoS
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 802978
OpenVAS Name: Wireshark Multiple Denial-of-Service Vulnerabilities-02 January16 (Windows)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Wireshark 1.12.9/2.0.1
Patch: aaa28a9d39158ca1033bbd3372cf423abbf4f202

Timelineinfo

12/03/2015 🔍
12/29/2015 +26 days 🔍
01/03/2016 +5 days 🔍
01/04/2016 +1 days 🔍
01/04/2016 +0 days 🔍
01/05/2016 +1 days 🔍
01/08/2016 +3 days 🔍
12/22/2024 +3271 days 🔍

Sourcesinfo

Product: wireshark.org

Advisory: code.wireshark.org⛔
Organization: Google
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2015-8725 (🔍)
GCVE (CVE): GCVE-0-2015-8725
GCVE (VulDB): GCVE-100-80069

OVAL: 🔍

SecurityFocus: 79382 - Wireshark Multiple Security Vulnerabilities
SecurityTracker: 1034551

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 01/05/2016 08:28
Updated: 12/22/2024 22:58
Changes: 01/05/2016 08:28 (69), 05/27/2018 12:07 (12), 07/02/2022 09:49 (6), 07/02/2022 09:54 (1), 12/22/2024 22:58 (24)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!