Runtime Software GetDataBack for NTFS 2.31 Registry cleartext storage
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.8 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in Runtime Software GetDataBack for NTFS 2.31. Affected by this issue is some unknown functionality of the component Registry. Executing a manipulation can lead to cleartext storage. This vulnerability is registered as CVE-2005-1098. Furthermore, an exploit is available.
Details
A vulnerability classified as problematic was found in Runtime Software GetDataBack for NTFS 2.31. This vulnerability affects an unknown function of the component Registry. The manipulation with an unknown input leads to a cleartext storage vulnerability. The CWE definition for the vulnerability is CWE-312. The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere. As an impact it is known to affect confidentiality. CVE summarizes:
GetDataBack for NTFS 2.31 stores the username and license key in plaintext in the Name value in the License registry key, which may allow local users to obtain sensitive information.
The weakness was published 04/06/2005 by kozan and ATmaCA (Website). The advisory is available at osvdb.org. This vulnerability was named CVE-2005-1098 since 04/13/2005. The exploitation appears to be easy. Local access is required to approach this attack. No form of authentication is required for a successful exploitation. Technical details are unknown but a public exploit is available. This vulnerability is assigned to T1555 by the MITRE ATT&CK project.
A public exploit has been developed by Kozan and been published even before and not after the advisory. It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (19967), Exploit-DB (912), OSVDB (15210†) and SecurityTracker (ID 1013644†). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.0VulDB Meta Temp Score: 3.8
VulDB Base Score: 4.0
VulDB Temp Score: 3.8
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cleartext storageCWE: CWE-312 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: Kozan
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/15/2005 🔍04/04/2005 🔍
04/05/2005 🔍
04/05/2005 🔍
04/06/2005 🔍
04/13/2005 🔍
05/02/2005 🔍
03/11/2015 🔍
07/23/2017 🔍
Sources
Advisory: osvdb.org⛔Researcher: kozan, ATmaCA
Status: Confirmed
CVE: CVE-2005-1098 (🔍)
GCVE (CVE): GCVE-0-2005-1098
GCVE (VulDB): GCVE-100-24850
X-Force: 19967
OSVDB: 15210 - GetDataBack Registry Cleartext License Information Disclosure
SecurityTracker: 1013644 - GetDataBack for NTFS Discloses License Key to Local Users
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/11/2015 11:41Updated: 07/23/2017 10:42
Changes: 03/11/2015 11:41 (50), 07/23/2017 10:42 (12)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.