# CVE-2006-5406: Misconfiguration in n/a

> Local attackers can read and modify sensitive files due to insecure directory permissions in Passgo Defender.

- **Severity:** Low 3.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:N`)
- **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:** 19 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7c4f-6qqr-r9w5

## What is CVE-2006-5406?

CVE-2006-5406 is a low-severity vulnerability in n/a, published on 19 Oct 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Passgo Defender 5.2 creates the application directory with insecure permissions (Everyone/Full Control), which allows local users to read and modify sensitive files.  NOTE: the provenance of this information is unknown; the details are obtained from third party information.

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

It affects 1 product.


Products: Passgo Defender.

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

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

## Is CVE-2006-5406 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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