Google Chrome 28.0.1500.95 document::finishedparsing resource management

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

Summaryinfo

A vulnerability marked as problematic has been reported in Google Chrome 28.0.1500.95. Affected by this vulnerability is the function document::finishedparsing of the file document::finishedparsing. This manipulation causes resource management. This vulnerability is handled as CVE-2013-2904. There is not any exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Google Chrome 28.0.1500.95 (Web Browser) and classified as critical. Affected by this vulnerability is the function document::finishedparsing of the file document::finishedparsing. The manipulation with an unknown input leads to a resource management vulnerability. The CWE definition for the vulnerability is CWE-399. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Use-after-free vulnerability in the Document::finishedParsing function in core/dom/Document.cpp in Blink, as used in Google Chrome before 29.0.1547.57, allows remote attackers to cause a denial of service or possibly have unspecified other impact via an onload event that changes an IFRAME element so that its src attribute is no longer an XML document, leading to unintended garbage collection of this document.

The weakness was released 08/20/2013 by Christian Jaeger (Cloudfuzzer) with Google Security Team as confirmed changelog entry (Website). The advisory is shared at googlechromereleases.blogspot.com. The public release was coordinated with Google. This vulnerability is known as CVE-2013-2904 since 04/11/2013. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 69470 (Debian DSA-2741-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. The commercial vulnerability scanner Qualys is able to test this issue with plugin 121395 (Google Chrome Prior to 29.0.1547.57 Multiple Vulnerabilities).

Upgrading to version 29.0.1547.57 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 Tenable (69470), SecurityFocus (BID 61865†), OSVDB (96435†), Secunia (SA54479†) and Vulnerability Center (SBV-41165†). Entries connected to this vulnerability are available at VDB-9998, VDB-9999, VDB-10000 and VDB-10001. 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: 7.0

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

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Resource management
CWE: CWE-399 / CWE-404
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: 69470
Nessus Name: Debian DSA-2741-1 : chromium-browser - several vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 892741
OpenVAS Name: Debian Security Advisory DSA 2741-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 29.0.1547.57

Timelineinfo

04/11/2013 🔍
08/20/2013 +131 days 🔍
08/20/2013 +0 days 🔍
08/20/2013 +0 days 🔍
08/20/2013 +0 days 🔍
08/21/2013 +1 days 🔍
08/21/2013 +0 days 🔍
08/23/2013 +2 days 🔍
05/21/2021 +2828 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: googlechromereleases.blogspot.com
Researcher: Christian Jaeger (Cloudfuzzer)
Organization: Google Security Team
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2013-2904 (🔍)
GCVE (CVE): GCVE-0-2013-2904
GCVE (VulDB): GCVE-100-10021

OVAL: 🔍
IAVM: 🔍

SecurityFocus: 61865 - RETIRED: Google Chrome Prior to 29.0.1547.57 Multiple Security Vulnerabilities
Secunia: 54479 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 96435
Vulnerability Center: 41165 - Google Chrome Before 29.0.1547.57 Remote Unspecified Vulnerability (CVE-2013-2904), High

See also: 🔍

Entryinfo

Created: 08/23/2013 12:53
Updated: 05/21/2021 16:31
Changes: 08/23/2013 12:53 (85), 05/09/2017 10:24 (4), 05/21/2021 16:31 (3)
Complete: 🔍
Committer:
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 ▸

Do you need the next level of professionalism?

Upgrade your account now!