CVE-2004-0280
published 2004-11-23CVE-2004-0280: Caucho Technology Resin 2.1.12 allows remote attackers to view JSP source via an HTTP request to a .jsp file that ends in a "%20" (encoded space character)…
PriorityP419medium5CVSS 2.0
AVNACLAuNCPINAN
EPSS
1.53%
71.6th percentile
Caucho Technology Resin 2.1.12 allows remote attackers to view JSP source via an HTTP request to a .jsp file that ends in a "%20" (encoded space character), e.g. index.jsp%20.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| caucho_technology | resin | — | — |
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
Improper Handling of URL Encoding (Hex Encoding)
mitre_cwe·CVSS 7.5
[HIGH] CWE-177 Improper Handling of URL Encoding (Hex Encoding)
CWE-177: Improper Handling of URL Encoding (Hex Encoding)
The product does not properly handle when all or part of an input has been URL encoded.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Integrity. Impact: Unexpected State.
Potential Mitigations:
[Architecture and Design] Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.
[Implementation] Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including le
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
CWE
Path Equivalence: 'filename ' (Trailing Space)
mitre_cwe·CVSS 5.0
[MEDIUM] CWE-46 Path Equivalence: 'filename ' (Trailing Space)
CWE-46: Path Equivalence: 'filename ' (Trailing Space)
The product accepts path input in the form of trailing space ('filedir ') 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.
Observed Examples:
CVE-2001-0693: Source disclosure via trailing encoded space "%20"
CVE-2001-0778: Source disclosure via trailing encoded space "%20"
CVE-2001-1248: Source disclosure via trailing encoded space "%20"
CVE-2004-0280: Source disclosure via trailing encoded space "%20"
CVE-2004-2213: Source disclosure via trail
2004-11-23
Published