CVE-2006-1378 json
PasswordSafe 3.0 beta, when running on Windows before XP, uses a weak random number generator (C++ rand function) during generation of the…
published 2006-03-24 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-1382
- cvss
- 4.9
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 25%
- public exploits
- 0
- none known
Summary
PasswordSafe 3.0 beta, when running on Windows before XP, uses a weak random number generator (C++ rand function) during generation of the database encryption key, which makes it easier for attackers to decrypt the database and steal passwords by generating keys for all possible rand() seed values and conducting a known plaintext attack.
Exploit prediction
0.33% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- securityfocus.com http://www.securityfocus.com/bid/17200 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.9 | AV:L/AC:L/Au:N/C:C/I:N/A:N |
References
-
securityfocus.com
/bid/17200
vdb-entry, exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/25429
vdb-entry
-
securityreason.com
/securityalert/618
third-party-advisory
-
securityfocus.com
/archive/1/428552/100/0/threaded
mailing-list
-
securityfocus.com
/archive/1/445509/100/0/threaded
mailing-list
Sources
- CVE List CVE-2006-1378
- NVD CVE-2006-1378
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.