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

> Local attackers can read cleartext passwords from the Nortel VPN client process memory, exposing sensitive credentials.

- **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:** 24 Mar 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q4m9-8qj6-qg26

## What is CVE-2005-0844?

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

### Official description

Nortel VPN client 5.01 stores the cleartext password in the memory of the Extranet.exe process, which could allow local users to obtain sensitive information.

Weakness: CWE-310

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

It affects 1 product.


Products: Nortel Contivity.

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

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

## Is CVE-2005-0844 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-2333](https://insights.sbomify.com/CVE-2007-2333/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2007-2334](https://insights.sbomify.com/CVE-2007-2334/): Missing authorization in n/a (high 7.5)
- [CVE-2005-2579](https://insights.sbomify.com/CVE-2005-2579/): Privilege escalation in n/a (high 7.2)
- [CVE-2005-1802](https://insights.sbomify.com/CVE-2005-1802/): Denial of service in n/a (medium 5.0)
- [CVE-2004-1105](https://insights.sbomify.com/CVE-2004-1105/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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