Wireshark up to 2.4.4 FCP Protocol Dissector packet-fcp.c Packet injection

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.3$0-$5k0.00

Summaryinfo

A vulnerability was found in Wireshark. It has been classified as problematic. The impacted element is an unknown function of the file epan/dissectors/packet-fcp.c of the component FCP Protocol Dissector. Performing a manipulation as part of Packet results in injection. This vulnerability is cataloged as CVE-2018-7336. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as problematic has been found in Wireshark (Packet Analyzer Software). This affects an unknown code block of the file epan/dissectors/packet-fcp.c of the component FCP Protocol Dissector. The manipulation as part of a Packet leads to a injection vulnerability. CWE is classifying the issue as CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. This is going to have an impact on availability. The summary by CVE is:

In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, the FCP protocol dissector could crash. This was addressed in epan/dissectors/packet-fcp.c by checking for a NULL pointer.

The bug was discovered 02/22/2018. The weakness was shared 02/23/2018 as Bug 14374 as confirmed bug report (Bugzilla). The advisory is shared at bugs.wireshark.org. This vulnerability is uniquely identified as CVE-2018-7336 since 02/22/2018. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1055 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 107093 (Wireshark 2.2.x < 2.2.13 / 2.4.x < 2.4.5 Multiple DoS Vulnerabilities), 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 371113 (F5 BIG-IP ASM and LTM Multiple Wireshark Vulnerabilities (K34035645)).

Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (107093) and SecurityFocus (BID 103166†). The entries VDB-113753, VDB-113754, VDB-113755 and VDB-113756 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

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.3

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Injection
CWE: CWE-74 / CWE-707 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 107093
Nessus Name: Wireshark 2.2.x < 2.2.13 / 2.4.x < 2.4.5 Multiple DoS Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 866192
OpenVAS Name: Wireshark Security Updates (wnpa-sec-2018-05 to -14) Mac OS X
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Patch: b56f598f1bc04f5d00f13b38c713763928cedb7c

Timelineinfo

02/22/2018 🔍
02/22/2018 +0 days 🔍
02/23/2018 +1 days 🔍
02/23/2018 +0 days 🔍
02/23/2018 +0 days 🔍
02/23/2018 +0 days 🔍
02/24/2018 +1 days 🔍
03/01/2018 +5 days 🔍
02/10/2023 +1807 days 🔍

Sourcesinfo

Product: wireshark.org

Advisory: Bug 14374
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2018-7336 (🔍)
GCVE (CVE): GCVE-0-2018-7336
GCVE (VulDB): GCVE-100-113769
SecurityFocus: 103166 - Wireshark FCP Dissector CVE-2018-7336 Denial of Service Vulnerability

See also: 🔍

Entryinfo

Created: 02/24/2018 12:29
Updated: 02/10/2023 07:49
Changes: 02/24/2018 12:29 (76), 01/08/2020 10:53 (6), 02/10/2023 07:49 (5)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!