libwebm up to 2018-02-02 Vp9HeaderParser webm_info.cc SetFrame frame_ use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in libwebm up to 2018-02-02. It has been classified as critical. This vulnerability affects the function vp9parser::Vp9HeaderParser::SetFrame of the file webm_info.cc of the component Vp9HeaderParser. The manipulation of the argument frame_ leads to use after free.
This vulnerability is referenced as CVE-2018-6548. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in libwebm up to 2018-02-02 and classified as critical. This issue affects the function vp9parser::Vp9HeaderParser::SetFrame of the file webm_info.cc of the component Vp9HeaderParser. The manipulation of the argument frame_ with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
A use-after-free issue was discovered in libwebm through 2018-02-02. If a Vp9HeaderParser was initialized once before, its property frame_ would not be changed because of code in vp9parser::Vp9HeaderParser::SetFrame. Its frame_ could be freed while the corresponding pointer would not be updated, leading to a dangling pointer. This is related to the function OutputCluster in webm_info.cc.
The bug was discovered 02/02/2018. The weakness was published 02/02/2018 (Website). It is possible to read the advisory at bugs.chromium.org. The identification of this vulnerability is CVE-2018-6548 since 02/02/2018. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Use after freeCWE: CWE-416 / CWE-119
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/02/2018 🔍02/02/2018 🔍
02/02/2018 🔍
02/02/2018 🔍
02/03/2018 🔍
01/01/2020 🔍
Sources
Advisory: bugs.chromium.orgStatus: Not defined
CVE: CVE-2018-6548 (🔍)
GCVE (CVE): GCVE-0-2018-6548
GCVE (VulDB): GCVE-100-112775
Entry
Created: 02/03/2018 09:07Updated: 01/01/2020 11:20
Changes: 02/03/2018 09:07 (58), 01/01/2020 11:20 (1)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.