CVE-2002-0112
published 2002-03-25CVE-2002-0112: Etype Eserv 2.97 allows remote attackers to view password protected files via /./ in the URL.
PriorityP433medium5CVSS 2.0
AVNACLAuNCPINAN
EXPLOIT
EPSS
8.13%
94.1th percentile
Etype Eserv 2.97 allows remote attackers to view password protected files via /./ in the URL.
Affected
7 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| etype | eserv | — | — |
| etype | eserv | — | — |
| etype | eserv | — | — |
| etype | eserv | — | — |
| etype | eserv | — | — |
| etype | eserv | — | — |
| etype | eserv | — | — |
CVEs like this are exactly what “Exploited This Week” covers.
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 writeups or analysis indexed.
CWE
Path Equivalence: '/./' (Single Dot Directory)
mitre_cwe·CVSS 5.0
[MEDIUM] CWE-55 Path Equivalence: '/./' (Single Dot Directory)
CWE-55: Path Equivalence: '/./' (Single Dot Directory)
The product accepts path input in the form of single dot directory exploit ('/./') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Confidentiality, Integrity. Impact: Read Files or Directories, Modify Files or Directories.
Potential Mitigations:
[Implementation] Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by
CWE
Improper Resolution of Path Equivalence
mitre_cwe
CWE-41 Improper Resolution of Path Equivalence
CWE-41: Improper Resolution of Path Equivalence
The product is vulnerable to file system contents disclosure through path equivalence. Path equivalence involves the use of special characters in file and directory names. The associated manipulations are intended to generate multiple names for the same object.
Path equivalence is usually employed in order to circumvent access controls expressed using an incomplete set of file name or file path representations. This is different from path traversal, wherein the manipulations are performed to generate a name for a different object.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Confidentiality, Integrity, Access Control. Impact: Read Files or Directories, Modify Files or Directories, Bypass Protection Mechanism. A
http://archives.neohapsis.com/archives/vulnwatch/2002-q1/0010.htmlhttp://marc.info/?l=bugtraq&m=101062172226812&w=2http://marc.info/?l=ntbugtraq&m=101062823505486&w=2http://online.securityfocus.com/archive/1/249734http://www.iss.net/security_center/static/7849.phphttp://www.securityfocus.com/bid/3838http://archives.neohapsis.com/archives/vulnwatch/2002-q1/0010.htmlhttp://marc.info/?l=bugtraq&m=101062172226812&w=2http://marc.info/?l=ntbugtraq&m=101062823505486&w=2http://online.securityfocus.com/archive/1/249734http://www.iss.net/security_center/static/7849.phphttp://www.securityfocus.com/bid/3838
2002-03-25
Published