| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Chrome 4.0.263.0. It has been declared as problematic. The affected element is an unknown function. The manipulation results in access control. This vulnerability is cataloged as CVE-2010-5073. There is no exploit available.
Details
A vulnerability was found in Google Chrome 4.0.263.0 (Web Browser). It has been classified as problematic. Affected is some unknown processing. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality. CVE summarizes:
The JavaScript implementation in Google Chrome 4 does not properly restrict the set of values contained in the object returned by the getComputedStyle method, which allows remote attackers to obtain sensitive information about visited web pages by calling this method. NOTE: this may overlap CVE-2010-5070.
The weakness was shared 12/07/2011 (Website). The advisory is shared for download at w2spconf.com. This vulnerability is traded as CVE-2010-5073 since 12/07/2011. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1068.
Upgrading eliminates this vulnerability. The upgrade is hosted for download at chrome.google.com.
The vulnerability is also documented in the databases at X-Force (71811), SecurityFocus (BID 51054†) and Vulnerability Center (SBV-36094†). The entries VDB-59603, VDB-59602, VDB-59601 and VDB-59600 are related to this item. Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
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: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: CWE-264
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 |
OpenVAS ID: 802357
OpenVAS Name: Google Chrome Multiple Information Disclosure Vulnerabilities (Linux)
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Upgrade: chrome.google.com
Timeline
12/07/2011 🔍12/07/2011 🔍
12/07/2011 🔍
12/07/2011 🔍
12/13/2011 🔍
09/06/2012 🔍
03/23/2015 🔍
04/16/2017 🔍
Sources
Vendor: google.comProduct: google.com
Advisory: w2spconf.com
Status: Not defined
CVE: CVE-2010-5073 (🔍)
GCVE (CVE): GCVE-0-2010-5073
GCVE (VulDB): GCVE-100-59604
OVAL: 🔍
X-Force: 71811
SecurityFocus: 51054 - WebKit 'getComputedStyle()' Information Disclosure Vulnerability
Vulnerability Center: 36094 - The JavaScript Implementation in Google Chrome 4 Remote Information Disclosure Vulnerability, Medium
See also: 🔍
Entry
Created: 03/23/2015 16:50Updated: 04/16/2017 11:44
Changes: 03/23/2015 16:50 (56), 04/16/2017 11:44 (9)
Complete: 🔍
Cache ID: 216:B5D:103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.