# CVE-2006-5965: Privilege escalation in n/a

> Local attackers can escalate privileges by modifying files in the PassGo SSO Plus directory due to insecure default permissions.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h5p4-whh5-9jp9

## What is CVE-2006-5965?

CVE-2006-5965 is a medium-severity vulnerability in n/a, published on 26 Nov 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

PassGo SSO Plus 2.1.0.32, and probably earlier versions, uses insecure permissions (Everyone/Full Control) for the PassGo Technologies directory, which allows local users to gain privileges by modifying critical programs.

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

It affects 1 product.


Products: Passgo Sso Plus.

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

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

## Is CVE-2006-5965 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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