Google Chrome up to 4.1 WebKit platform/KURLGoogle.cpp protocolIs cross site scripting

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.9$0-$5k0.00

Summaryinfo

A vulnerability described as problematic has been identified in Google Chrome up to 4.1. The impacted element is the function protocolIs of the file platform/KURLGoogle.cpp of the component WebKit. The manipulation results in cross site scripting. This vulnerability is cataloged as CVE-2010-1236. The attack may be launched remotely. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Google Chrome up to 4.1 (Web Browser). Affected is the function protocolIs of the file platform/KURLGoogle.cpp of the component WebKit. The manipulation with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. CVE summarizes:

The protocolIs function in platform/KURLGoogle.cpp in WebCore in WebKit before r55822, as used in Google Chrome before 4.1.249.1036 and Flock Browser 3.x before 3.0.0.4112, does not properly handle whitespace at the beginning of a URL, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a crafted javascript: URL, as demonstrated by a \x00javascript:alert sequence.

The weakness was shared 04/01/2010 by Sergey Glazunov (Website). The advisory is available at bugs.webkit.org. This vulnerability is traded as CVE-2010-1236 since 04/01/2010. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1059.007 by the MITRE ATT&CK project.

It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 45086 (Google Chrome < 4.1.249.1036 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Windows. The commercial vulnerability scanner Qualys is able to test this issue with plugin 117083 (Google Chrome Code Execution and Security Bypass Vulnerabilities).

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 databases at Tenable (45086), SecurityFocus (BID 38829†), Secunia (SA43068†) and Vulnerability Center (SBV-25595†). The entries VDB-50798, VDB-50797, VDB-50136 and VDB-53804 are related to this item. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 3.9

VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Cross site scripting
CWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 45086
Nessus Name: Google Chrome < 4.1.249.1036 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 801312
OpenVAS Name: Google Chrome Multiple Vulnerabilities (win)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Chrome 4.0.263.0

Timelineinfo

03/17/2010 🔍
03/17/2010 +0 days 🔍
04/01/2010 +15 days 🔍
04/01/2010 +0 days 🔍
04/01/2010 +0 days 🔍
05/04/2010 +33 days 🔍
01/25/2011 +266 days 🔍
03/19/2015 +1514 days 🔍
05/04/2026 +4064 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: bugs.webkit.org
Researcher: Sergey Glazunov
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2010-1236 (🔍)
GCVE (CVE): GCVE-0-2010-1236
GCVE (VulDB): GCVE-100-52554

OVAL: 🔍

SecurityFocus: 38829 - Google Chrome prior to 4.1.249.1036 Multiple Security Vulnerabilities
Secunia: 43068 - SUSE update for Multiple Packages, Highly Critical
Vulnerability Center: 25595 - Google Chrome \x3C 4.1.249.1036 Allows Cross Origin Operations, Medium
Vupen: ADV-2011-0212

See also: 🔍

Entryinfo

Created: 03/19/2015 12:22
Updated: 05/04/2026 18:31
Changes: 03/19/2015 12:22 (66), 02/23/2017 22:05 (14), 09/07/2021 03:58 (2), 01/26/2025 10:37 (18), 05/04/2026 18:31 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!