WebkitGTK+ 1.10.2 RenderObject.cpp willBeDestroyed memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in WebkitGTK+ 1.10.2 and classified as critical. This impacts the function RenderObject::willBeDestroyed of the file WebCore/rendering/RenderObject.cpp. Executing a manipulation can lead to memory corruption.
Additionally, an exploit exists.
It is suggested to upgrade the affected component.
Details
A vulnerability has been found in WebkitGTK+ 1.10.2 (Web Browser) and classified as critical. This vulnerability affects the function RenderObject::willBeDestroyed of the file WebCore/rendering/RenderObject.cpp. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was released 01/11/2013 as not defined bug report (Website). The advisory is available at trac.webkit.org. The public release was coordinated with the vendor. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details and also a public exploit are known.
It is declared as proof-of-concept.
Upgrading to version 2.0.0 eliminates this vulnerability. The upgrade is hosted for download at trac.webkit.org. Applying a patch is able to eliminate this problem. The bugfix is ready for download at trac.webkit.org. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (92500†). Entries connected to this vulnerability are available at VDB-8448 and VDB-8447. Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 9.0
VulDB Base Score: 10.0
VulDB Temp Score: 9.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: WebkitGTK+ 2.0.0
Patch: trac.webkit.org
Timeline
01/11/2013 🔍01/11/2013 🔍
04/19/2013 🔍
05/05/2018 🔍
Sources
Advisory: trac.webkit.orgStatus: Not defined
Coordinated: 🔍
GCVE (VulDB): GCVE-100-8446
OSVDB: 92500
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 04/19/2013 18:13Updated: 05/05/2018 18:07
Changes: 04/19/2013 18:13 (48), 05/05/2018 18:07 (2)
Complete: 🔍
Committer:
Cache ID: 216:B5A:103
No comments yet. Languages: en.
Please log in to comment.