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

> Local attackers can read stored credentials from the registry to gain unauthorized privileges in DelphiTurk CodeBank.

- **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:** 15 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2c67-m4vp-q6p7

## What is CVE-2005-0422?

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

### Official description

DelphiTurk CodeBank (aka KodBank) 3.1 and earlier stores usernames and passwords in the Codebank registry key, which allows local users to gain privileges.

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

It affects 1 product.


Products: Delphiturk Codebank.

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

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

## Is CVE-2005-0422 being exploited?

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

Public exploit code:

- DelphiTurk CodeBank 3.1 - Local Username and Password Disclosure (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-0422 is a low-severity vulnerability in n/a, published on 15 Feb 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-0422 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-0422/ (Markdown: https://insights.sbomify.com/CVE-2005-0422/index.md)
```

## Sources

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

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