CVE-1999-1497
Ipswitch IMail 5.0 and 6.0 uses weak encryption to store passwords in registry keys, which allows...
Ipswitch IMail 5.0 and 6.0 uses weak encryption to store passwords in registry keys, which allows local attackers to read passwords for e-mail accounts.
Exploit likelihood
What each source reports
NVD Score used
7.2
Ipswitch IMail 5.0 and 6.0 uses weak encryption to store passwords in registry keys, which allows local attackers to read passwords for e-mail accounts.
- Record
CVE-1999-1497- CVSS 2.0
- 7.2 High
AV:L/AC:L/Au:N/C:C/I:C/A:C - Updated
- 2026-11-02
CVE List No score
Ipswitch IMail 5.0 and 6.0 uses weak encryption to store passwords in registry keys, which allows local attackers to read passwords for e-mail accounts.
- Record
CVE-1999-1497- Updated
- 2026-11-02
EUVDEUVD-1999-1478 No score
Ipswitch IMail 5.0 and 6.0 uses weak encryption to store passwords in registry keys, which allows local attackers to read passwords for e-mail accounts.
- Record
EUVD-1999-1478- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-q3wh-6m92-8378 No score
Ipswitch IMail 5.0 and 6.0 uses weak encryption to store passwords in registry keys, which allows...
Ipswitch IMail 5.0 and 6.0 uses weak encryption to store passwords in registry keys, which allows local attackers to read passwords for e-mail accounts.
- Record
GHSA-q3wh-6m92-8378- Updated
- 2026-11-02
Affected products
Public exploits
Links only. Every CVE stores no exploit code.
| Source | Link | Date |
|---|---|---|
| Exploit-DB | Ipswitch IMail Server 5.0/5.0.5/5.0.6/5.0.7/5.0.8/6.0 - Weak Password Encryption | 1999-12-19 |
| Exploit-DB | IPSwitch IMail Server 8.1 - Local Password Decryption Utility | 2004-08-18 |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, Exploit-DB, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-1999-1497 is a high vulnerability (CVSS 7.2) in Ipswitch Imail, published December 21, 1999. Public exploit code exists. EPSS puts the chance of exploitation in the next 30 days at 1.40%, the 72nd percentile. No source names a fixed version.