CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
8.4 | $0-$5k | 0.00 |
A vulnerability has been found in Google Chrome (Web Browser) and classified as critical. This vulnerability affects an unknown function. The manipulation with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-80. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
Unspecified vulnerability in Google Chrome before 4.1.249.1059 allows remote attackers to access local files via vectors related to "developer tools."
The weakness was released 04/23/2010 by Meder Kydyraliev (SkyLined) (Website). The advisory is available at securityfocus.com. This vulnerability was named CVE-2010-1502. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1059.007 by the MITRE ATT&CK project.
The vulnerability scanner Nessus provides a plugin with the ID 45610 (Google Chrome < 4.1.249.1059 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Windows.
Upgrading to version 4.0.263.0 eliminates this vulnerability. The upgrade is hosted for download at chrome.google.com.
The vulnerability is also documented in the vulnerability database at Tenable (45610). Entries connected to this vulnerability are available at 52910, 52909, 52908 and 52907.
Product
Type
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv3
VulDB Meta Base Score: 8.8VulDB Meta Temp Score: 8.4
VulDB Base Score: 8.8
VulDB Temp Score: 8.4
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: Cross site scriptingCWE: CWE-80 / CWE-74 / CWE-707
ATT&CK: T1059.007
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 |
Nessus ID: 45610
Nessus Name: Google Chrome < 4.1.249.1059 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
OpenVAS ID: 902050
OpenVAS Name: Google Chrome Multiple Vulnerabilities (win)
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Chrome 4.0.263.0
Timeline
04/20/2010 🔍04/20/2010 🔍
04/23/2010 🔍
04/23/2010 🔍
04/23/2010 🔍
04/26/2010 🔍
03/19/2015 🔍
09/08/2021 🔍
Sources
Vendor: google.comProduct: google.com
Advisory: securityfocus.com⛔
Researcher: Meder Kydyraliev (SkyLined)
Status: Not defined
Confirmation: 🔍
CVE: CVE-2010-1502 (🔍)
OVAL: 🔍
Vulnerability Center: 25528 - Google Chrome Remote Information Disclosure Vulnerability via Vectors Related to Developer Tools, Medium
SecurityFocus: 39603 - RETIRED: Google Chrome prior to 4.1.249.1059 Multiple Security Vulnerabilities
See also: 🔍
Entry
Created: 03/19/2015 12:22 PMUpdated: 09/08/2021 01:03 PM
Changes: 03/19/2015 12:22 PM (59), 02/23/2017 11:40 AM (11), 09/08/2021 12:56 PM (4), 09/08/2021 01:03 PM (1)
Complete: 🔍
No comments yet. Languages: en.
Please log in to comment.