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

> Local attackers can read cleartext credentials from the Dev Hound configuration file to escalate privileges.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 23 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-ggvw-gcq7-rp4h

## What is CVE-2005-4506?

CVE-2005-4506 is a medium-severity vulnerability in n/a, published on 23 Dec 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Nexus Concepts Dev Hound 2.24 and earlier stores username and password information in cleartext in the devhound.tdbd file, which allows local users to gain privileges.

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

It affects 1 product.


Products: Nexus Concepts Dev Hound.

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

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

## Is CVE-2005-4506 being exploited?

There is no known exploitation of CVE-2005-4506 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2005-4508](https://insights.sbomify.com/CVE-2005-4508/): Information disclosure in n/a (medium 5.0)
- [CVE-2005-4507](https://insights.sbomify.com/CVE-2005-4507/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-4506 is a medium-severity vulnerability in n/a, published on 23 Dec 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-4506 in the wild and no public exploit code.

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-4506/ (Markdown: https://insights.sbomify.com/CVE-2005-4506/index.md)
```

## Sources

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

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