# CVE-2006-1164: Information disclosure in n/a

> Remote attackers can obtain usernames and password hashes by directly accessing the list.gtdat file stored under the web document root.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-24gw-2pw3-2rvr

## What is CVE-2006-1164?

CVE-2006-1164 is a high-severity vulnerability in n/a, published on 12 Mar 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Nodez 4.6.1.1 and earlier stores sensitive data in the list.gtdat file under the web document root with insufficient access control, which allows remote attackers to obtain usernames and password hashes by directly accessing list.gtdat.

## Which versions are affected by CVE-2006-1164?

It affects 1 product.


Products: Nodez Nodez.

## How do I fix CVE-2006-1164?

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

## Is CVE-2006-1164 being exploited?

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

Public exploit code:

- nodez 4.6.1.1 mercury - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-1163](https://insights.sbomify.com/CVE-2006-1163/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2006-1162](https://insights.sbomify.com/CVE-2006-1162/): Path traversal in n/a (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-1164 and fix it if it is affected.

What it is: CVE-2006-1164 is a high-severity vulnerability in n/a, published on 12 Mar 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-1164 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-2006-1164/ (Markdown: https://insights.sbomify.com/CVE-2006-1164/index.md)
```

## Sources

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

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