Wireshark up to 2.4.4 SigComp Dissector packet-sigcomp.c length 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 identified as problematic has been detected in Wireshark. Affected by this vulnerability is an unknown functionality of the file epan/dissectors/packet-sigcomp.c of the component SigComp Dissector. This manipulation of the argument length as part of Packet causes injection. This vulnerability appears as CVE-2018-7418. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.

Detailsinfo

A vulnerability has been found in Wireshark (Packet Analyzer Software) and classified as problematic. Affected by this vulnerability is some unknown functionality of the file epan/dissectors/packet-sigcomp.c of the component SigComp Dissector. The manipulation of the argument length as part of a Packet leads to a injection vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect availability. The summary by CVE is:

In Wireshark 2.2.0 to 2.2.12 and 2.4.0 to 2.4.4, the SIGCOMP dissector could crash. This was addressed in epan/dissectors/packet-sigcomp.c by correcting the extraction of the length value.

The bug was discovered 02/22/2018. The weakness was presented 02/23/2018 as Bug 14410 as not defined bug report (Bugzilla). The advisory is shared at bugs.wireshark.org. This vulnerability is known as CVE-2018-7418 since 02/22/2018. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. 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 107001 (openSUSE Security Update : wireshark (openSUSE-2018-210)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks 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 2 days after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (107001) and SecurityFocus (BID 103157†). See VDB-113772, VDB-113774, VDB-113775 and VDB-113776 for similar entries. 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.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: 107001
Nessus Name: openSUSE Security Update : wireshark (openSUSE-2018-210)
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: 29d920b8309905dda11ad397596fe8aafc9b4bf7

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/24/2018 +1 days 🔍
02/25/2018 +1 days 🔍
02/26/2018 +1 days 🔍
07/16/2024 +2332 days 🔍

Sourcesinfo

Product: wireshark.org

Advisory: Bug 14410
Status: Not defined
Confirmation: 🔍

CVE: CVE-2018-7418 (🔍)
GCVE (CVE): GCVE-0-2018-7418
GCVE (VulDB): GCVE-100-113773
SecurityFocus: 103157 - Wireshark SIGCOMP Dissector 'epan/dissectors/packet-sigcomp.c' Denial of Service Vulnerability

See also: 🔍

Entryinfo

Created: 02/24/2018 12:30
Updated: 07/16/2024 16:32
Changes: 02/24/2018 12:30 (77), 01/08/2020 11:20 (6), 02/10/2023 08:06 (5), 07/16/2024 16:32 (16)
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 ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!