CVE-2005-1098: GetDataBack for NTFS 2.31 stores the username and license key in plaintext in the Name value in the License re
CVE-2005-1098 is a low-severity flaw (CVSS 2.1) affecting getdataback for ntfs. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- Public exploit reference
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 2.1 (Low) |
| EPSS exploit chance | 1.1% (top 34%) |
| CISA exploited list | No |
| Published | 2005-05-02 |
| Last modified | 2026-06-16 |
Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Public exploits and detection
Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.
- Exploit-DB: GetDataBack Data Recovery 2.31 - Licence Recover
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2005-1098?
getdataback for ntfs: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2005-1098 being exploited?
CVE-2005-1098 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2005-1098 affect?
CVE-2005-1098 affects getdataback for ntfs. Severity is low (CVSS 2.1). 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.
How urgent is CVE-2005-1098?
Priority 29/100. Public exploit reference