WebkitGTK+ up to 2.0.3 AccessibilityRenderObject.cpp computeAccessibilityIsIgnored Local Privilege Escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in WebkitGTK+ up to 2.0.3. The affected element is the function AccessibilityRenderObject::computeAccessibilityIsIgnored of the file accessibility/AccessibilityRenderObject.cpp. The manipulation leads to an unknown weakness.
There is not any exploit available.
It is suggested to install a patch to address this issue.
Details
A vulnerability was found in WebkitGTK+ up to 2.0.3 (Web Browser). It has been rated as problematic. This issue affects the function AccessibilityRenderObject::computeAccessibilityIsIgnored of the file accessibility/AccessibilityRenderObject.cpp. The impact remains unknown.
The weakness was released 05/07/2013 as not defined changelog entry (Website). The advisory is shared at trac.webkit.org. The public release was coordinated with the project team. Technical details are known, but no exploit is available.
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 (95133†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Local Privilege EscalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
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: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Patch: trac.webkit.org
Timeline
05/07/2013 🔍05/07/2013 🔍
07/16/2013 🔍
03/19/2019 🔍
Sources
Advisory: trac.webkit.orgStatus: Not defined
Confirmation: 🔍
Coordinated: 🔍
GCVE (VulDB): GCVE-100-9521
OSVDB: 95133
Entry
Created: 07/16/2013 12:44Updated: 03/19/2019 22:01
Changes: 07/16/2013 12:44 (43), 03/19/2019 22:01 (1)
Complete: 🔍
Committer:
Cache ID: 216:3CD:103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.