Wireshark up to 3.2.7 Facebook Zero Protocol Dissector packet-fbzero.c by infinite loop

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

Summaryinfo

A vulnerability classified as problematic was found in Wireshark up to 3.2.7. Affected by this vulnerability is an unknown functionality of the file epan/dissectors/packet-fbzero.c by of the component Facebook Zero Protocol Dissector. Executing a manipulation can lead to infinite loop. This vulnerability is handled as CVE-2020-26575. There is not any exploit available. It is advisable to implement a patch to correct this issue.

Detailsinfo

A vulnerability classified as problematic was found in Wireshark up to 3.2.7 (Packet Analyzer Software). This vulnerability affects an unknown function of the file epan/dissectors/packet-fbzero.c by of the component Facebook Zero Protocol Dissector. The manipulation with an unknown input leads to a infinite loop vulnerability. The CWE definition for the vulnerability is CWE-835. The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. As an impact it is known to affect availability.

The weakness was released 10/07/2020. The advisory is shared for download at gitlab.com. This vulnerability was named CVE-2020-26575. There are known technical details, but no exploit is available.

Applying a patch is able to eliminate this problem. The bugfix is ready for download at gitlab.com.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.4

VulDB Base Score: 3.5
VulDB Temp Score: 3.4
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: Infinite loop
CWE: CWE-835 / CWE-404
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

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Patch: gitlab.com

Timelineinfo

10/06/2020 🔍
10/07/2020 +1 days 🔍
10/07/2020 +0 days 🔍
11/16/2020 +40 days 🔍

Sourcesinfo

Product: wireshark.org

Advisory: gitlab.com
Status: Not defined
Confirmation: 🔍

CVE: CVE-2020-26575 (🔍)
GCVE (CVE): GCVE-0-2020-26575
GCVE (VulDB): GCVE-100-162316

Entryinfo

Created: 10/07/2020 08:29
Updated: 11/16/2020 21:41
Changes: 10/07/2020 08:29 (25), 10/07/2020 08:32 (13), 11/15/2020 10:21 (4), 11/16/2020 21:34 (3), 11/16/2020 21:41 (14)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!