# CVE-2005-2579: Privilege escalation in n/a

> Local users can escalate privileges by exploiting improper privilege dropping in the Nortel Contivity VPN Client certificate configuration dialog.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h8gr-xrvm-3293

## What is CVE-2005-2579?

CVE-2005-2579 is a high-severity vulnerability in n/a, published on 16 Aug 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Nortel Contivity VPN Client V05_01.030, when configuring a certificate to be used as authentication, does not properly drop system privileges, which allows local users to gain privileges by opening a program with the File Open dialog box.

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

It affects 1 product.


Products: Nortel Contivity.

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

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

## Is CVE-2005-2579 being exploited?

There is no known exploitation of CVE-2005-2579 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-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)
- [CVE-2000-0063](https://insights.sbomify.com/CVE-2000-0063/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2579 is a high-severity vulnerability in n/a, published on 16 Aug 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2005-2579 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-2579/ (Markdown: https://insights.sbomify.com/CVE-2005-2579/index.md)
```

## Sources

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

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