Google Chrome DocumentStyleSheetCollection.cpp addStyleSheetCandidateNode Remote Code Execution
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Chrome and classified as problematic. Impacted is the function DocumentStyleSheetCollection::addStyleSheetCandidateNode of the file dom/DocumentStyleSheetCollection.cpp. Executing a manipulation can lead to an unknown weakness.
The attack can be executed remotely. There is not any exploit available.
It is advisable to implement a patch to correct this issue.
Details
A vulnerability was found in Google Chrome (Web Browser) (the affected version is unknown). It has been declared as critical. This vulnerability affects the function DocumentStyleSheetCollection::addStyleSheetCandidateNode of the file dom/DocumentStyleSheetCollection.cpp. The impact remains unknown.
The weakness was released 08/09/2013 as 270272 as not defined changelog entry (Website). The advisory is shared for download at code.google.com. The public release was coordinated with the vendor. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. Responsible for the vulnerability is the following code:
TreeScope* treeScope = node->treeScope();
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. A possible mitigation has been published immediately after the disclosure of the vulnerability. The vulnerability will be addressed with the following lines of code:
TreeScope* treeScope = scopingNode ? scopingNode->treeScope() : m_document;
The vulnerability is also documented in the vulnerability database at OSVDB (96148†). Entries connected to this vulnerability are available at VDB-9917, VDB-9915, VDB-9914 and VDB-9912. Once again VulDB remains the best source for vulnerability data.
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: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
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: Remote Code ExecutionCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: chrome.google.com
Patch: chromium.googlesource.com
Timeline
08/09/2013 🔍08/09/2013 🔍
08/12/2013 🔍
06/07/2017 🔍
Sources
Vendor: google.comProduct: google.com
Advisory: 270272
Status: Not defined
Confirmation: 🔍
Coordinated: 🔍
GCVE (VulDB): GCVE-100-9916
OSVDB: 96148 - Google Chrome DocumentStyleSheetCollection Functions Node Handling Unspecified Impact
See also: 🔍
Entry
Created: 08/12/2013 17:21Updated: 06/07/2017 15:07
Changes: 08/12/2013 17:21 (50), 06/07/2017 15:07 (1)
Complete: 🔍
Committer:
Cache ID: 216:B1E:103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.