Google Chrome 31.0.1650.63 AccessibilityTable.cpp isDataTable 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.
6.7$0-$5k0.00

Summaryinfo

A vulnerability categorized as problematic has been discovered in Google Chrome 31.0.1650.63. This affects the function AccessibilityTable::isDataTable of the file core/accessibility/AccessibilityTable.cpp. Such manipulation leads to denial of service. This vulnerability is referenced as CVE-2013-6644. Furthermore, an exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome 31.0.1650.63 (Web Browser) and classified as critical. Affected by this issue is the function AccessibilityTable::isDataTable of the file core/accessibility/AccessibilityTable.cpp. 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 availability. CVE summarizes:

Multiple unspecified vulnerabilities in Google Chrome before 32.0.1700.76 on Windows and before 32.0.1700.77 on Mac OS X and Linux allow attackers to cause a denial of service or possibly have other impact via unknown vectors.

The weakness was published 10/16/2013 as Tracking bug for internal security fixes for Chrome 32, Release 0 as confirmed advisory (Website). The advisory is shared for download at code.google.com. The public release has been coordinated with the vendor. This vulnerability is handled as CVE-2013-6644 since 11/05/2013. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a public exploit are known.

It is declared as proof-of-concept. As 0-day the estimated underground price was around $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 72538 (Debian DSA-2862-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 122879 (Debian Security Update for chromium-browser (DSA 2862-1)).

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

The vulnerability is also documented in the databases at Tenable (72538), SecurityFocus (BID 64805†), OSVDB (102309†) and Secunia (SA56248†). googlechromereleases.blogspot.ch is providing further details. Similar entries are available at VDB-11958, VDB-11959, VDB-11960 and VDB-11961. Once again VulDB remains the best source for vulnerability data.

Affected

  • Google Chrome 31.0.1650.63
  • WebKitGTK+ 2.2.3/2.3.4

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.5
VulDB Meta Temp Score: 6.7

VulDB Base Score: 7.5
VulDB Temp Score: 6.7
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: 🔍
Access: Public
Status: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 72538
Nessus Name: Debian DSA-2862-1 : chromium-browser - several vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 702862
OpenVAS Name: Debian Security Advisory DSA 2862-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 32.0.1700.76

Timelineinfo

10/16/2013 🔍
11/05/2013 +20 days 🔍
01/14/2014 +69 days 🔍
01/14/2014 +0 days 🔍
01/14/2014 +0 days 🔍
01/16/2014 +2 days 🔍
01/21/2014 +5 days 🔍
02/17/2014 +27 days 🔍
06/08/2021 +2668 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: Tracking bug for internal security fixes for Chrome 32, Release 0
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2013-6644 (🔍)
GCVE (CVE): GCVE-0-2013-6644
GCVE (VulDB): GCVE-100-12020

OVAL: 🔍
IAVM: 🔍

SecurityFocus: 64805
Secunia: 56248 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 102309

Misc.: 🔍
See also: 🔍

Entryinfo

Created: 01/21/2014 15:45
Updated: 06/08/2021 14:41
Changes: 01/21/2014 15:45 (81), 05/17/2018 08:37 (7), 06/08/2021 14:41 (4)
Complete: 🔍
Committer:
Cache ID: 216:3D8:103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!