Google Chrome 38.0.2125.7 DOM 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.
6.4$5k-$25k0.00

Summaryinfo

A vulnerability was found in Google Chrome 38.0.2125.7 and classified as critical. The impacted element is an unknown function of the component DOM Handler. Such manipulation leads to use after free. This vulnerability is listed as CVE-2014-3192. There is no available exploit. A patch should be applied to remediate this issue.

Detailsinfo

A vulnerability was found in Google Chrome 38.0.2125.7 (Web Browser). It has been rated as critical. Affected by this issue is an unknown code of the component DOM 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.

The weakness was presented 10/07/2014 by Takeshi Terada (cloudfuzzer) with OUSPG as Stable Channel Update, October 2014 as confirmed release notes (Website). The advisory is available at googlechromereleases.blogspot.com. This vulnerability is handled as CVE-2014-3192 since 05/03/2014. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 02/21/2022). 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 81145 (Apple TV < 7.0.3 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Misc. and running in the context r. The commercial vulnerability scanner Qualys is able to test this issue with plugin 195644 (Ubuntu Security Notification for Oxide-qt Vulnerabilities (USN-2345-1)).

Upgrading to version 38.0.2125.101 eliminates this vulnerability. The upgrade is hosted for download at chrome.google.com. Applying a patch is able to eliminate this problem. The best possible mitigation is suggested to be patching the affected component. A possible mitigation has been published immediately after the disclosure of the vulnerability. The release notes contains the following remark:

This update includes 159 security fixes, including 113 relatively minor fixes found using MemorySanitizer.

The vulnerability is also documented in the databases at X-Force (96961), Tenable (81145), SecurityFocus (BID 70273†) and SecurityTracker (ID 1030980†). chromium.googlesource.com is providing further details. See VDB-67475, VDB-67476, VDB-67774 and VDB-67775 for similar entries. 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: 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: Use after free
CWE: CWE-416 / CWE-119
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: 81145
Nessus Name: Apple TV < 7.0.3 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 840722
OpenVAS Name: Google Chrome Multiple Vulnerabilities - 01 Oct14 (Windows)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Chrome 38.0.2125.101

Timelineinfo

05/03/2014 🔍
10/07/2014 +157 days 🔍
10/07/2014 +0 days 🔍
10/07/2014 +0 days 🔍
10/08/2014 +1 days 🔍
10/09/2014 +1 days 🔍
10/13/2014 +4 days 🔍
02/03/2015 +113 days 🔍
02/21/2022 +2575 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: Stable Channel Update, October 2014
Researcher: Takeshi Terada (cloudfuzzer)
Organization: OUSPG
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2014-3192 (🔍)
GCVE (CVE): GCVE-0-2014-3192
GCVE (VulDB): GCVE-100-67778

OVAL: 🔍
IAVM: 🔍

X-Force: 96961 - Google Chrome DOM code execution, Medium Risk
SecurityFocus: 70273 - Google Chrome Prior to 38.0.2125.101 Multiple Security Vulnerabilities
SecurityTracker: 1030980

Misc.: 🔍
See also: 🔍

Entryinfo

Created: 10/13/2014 12:15
Updated: 02/21/2022 17:00
Changes: 10/13/2014 12:15 (86), 05/02/2019 21:07 (5), 02/21/2022 17:00 (3)
Complete: 🔍
Cache ID: 216:978:103

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!