Google Chrome 28.0.1500.95 browser.cookie cross-site request forgery

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.
4.8$0-$5k0.00

Summaryinfo

A vulnerability has been found in Google Chrome 28.0.1500.95 and classified as problematic. Affected is an unknown function of the file browser.cookie. This manipulation causes cross-site request forgery. This vulnerability is tracked as CVE-2013-6166. Moreover, an exploit is present. To fix this issue, it is recommended to deploy a patch.

Detailsinfo

A vulnerability has been found in Google Chrome 28.0.1500.95 (Web Browser) and classified as problematic. Affected by this vulnerability is an unknown part of the file browser.cookie. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. As an impact it is known to affect availability. The summary by CVE is:

Google Chrome before 29 sends HTTP Cookie headers without first validating that they have the required character-set restrictions, which allows remote attackers to conduct the equivalent of a persistent Logout CSRF attack via a crafted parameter that forces a web application to set a malformed cookie within an HTTP response.

The weakness was disclosed 10/10/2013 by Stefan Bühler as confirmed mailinglist post (oss-sec). It is possible to read the advisory at seclists.org. The vendor was not involved in the public release. This vulnerability is known as CVE-2013-6166 since 10/16/2013. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known.

It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 69423 (Google Chrome < 29.0.1547.57 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Windows.

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 code.google.com. The best possible mitigation is suggested to be patching the affected component.

The vulnerability is also documented in the databases at X-Force (88109), Exploit-DB (38420), Tenable (69423), OSVDB (98762†) and Vulnerability Center (SBV-43848†). The entries VDB-9998, VDB-9999, VDB-10000 and VDB-10001 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 4.8

VulDB Base Score: 5.3
VulDB Temp Score: 4.8
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 request forgery
CWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 69423
Nessus Name: Google Chrome < 29.0.1547.57 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 801329
OpenVAS Name: Google Chrome Cross-Site Request Forgery (CSRF) Vulnerability (Windows)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Upgrade: chrome.google.com
Patch: code.google.com

Timelineinfo

04/04/2013 🔍
10/10/2013 +189 days 🔍
10/16/2013 +6 days 🔍
10/22/2013 +6 days 🔍
02/15/2014 +116 days 🔍
04/01/2014 +45 days 🔍
12/15/2024 +3911 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: seclists.org
Researcher: Stefan Bühler
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2013-6166 (🔍)
GCVE (CVE): GCVE-0-2013-6166
GCVE (VulDB): GCVE-100-10867

OVAL: 🔍

X-Force: 88109
OSVDB: 98762
Vulnerability Center: 43848 - Google Chrome Before 29.0.1547.57 Remote Code Execution Vulnerability via a Crafted Parameter, Medium

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 10/22/2013 17:42
Updated: 12/15/2024 16:13
Changes: 10/22/2013 17:42 (73), 05/24/2017 10:54 (2), 05/31/2021 14:46 (3), 12/15/2024 16:13 (23)
Complete: 🔍
Committer:
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you know our Splunk app?

Download it now for free!