# CVE-2006-3675: Security feature bypass in n/a

> Attackers with physical access can bypass database locking to read sensitive password data when specific dialogues are open.

- **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:** 28 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9pc9-9hf2-9g5g

## What is CVE-2006-3675?

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

### Official description

Password Safe 2.11, 2.16 and 3.0BETA1 does not respect the configuration settings for locking the password database when certain dialogue windows are open, which might allow attackers with physical access to obtain the database contents.

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

It affects 1 product.


Products: Counterpane Passwordsafe.

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

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

## Is CVE-2006-3675 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-3801](https://insights.sbomify.com/CVE-2005-3801/): Weak cryptography in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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