Google Chrome 29.0.1547.76 Quota Dispatcher Termination quota_dispatcher_host.cc RequestQuotaDispatcher use after free

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.
9.5$5k-$25k0.00

Summaryinfo

A vulnerability was found in Google Chrome 29.0.1547.76. It has been declared as critical. This affects the function RequestQuotaDispatcher of the file quota_dispatcher_host.cc of the component Quota Dispatcher Termination Handler. Such manipulation leads to use after free. This vulnerability is uniquely identified as CVE-2013-2923. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome 29.0.1547.76 (Web Browser) and classified as very critical. Affected by this issue is the function RequestQuotaDispatcher of the file quota_dispatcher_host.cc of the component Quota Dispatcher Termination Handler. The manipulation with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. Impacted is confidentiality, integrity, and availability. CVE summarizes:

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

The weakness was disclosed 09/09/2013 as 285380 (Website). The advisory is available at code.google.com. This vulnerability is handled as CVE-2013-2923 since 04/11/2013. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 05/13/2018). It is expected to see the exploit prices for this product increasing in the near future.

The vulnerability scanner Nessus provides a plugin with the ID 70636 (Debian DSA-2785-1 : chromium-browser - several vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 166720 (OpenSuSE Security Update for chromium (openSUSE-SU-2014:0065-1)).

Upgrading to version 30.0.1599.66 eliminates this vulnerability. The upgrade is hosted for download at chrome.google.com. A possible mitigation has been published 4 weeks after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (70636), SecurityFocus (BID 62752†), OSVDB (98004†) and Secunia (SA55087†). googlechromereleases.blogspot.com is providing further details. The entries VDB-9992, VDB-10161, VDB-10162 and VDB-10163 are pretty similar. 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: 10.0
VulDB Meta Temp Score: 9.5

VulDB Base Score: 10.0
VulDB Temp Score: 9.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
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: 70636
Nessus Name: Debian DSA-2785-1 : chromium-browser - several vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 892794
OpenVAS Name: Debian Security Advisory DSA 2785-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 30.0.1599.66

Timelineinfo

04/11/2013 🔍
09/09/2013 +151 days 🔍
10/01/2013 +22 days 🔍
10/02/2013 +1 days 🔍
10/02/2013 +0 days 🔍
10/03/2013 +1 days 🔍
10/27/2013 +24 days 🔍
05/13/2018 +1659 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: 285380
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2013-2923 (🔍)
GCVE (CVE): GCVE-0-2013-2923
GCVE (VulDB): GCVE-100-10562

OVAL: 🔍
IAVM: 🔍

SecurityFocus: 62752
Secunia: 55087 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 98004

Misc.: 🔍
See also: 🔍

Entryinfo

Created: 10/03/2013 15:15
Updated: 05/13/2018 10:20
Changes: 10/03/2013 15:15 (76), 05/13/2018 10:20 (8)
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 want to use VulDB in your project?

Use the official API to access entries easily!