CVE-2005-2160
published 2005-07-06CVE-2005-2160: IMail stores usernames and passwords in cleartext in a cookie, which allows remote attackers to obtain sensitive information.
PriorityP423high7.5CVSS 3.1
AVNACLPRNUINSUCHINAN
EPSS
1.96%
77.8th percentile
IMail stores usernames and passwords in cleartext in a cookie, which allows remote attackers to obtain sensitive information.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| ipswitch | imail | — | — |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:P/I:N/A:N
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
CWE
Cleartext Storage of Sensitive Information
mitre_cwe
CWE-312 Cleartext Storage of Sensitive Information
CWE-312: Cleartext Storage of Sensitive Information
The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
Modes of Introduction:
Phase: Architecture and Design
Note: OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.
Common Consequences:
Scope: Confidentiality. Impact: Read Application Data. An attacker with access to the system could read sensitive information stored in cleartext (i.e., unencrypted). Even if the information is encoded in a way that is not human-readable, certain techniques could determine which encoding is being used, then decode the information.
Detection Methods:
Automated Static Analysis: Automated static analysis, commonly referred to as Stat
CWE
Cleartext Storage of Sensitive Information in a Cookie
mitre_cwe·CVSS 7.5
[HIGH] CWE-315 Cleartext Storage of Sensitive Information in a Cookie
CWE-315: Cleartext Storage of Sensitive Information in a Cookie
The product stores sensitive information in cleartext in a cookie.
Attackers can use widely-available tools to view the cookie and read the sensitive information. Even if the information is encoded in a way that is not human-readable, certain techniques could determine which encoding is being used, then decode the information.
Modes of Introduction:
Phase: Architecture and Design
Note: OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.
Common Consequences:
Scope: Confidentiality. Impact: Read Application Data.
Detection Methods:
Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instan
2005-07-06
Published