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.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Link | Tags |
---|---|
http://use.perl.org/~cbrooks/journal/10542 | |
http://www.securityfocus.com/archive/1/311414 | exploit mailing list |
http://www.securityfocus.com/bid/6833 | vdb entry |
http://securityreason.com/securityalert/3237 | third party advisory |
https://exchange.xforce.ibmcloud.com/vulnerabilities/11308 | vdb entry |
http://search.cpan.org/~smylers/CGI-Lite-2.02/Lite.pm | exploit |
http://archives.neohapsis.com/archives/vulnwatch/2003-q1/0065.html | exploit mailing list |