# CVE-2005-1098: Information disclosure in n/a

> Local attackers can read plaintext license credentials from the registry, exposing sensitive user information in GetDataBack for NTFS.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Apr 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wjhp-jhm5-c75h

## What is CVE-2005-1098?

CVE-2005-1098 is a low-severity vulnerability in n/a, published on 13 Apr 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2005-1098?

It affects 1 product.


Products: Runtime Software Getdataback for Ntfs.

## How do I fix CVE-2005-1098?

No fix has been published for CVE-2005-1098 yet. Limit exposure of the affected software until one is available.

## Is CVE-2005-1098 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1098 exists.

Public exploit code:

- GetDataBack Data Recovery 2.31 - Licence Recover (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1098 and fix it if it is affected.

What it is: CVE-2005-1098 is a low-severity vulnerability in n/a, published on 13 Apr 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1098 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2005-1098/ (Markdown: https://insights.sbomify.com/CVE-2005-1098/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2005-1098
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2005-1098
- OSV: https://osv.dev/vulnerability/CVE-2005-1098

---
From sbomify Insights: https://insights.sbomify.com/CVE-2005-1098/
Summaries are generated and may contain mistakes; the official description above is the record.