Google Chrome 34.0.1847.115 V8 Handler numeric error

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

Summaryinfo

A vulnerability marked as critical has been reported in Google Chrome 34.0.1847.115. This impacts an unknown function of the component V8 Handler. The manipulation leads to numeric error. This vulnerability is traded as CVE-2014-1721. There is no exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Google Chrome 34.0.1847.115 (Web Browser). This issue affects an unknown code of the component V8 Handler. The manipulation with an unknown input leads to a numeric error vulnerability. Using CWE to declare the problem leads to CWE-189. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Google V8, as used in Google Chrome before 34.0.1847.116, does not properly implement lazy deoptimization, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via crafted JavaScript code, as demonstrated by improper handling of a heap allocation of a number outside the Small Integer (aka smi) range.

The weakness was shared 04/08/2014 by Christian Holler (Cloudfuzzer) with Google as Stable Channel Update as confirmed release notes (Website). The advisory is shared at googlechromereleases.blogspot.dk. The identification of this vulnerability is CVE-2014-1721 since 01/29/2014. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 73431 (FreeBSD : chromium -- multiple vulnerabilities (963413a5-bf50-11e3-a2d6-00262d5ed8ee)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 166973 (OpenSuSE Security Update for chromium (openSUSE-SU-2014:0601-1)).

Upgrading to version 34.0.1847.116 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 vulnerability is also documented in the databases at X-Force (92368), Tenable (73431), SecurityFocus (BID 66704†), Secunia (SA57506†) and Vulnerability Center (SBV-43962†). The entries VDB-5661, VDB-5662, VDB-10842 and VDB-10843 are related to this item. 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: 7.3
VulDB Meta Temp Score: 6.4

VulDB Base Score: 7.3
VulDB Temp Score: 6.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Numeric error
CWE: CWE-189
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Unproven

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 73431
Nessus Name: FreeBSD : chromium -- multiple vulnerabilities (963413a5-bf50-11e3-a2d6-00262d5ed8ee)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 803358
OpenVAS Name: Google Chrome Multiple Vulnerabilities - 01 Apr14 (Windows)
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 34.0.1847.116

Timelineinfo

01/29/2014 🔍
04/08/2014 +69 days 🔍
04/08/2014 +0 days 🔍
04/08/2014 +0 days 🔍
04/08/2014 +0 days 🔍
04/08/2014 +0 days 🔍
04/09/2014 +1 days 🔍
04/09/2014 +0 days 🔍
04/16/2014 +7 days 🔍
05/10/2026 +4407 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: Stable Channel Update
Researcher: Christian Holler (Cloudfuzzer)
Organization: Google
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2014-1721 (🔍)
GCVE (CVE): GCVE-0-2014-1721
GCVE (VulDB): GCVE-100-12989

OVAL: 🔍
IAVM: 🔍

X-Force: 92368 - Google Chrome V8 code execution, Medium Risk
SecurityFocus: 66704 - Google Chrome Prior to 34.0.1847.116 Multiple Security Vulnerabilities
Secunia: 57506 - Google Chrome Multiple Vulnerabilities, Highly Critical
Vulnerability Center: 43962 - Google Chrome Before 34.0.1847.116 Remote DoS or Other Impact due to Memory Corruption in V8, High

See also: 🔍

Entryinfo

Created: 04/16/2014 12:43
Updated: 05/10/2026 04:15
Changes: 04/16/2014 12:43 (86), 05/24/2017 11:39 (5), 06/17/2021 11:06 (3), 05/10/2026 04:15 (16)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!