VDB-8157 · OSVDB 91899 · GCVE-100-8157

WebkitGTK+ up to 2.0.0 WebCore/dom/Node.cpp enclosingBlockFlowElement Remote Code Execution

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

Summaryinfo

A vulnerability identified as problematic has been detected in WebkitGTK+ up to 2.0.0. The affected element is the function Node::enclosingBlockFlowElement of the file WebCore/dom/Node.cpp. Performing a manipulation results in Remote Code Execution. Moreover, an exploit is present. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability, which was classified as critical, was found in WebkitGTK+ up to 2.0.0 (Web Browser). This affects the function Node::enclosingBlockFlowElement of the file WebCore/dom/Node.cpp. The manipulation with an unknown input leads to a remote code execution vulnerability. This is going to have an impact on confidentiality, integrity, and availability.

The weakness was disclosed 04/01/2013 as not defined changelog entry (Website). The advisory is shared at trac.webkit.org. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known.

The exploit is shared for download at bugs.webkit.org. It is declared as proof-of-concept.

Applying a patch is able to eliminate this problem. The bugfix is ready for download at trac.webkit.org. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the vulnerability database at OSVDB (91899†). The entry VDB-8158 is pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.8
VulDB Meta Temp Score: 8.8

VulDB Base Score: 9.8
VulDB Temp Score: 8.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Remote Code Execution
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

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

Patch: trac.webkit.org

Timelineinfo

04/01/2013 🔍
04/01/2013 +0 days 🔍
04/04/2013 +3 days 🔍
05/05/2018 +1857 days 🔍

Sourcesinfo

Advisory: trac.webkit.org
Status: Not defined

GCVE (VulDB): GCVE-100-8157
OSVDB: 91899

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

Entryinfo

Created: 04/04/2013 16:33
Updated: 05/05/2018 18:00
Changes: 04/04/2013 16:33 (46), 05/05/2018 18:00 (1)
Complete: 🔍
Committer:
Cache ID: 216:8D7: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 ▸

Interested in the pricing of exploits?

See the underground prices here!