CVE-2003-1365
Summary
| CVE | CVE-2003-1365 |
|---|---|
| State | PUBLISHED |
| Assigner | mitre |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2003-12-31 05:00:00 UTC |
| Updated | 2025-04-03 01:03:51 UTC |
| Description | The escape_dangerous_chars function in CGI::Lite 2.0 and earlier does not correctly remove special characters including (1) "\" (backslash), (2) "?", (3) "~" (tilde), (4) "^" (carat), (5) newline, or (6) carriage return, which could allow remote attackers to read or write arbitrary files, or execute arbitrary commands, in shell scripts that rely on CGI::Lite to filter such dangerous inputs. |
Risk And Classification
CVSS v2.0 Breakdown
Access Vector
NetworkAccess Complexity
LowAuthentication
NoneConfidentiality
NoneIntegrity
PartialAvailability
NoneAV:N/AC:L/Au:N/C:N/I:P/A:N
NVD Known Affected Configurations (CPE 2.3)
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Security bug in CGI::Lite::escape_dangerous_chars() function - CXSecurity.com | af854a3a-2127-422b-91ae-364da2661108 | securityreason.com | |
| CGI Lite Perl Module Metacharacter Input Validation Vulnerability | af854a3a-2127-422b-91ae-364da2661108 | www.securityfocus.com | |
| Neohapsis Archives - VulnWatch - [VulnWatch] Security bug in CGI::Lite::escape_dangerous_chars() function - From rfg_at_monkeys.com | af854a3a-2127-422b-91ae-364da2661108 | archives.neohapsis.com | Exploit |
| search.cpan.org: CGI::Lite - Process and decode WWW forms and cookies | af854a3a-2127-422b-91ae-364da2661108 | search.cpan.org | Exploit |
| IBM X-Force Exchange | af854a3a-2127-422b-91ae-364da2661108 | exchange.xforce.ibmcloud.com | |
| Journal of cbrooks (3267) | af854a3a-2127-422b-91ae-364da2661108 | use.perl.org | |
| SecurityFocus HOME Mailing List: BugTraq | af854a3a-2127-422b-91ae-364da2661108 | www.securityfocus.com | Exploit |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.