Wireshark 3.0.0 Rbm Dissector file-rbm.c resource management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Wireshark 3.0.0. Impacted is an unknown function of the file epan/dissectors/file-rbm.c of the component Rbm Dissector. Performing a manipulation results in resource management. This vulnerability is cataloged as CVE-2019-10900. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability, which was classified as problematic, was found in Wireshark 3.0.0 (Packet Analyzer Software). This affects some unknown functionality of the file epan/dissectors/file-rbm.c of the component Rbm Dissector. The manipulation with an unknown input leads to a resource management vulnerability. CWE is classifying the issue as CWE-399. This is going to have an impact on availability. The summary by CVE is:
In Wireshark 3.0.0, the Rbm dissector could go into an infinite loop. This was addressed in epan/dissectors/file-rbm.c by handling unknown object types safely.
The bug was discovered 04/08/2019. The weakness was shared 04/09/2019 by Mateusz Jurczyk (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2019-10900 since 04/05/2019. 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.
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 commercial vulnerability scanner Qualys is able to test this issue with plugin 371730 (Wireshark Multiple Security Vulnerabilities (wnpa-sec-2019-09 to wnpa-sec-2019-18)).
Applying the patch 26eee01f57f0a86fb375892c7937eac24ede4610 is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 107834†). The entries VDB-133144, VDB-133145, VDB-133143 and VDB-133146 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
Website
- Product: https://www.wireshark.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Resource managementCWE: CWE-399 / 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-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: 26eee01f57f0a86fb375892c7937eac24ede4610
Timeline
04/05/2019 🔍04/08/2019 🔍
04/09/2019 🔍
04/09/2019 🔍
04/09/2019 🔍
08/27/2023 🔍
Sources
Product: wireshark.orgAdvisory: FEDORA-2019-77b2d840ef⛔
Researcher: Mateusz Jurczyk
Status: Confirmed
CVE: CVE-2019-10900 (🔍)
GCVE (CVE): GCVE-0-2019-10900
GCVE (VulDB): GCVE-100-133149
SecurityFocus: 107834 - Wireshark Multiple Denial of Service Vulnerabilities
See also: 🔍
Entry
Created: 04/09/2019 09:33Updated: 08/27/2023 14:55
Changes: 04/09/2019 09:33 (60), 05/27/2020 16:16 (5), 08/27/2023 14:55 (5)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.