Vulnerability Description
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.
CVSS Score
CRITICAL
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Webmproject | Libwebm | <= 1.0.0.27 |
Related Weaknesses (CWE)
References
- https://bugs.chromium.org/p/webm/issues/detail?id=1493Permissions Required
- https://github.com/dwfault/PoCs/blob/master/libwebm%20Vp9HeaderParser%20UAF%20byExploitThird Party Advisory
- https://bugs.chromium.org/p/webm/issues/detail?id=1493Permissions Required
- https://github.com/dwfault/PoCs/blob/master/libwebm%20Vp9HeaderParser%20UAF%20byExploitThird Party Advisory
FAQ
What is CVE-2018-6548?
CVE-2018-6548 is a vulnerability with a CVSS score of 9.8 (CRITICAL). 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::Vp9HeaderP...
How severe is CVE-2018-6548?
CVE-2018-6548 has been rated CRITICAL with a CVSS base score of 9.8/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2018-6548?
Check the references section above for vendor advisories and patch information. Affected products include: Webmproject Libwebm.