Google Chrome 31.0.1650.57 Media Subsample Calculation/Conversion integer coercion

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

Summaryinfo

A vulnerability was found in Google Chrome 31.0.1650.57 and classified as critical. Affected by this issue is some unknown functionality of the component Media Subsample Calculation/Conversion Handler. Executing a manipulation can lead to integer coercion. This vulnerability is handled as CVE-2013-6637. There is not any exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as very critical was found in Google Chrome 31.0.1650.57 (Web Browser). This vulnerability affects an unknown code of the component Media Subsample Calculation/Conversion Handler. The manipulation with an unknown input leads to a integer coercion vulnerability. The CWE definition for the vulnerability is CWE-192. Integer coercion refers to a set of flaws pertaining to the type casting, extension, or truncation of primitive data types. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

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

The weakness was released 11/19/2013 as 317999 as confirmed advisory (Website). The advisory is available at googlechromereleases.blogspot.com. This vulnerability was named CVE-2013-6637 since 11/05/2013. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 06/02/2021). 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 71254 (Debian DSA-2811-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 166599 (OpenSuSE Security Update for Chromium (openSUSE-SU-2013:1927-1)).

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

The vulnerability is also documented in the databases at Tenable (71254), SecurityFocus (BID 64078†), OSVDB (100592†) and Secunia (SA55942†). Additional details are provided at code.google.com. Entries connected to this vulnerability are available at VDB-11377, VDB-11378, VDB-11379 and VDB-11380. 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: Integer coercion
CWE: CWE-192 / CWE-189
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: 71254
Nessus Name: Debian DSA-2811-1 : chromium-browser - several vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 892811
OpenVAS Name: Debian Security Advisory DSA 2811-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 31.0.1650.63

Timelineinfo

11/05/2013 🔍
11/19/2013 +14 days 🔍
12/04/2013 +14 days 🔍
12/04/2013 +0 days 🔍
12/05/2013 +1 days 🔍
12/06/2013 +1 days 🔍
12/06/2013 +0 days 🔍
12/09/2013 +3 days 🔍
06/02/2021 +2732 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: 317999
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2013-6637 (🔍)
GCVE (CVE): GCVE-0-2013-6637
GCVE (VulDB): GCVE-100-11386

OVAL: 🔍
IAVM: 🔍

SecurityFocus: 64078
Secunia: 55942 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 100592
SecurityTracker: 1029442

Misc.: 🔍
See also: 🔍

Entryinfo

Created: 12/06/2013 09:49
Updated: 06/02/2021 19:34
Changes: 12/06/2013 09:49 (76), 05/15/2018 10:20 (7), 06/02/2021 19:26 (2), 06/02/2021 19:34 (2)
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 ▸

Might our Artificial Intelligence support you?

Check our Alexa App!