Google Chrome WebVTTParser.cpp createDocumentFragmentFromCueText denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Chrome. It has been classified as problematic. The affected element is the function WebVTTParser::createDocumentFragmentFromCueText of the file html/track/WebVTTParser.cpp. The manipulation leads to denial of service.
The attack is possible to be carried out remotely. Moreover, an exploit is present.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Google Chrome (Web Browser) (unknown version). It has been rated as problematic. This issue affects the function WebVTTParser::createDocumentFragmentFromCueText of the file html/track/WebVTTParser.cpp. The manipulation with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is availability.
The weakness was disclosed 08/10/2013 as not defined changelog entry (Website). The advisory is shared at chromiumcodereview.appspot.com. The public release has been coordinated in cooperation with Google. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1499 for this issue.
The exploit is available at chromium.googlesource.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $5k-$25k.
Upgrading eliminates this vulnerability. The upgrade is hosted for download at chrome.google.com. Applying a patch is able to eliminate this problem. The bugfix is ready for download at chromium.googlesource.com. The best possible mitigation is suggested to be patching the affected component.
The vulnerability is also documented in the vulnerability database at OSVDB (96149†). The entries VDB-9916, VDB-9915 and VDB-9914 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.google.com/
- Product: https://www.google.com/chrome/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Denial of serviceCWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
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: PatchStatus: 🔍
0-Day Time: 🔍
Upgrade: chrome.google.com
Patch: chromium.googlesource.com
Timeline
08/10/2013 🔍08/12/2013 🔍
06/07/2017 🔍
Sources
Vendor: google.comProduct: google.com
Advisory: chromiumcodereview.appspot.com
Status: Not defined
Confirmation: 🔍
Coordinated: 🔍
GCVE (VulDB): GCVE-100-9917
OSVDB: 96149 - Google Chrome WebVTTParser::createDocumentFragmentFromCueText Function Empty Text Handling DoS
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 08/12/2013 17:22Updated: 06/07/2017 15:07
Changes: 08/12/2013 17:22 (50), 06/07/2017 15:07 (2)
Complete: 🔍
Committer:
Cache ID: 216:DB8: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.