Google Chrome 47 DOM access control

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

Summaryinfo

A vulnerability classified as critical has been found in Google Chrome 47. This affects an unknown function of the component DOM Handler. This manipulation causes access control. This vulnerability is handled as CVE-2015-6768. There is not any exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome 47 (Web Browser). It has been declared as critical. Affected by this vulnerability is some unknown processing of the component DOM Handler. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect integrity. The summary by CVE is:

The DOM implementation in Google Chrome before 47.0.2526.73 allows remote attackers to bypass the Same Origin Policy via unspecified vectors, a different vulnerability than CVE-2015-6770.

The weakness was released 12/01/2015 by Mariusz Mlynski (Cloudfuzzer) with Qihoo 360 as Stable Channel Update, December 2015 as confirmed release notes (Blog). It is possible to read the advisory at googlechromereleases.blogspot.com. This vulnerability is known as CVE-2015-6768 since 08/31/2015. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/28/2022). It is expected to see the exploit prices for this product increasing in the near future.The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

The vulnerability scanner Nessus provides a plugin with the ID 87289 (Debian DSA-3415-1 : chromium-browser - security update), 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 175578 (Debian Security Update for chromium-browser (DSA 3415-1)).

Upgrading to version 47.0.2526.73 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 (108406), Tenable (87289), SecurityFocus (BID 78416†) and Vulnerability Center (SBV-54718†). Entries connected to this vulnerability are available at VDB-79137, VDB-79348, VDB-79349 and VDB-79350. Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 4.6

VulDB Base Score: 5.3
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Access control
CWE: CWE-264
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: 87289
Nessus Name: Debian DSA-3415-1 : chromium-browser - security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 703415
OpenVAS Name: Debian Security Advisory DSA 3415-1 (chromium-browser - security update)
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 47.0.2526.73

Timelineinfo

08/31/2015 🔍
12/01/2015 +92 days 🔍
12/01/2015 +0 days 🔍
12/01/2015 +0 days 🔍
12/01/2015 +0 days 🔍
12/02/2015 +1 days 🔍
12/02/2015 +0 days 🔍
12/05/2015 +3 days 🔍
12/10/2015 +5 days 🔍
06/28/2022 +2392 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: Stable Channel Update, December 2015
Researcher: Mariusz Mlynski (Cloudfuzzer)
Organization: Qihoo 360
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2015-6768 (🔍)
GCVE (CVE): GCVE-0-2015-6768
GCVE (VulDB): GCVE-100-79351

OVAL: 🔍

X-Force: 108406 - Google Chrome DOM security bypass
SecurityFocus: 78416 - Google Chrome Prior to 47.0.2526.73 Multiple Security Vulnerabilities
SecurityTracker: 1034298
Vulnerability Center: 54718 - Google Chrome <47.0.2526.73 Remote Cross Origin Bypass in DOM - CVE-2015-6768, High

See also: 🔍

Entryinfo

Created: 12/02/2015 10:17
Updated: 06/28/2022 08:51
Changes: 12/02/2015 10:17 (73), 05/09/2018 11:50 (14), 06/28/2022 08:51 (3)
Complete: 🔍
Cache ID: 216:A49:103

Be aware that VulDB is the high quality source for vulnerability data.

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!