CVE-2002-1025
published 2002-10-04CVE-2002-1025: JRun 3.0 through 4.0 allows remote attackers to read JSP source code via an encoded null byte in an HTTP GET request, which causes the server to send the .JSP…
PriorityP416medium5CVSS 2.0
AVNACLAuNCPINAN
EPSS
2.01%
78.4th percentile
JRun 3.0 through 4.0 allows remote attackers to read JSP source code via an encoded null byte in an HTTP GET request, which causes the server to send the .JSP file unparsed.
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| macromedia | jrun | — | — |
| macromedia | jrun | — | — |
| macromedia | jrun | — | — |
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 Neutralization of Null Byte or NUL Character
mitre_cwe
CWE-158 Improper Neutralization of Null Byte or NUL Character
CWE-158: Improper Neutralization of Null Byte or NUL Character
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes NUL characters or null bytes when they are sent to a downstream component.
As data is parsed, an injected NUL character or null byte may cause the product to believe the input is terminated earlier than it actually is, or otherwise cause the input to be misinterpreted. This could then be used to inject potentially dangerous input that occurs after the null byte or otherwise bypass validation routines and other protection mechanisms.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Integrity. Impact: Unexpected State.
Potential Mitigations:
Developers should anticipate that null characters or
http://archives.neohapsis.com/archives/vulnwatch/2002-q2/0138.htmlhttp://online.securityfocus.com/archive/1/280062http://www.iss.net/security_center/static/9459.phphttp://www.macromedia.com/v1/handlers/index.cfm?ID=23164http://www.osvdb.org/5028http://www.securityfocus.com/bid/5134http://archives.neohapsis.com/archives/vulnwatch/2002-q2/0138.htmlhttp://online.securityfocus.com/archive/1/280062http://www.iss.net/security_center/static/9459.phphttp://www.macromedia.com/v1/handlers/index.cfm?ID=23164http://www.osvdb.org/5028http://www.securityfocus.com/bid/5134
2002-10-04
Published