GNOME up to 3.7.91 TrackerIndexingTree Filter Rule tracker-indexing-tree.c memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in GNOME up to 3.7.91. The impacted element is an unknown function of the file tracker-indexing-tree.c of the component TrackerIndexingTree Filter Rule. This manipulation causes memory corruption. No exploit is available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in GNOME up to 3.7.91. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file tracker-indexing-tree.c of the component TrackerIndexingTree Filter Rule. 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 published 03/07/2013 as not defined changelog entry (Website). It is possible to read the advisory at ftp.gnome.org. The public release has been coordinated with the project team. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 3.7.92 eliminates this vulnerability. The upgrade is hosted for download at mail.gnome.org. Applying a patch is able to eliminate this problem. The bugfix is ready for download at mail.gnome.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 (94146†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
- 3.7.0
- 3.7.1
- 3.7.2
- 3.7.3
- 3.7.4
- 3.7.5
- 3.7.6
- 3.7.7
- 3.7.8
- 3.7.9
- 3.7.10
- 3.7.11
- 3.7.12
- 3.7.13
- 3.7.14
- 3.7.15
- 3.7.16
- 3.7.17
- 3.7.18
- 3.7.19
- 3.7.20
- 3.7.21
- 3.7.22
- 3.7.23
- 3.7.24
- 3.7.25
- 3.7.26
- 3.7.27
- 3.7.28
- 3.7.29
- 3.7.30
- 3.7.31
- 3.7.32
- 3.7.33
- 3.7.34
- 3.7.35
- 3.7.36
- 3.7.37
- 3.7.38
- 3.7.39
- 3.7.40
- 3.7.41
- 3.7.42
- 3.7.43
- 3.7.44
- 3.7.45
- 3.7.46
- 3.7.47
- 3.7.48
- 3.7.49
- 3.7.50
- 3.7.51
- 3.7.52
- 3.7.53
- 3.7.54
- 3.7.55
- 3.7.56
- 3.7.57
- 3.7.58
- 3.7.59
- 3.7.60
- 3.7.61
- 3.7.62
- 3.7.63
- 3.7.64
- 3.7.65
- 3.7.66
- 3.7.67
- 3.7.68
- 3.7.69
- 3.7.70
- 3.7.71
- 3.7.72
- 3.7.73
- 3.7.74
- 3.7.75
- 3.7.76
- 3.7.77
- 3.7.78
- 3.7.79
- 3.7.80
- 3.7.81
- 3.7.82
- 3.7.83
- 3.7.84
- 3.7.85
- 3.7.86
- 3.7.87
- 3.7.88
- 3.7.89
- 3.7.90
- 3.7.91
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.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: 🔍
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: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: GNOME 3.7.92
Patch: mail.gnome.org
Timeline
03/07/2013 🔍03/07/2013 🔍
06/12/2013 🔍
03/20/2019 🔍
Sources
Advisory: ftp.gnome.orgStatus: Not defined
Confirmation: 🔍
Coordinated: 🔍
GCVE (VulDB): GCVE-100-9115
OSVDB: 94146
Entry
Created: 06/12/2013 13:52Updated: 03/20/2019 08:35
Changes: 06/12/2013 13:52 (46), 03/20/2019 08:35 (1)
Complete: 🔍
Committer:
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.