| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in database 2.11. The impacted element is an unknown function. This manipulation causes information disclosure. This vulnerability is registered as CVE-2006-3675. No exploit is available. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability classified as problematic was found in database 2.11. Affected by this vulnerability is some unknown processing. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:
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.
The weakness was published 07/28/2006 (Website). It is possible to read the advisory at securityfocus.com. This vulnerability is known as CVE-2006-3675 since 07/18/2006. The exploitation appears to be easy. Attacking locally is a requirement. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the databases at X-Force (27933), SecurityFocus (BID 19078†) and SecurityTracker (ID 1016565†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.0VulDB Meta Temp Score: 3.5
VulDB Base Score: 4.0
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Unproven
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
07/18/2006 🔍07/24/2006 🔍
07/25/2006 🔍
07/28/2006 🔍
07/28/2006 🔍
03/12/2015 🔍
09/16/2017 🔍
Sources
Advisory: securityfocus.com⛔Status: Confirmed
CVE: CVE-2006-3675 (🔍)
GCVE (CVE): GCVE-0-2006-3675
GCVE (VulDB): GCVE-100-31555
X-Force: 27933 - Password Safe lock weak security
SecurityFocus: 19078 - Password Safe Local Insecure Idle Timeout Lock Vulnerability
SecurityTracker: 1016565 - Password Safe May Fail to Lock the Password Database
Entry
Created: 03/12/2015 14:25Updated: 09/16/2017 10:36
Changes: 03/12/2015 14:25 (50), 09/16/2017 10:36 (6)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.