Google Chrome 31.0.1650.57 Empty Inline RenderBlockLineLayout.cpp handleEndOfLine 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.
9.0$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Google Chrome 31.0.1650.57. This impacts the function BreakingContext::handleEndOfLine of the file rendering/RenderBlockLineLayout.cpp of the component Empty Inline Handler. This manipulation causes use after free. This vulnerability appears as CVE-2013-6637. In addition, an exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome 31.0.1650.57 (Web Browser). It has been declared as critical. Affected by this vulnerability is the function BreakingContext::handleEndOfLine of the file rendering/RenderBlockLineLayout.cpp of the component Empty Inline Handler. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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 presented 11/07/2013 as 305904 as confirmed advisory (Website). It is possible to read the advisory at googlechromereleases.blogspot.com. This vulnerability is known as CVE-2013-6637 since 11/05/2013. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known.

It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $100k and more. 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 4 weeks after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (71254), SecurityFocus (BID 64078†), OSVDB (100589†) and Secunia (SA55942†). Additional details are provided at code.google.com. See VDB-11377, VDB-11378, VDB-11379 and VDB-11380 for similar entries. 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: 10.0
VulDB Meta Temp Score: 9.0

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

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/07/2013 +2 days 🔍
12/04/2013 +27 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: 305904
Status: Confirmed
Confirmation: 🔍

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

OVAL: 🔍
IAVM: 🔍

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

scip Labs: https://www.scip.ch/en/?labs.20161013
Misc.: 🔍
See also: 🔍

Entryinfo

Created: 12/06/2013 09:49
Updated: 06/02/2021 18:55
Changes: 12/06/2013 09:49 (80), 05/15/2018 10:20 (7), 06/02/2021 18:55 (2)
Complete: 🔍
Cache ID: 216::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!