CVE-2006-3675

Public Exploit

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.

2.1

CVSS

Severity: Low

CVSS 2.0 •

EPSS 0.11%

Third-Party Advisory securityreason.com

Affected: n/a n/a

References

Link	Tags
http://www.securityfocus.com/bid/19078	vdb entry exploit
http://securitytracker.com/id?1016565	vdb entry exploit
http://securityreason.com/securityalert/1308	third party advisory
http://www.symantec.com/enterprise/research/SYMSA-2006-008.txt	exploit
https://exchange.xforce.ibmcloud.com/vulnerabilities/27933	vdb entry
http://www.securityfocus.com/archive/1/441040/100/0/threaded	mailing list

Frequently Asked Questions

What is the severity of CVE-2006-3675?: CVE-2006-3675 has been scored as a low severity vulnerability.
How to fix CVE-2006-3675?: To fix CVE-2006-3675, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2006-3675 being actively exploited in the wild?: It is possible that CVE-2006-3675 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.

This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.