Google Chrome up to 26.0.1410.65 denial of service

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

Summaryinfo

A vulnerability classified as problematic has been found in Google Chrome up to 26.0.1410.65. Affected by this vulnerability is an unknown functionality. The manipulation leads to denial of service. This vulnerability is uniquely identified as CVE-2013-2836. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome up to 26.0.1410.65 (Web Browser) and classified as problematic. This issue affects some unknown processing. The manipulation with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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

The weakness was disclosed 05/21/2013 as Issue 222770 as confirmed bug report (Website). It is possible to read the advisory at code.google.com. The public release has been coordinated in cooperation with Google. The identification of this vulnerability is CVE-2013-2836 since 04/11/2013. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 66549 (FreeBSD : chromium -- multiple vulnerabilities (358133b5-c2b9-11e2-a738-00262d5ed8ee)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 121201 (Google Chrome Prior to 27.0.1453.93 Multiple Vulnerabilities).

Upgrading to version 27.0.1453.93 eliminates this vulnerability. The upgrade is hosted for download at google.com. The problem might be mitigated by replacing the product with Mozilla Firefox, Microsoft Internet Explorer or Opera as an alternative. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (66549), SecurityFocus (BID 60062†), OSVDB (93944†) and Secunia (SA53430†). nakedsecurity.sophos.com is providing further details. The entries VDB-8503, VDB-8559, VDB-8661 and VDB-8840 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.6
VulDB Meta Temp Score: 5.4

VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Denial of service
CWE: CWE-404
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: 66549
Nessus Name: FreeBSD : chromium -- multiple vulnerabilities (358133b5-c2b9-11e2-a738-00262d5ed8ee)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 803705
OpenVAS Name: Google Chrome Multiple Vulnerabilities-01 May13 (Linux)
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 27.0.1453.93
Alternative: Mozilla Firefox/Microsoft Internet Explorer/Opera

Timelineinfo

04/11/2013 🔍
05/21/2013 +40 days 🔍
05/21/2013 +0 days 🔍
05/21/2013 +0 days 🔍
05/22/2013 +1 days 🔍
05/22/2013 +0 days 🔍
05/23/2013 +1 days 🔍
06/07/2013 +15 days 🔍
04/30/2019 +2153 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: Issue 222770
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2013-2836 (🔍)
GCVE (CVE): GCVE-0-2013-2836
GCVE (VulDB): GCVE-100-8987

OVAL: 🔍

SecurityFocus: 60062 - Google Chrome CVE-2013-2836 Multiple Unspecified Security Vulnerabilities
Secunia: 53430 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 93944

Misc.: 🔍
See also: 🔍

Entryinfo

Created: 06/07/2013 10:35
Updated: 04/30/2019 17:58
Changes: 06/07/2013 10:35 (83), 04/30/2019 17:58 (1)
Complete: 🔍
Cache ID: 216:EDF:103

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!