Google Chrome 28.0.1500.95 Webstore 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.
6.0$0-$5k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in Google Chrome 28.0.1500.95. This affects an unknown function of the component Webstore. The manipulation leads to cross site scripting. This vulnerability is uniquely identified as CVE-2013-2887. The attack is possible to be carried out remotely. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome 28.0.1500.95 (Web Browser). It has been rated as critical. This issue affects an unknown code of the component Webstore. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Multiple unspecified vulnerabilities in Google Chrome before 29.0.1547.57 allow attackers to cause a denial of service or possibly have other impact via unknown vectors.

The weakness was disclosed 08/20/2013 with Google as 274602 (Website). It is possible to read the advisory at code.google.com. The identification of this vulnerability is CVE-2013-2887 since 04/11/2013. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.

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 and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 121395 (Google Chrome Prior to 29.0.1547.57 Multiple Vulnerabilities).

Upgrading to version 29.0.1547.57 eliminates this vulnerability. The upgrade is hosted for download at chrome.google.com. A possible mitigation has been published immediately after the disclosure of the vulnerability. The advisory contains the following remark:

This update includes 25 security fixes.

The vulnerability is also documented in the databases at Tenable (69423), SecurityFocus (BID 61885†), OSVDB (96468†) and Secunia (SA54479†). googlechromereleases.blogspot.com is providing further details. The entries VDB-9998, VDB-9999, VDB-10000 and VDB-10001 are pretty similar. Be aware that VulDB is the high quality source 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: 6.3
VulDB Meta Temp Score: 6.0

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
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-80 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

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: 🔍
Nessus Context: 🔍

OpenVAS ID: 892741
OpenVAS Name: Debian Security Advisory DSA 2741-1 (chromium-browser - several vulnerabilities
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Chrome 29.0.1547.57

Timelineinfo

04/11/2013 🔍
08/20/2013 +131 days 🔍
08/20/2013 +0 days 🔍
08/20/2013 +0 days 🔍
08/20/2013 +0 days 🔍
08/21/2013 +1 days 🔍
08/21/2013 +0 days 🔍
08/23/2013 +2 days 🔍
04/30/2019 +2076 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: 274602
Organization: Google
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2013-2887 (🔍)
GCVE (CVE): GCVE-0-2013-2887
GCVE (VulDB): GCVE-100-10007

OVAL: 🔍
IAVM: 🔍

SecurityFocus: 61885 - Google Chrome CVE-2013-2887 Multiple Unspecified Security Vulnerabilities
Secunia: 54479 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 96468

Misc.: 🔍
See also: 🔍

Entryinfo

Created: 08/23/2013 11:06
Updated: 04/30/2019 09:03
Changes: 08/23/2013 11:06 (84), 04/30/2019 09:03 (1)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!