CVE-2004-2555 json
Riverdeep FoolProof Security 3.9.x on Windows 98 and Windows ME uses weak cryptography (arithmetic and XOR operations) to relate the Contro…
published 2004-12-31 21 y ago modified 2026-06-16 4 mo ago also EUVD-2004-2546
- cvss
- 2.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 57%
- public exploits
- 1
- Exploit-DB
Summary
Riverdeep FoolProof Security 3.9.x on Windows 98 and Windows ME uses weak cryptography (arithmetic and XOR operations) to relate the Control password to the Administrator password, which allows local users to calculate the Administrator password if they know the Control password and password recovery key.
Timeline
- First public exploit (EDB-24171)
- Published
Exploit prediction
0.83% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-24171 SmartStuff FoolProof Security Program 3.9.x - Administrative Password Recovery local, 2004-06-05
- osvdb.org http://www.osvdb.org/6735 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/10467 referenced PoC, tagged "exploit" by a source, unverified
- archives.neohapsis.com http://archives.neohapsis.com/archives/fulldisclosure/2004-06/0081.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
References
-
osvdb.org
/6735
vdb-entry, exploit
-
securityfocus.com
/bid/10467
vdb-entry, exploit
-
archives.neohapsis.com
/archives/fulldisclosure/2004-06/0081.html
mailing-list, exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/16327
vdb-entry
-
secunia.com
/advisories/11790
third-party-advisory
Sources
- CVE List CVE-2004-2555
- NVD CVE-2004-2555
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.