WebApp Sec mailing list archives
Re: SQL Injection
From: "Steven M. Christey" <coley () mitre org>
Date: Tue, 8 Jun 2004 17:52:15 -0400 (EDT)
BTW, any opinions on if I just encode all input without checking for any characters? Say converting all <script> to <script> Can anyone still do XSS or SQL Injection in that case?
Not that I can think of, but there might be implications if there's a back end. However... If the routine is being coded in C or another language that's prone to buffer overflows, then you need to make sure to account for all the potential quoting when allocating the memory to hold the resulting string. "Transformation-based" buffer overflows (my hastily coined term) are starting to become more common. If the transformation converts a double-quote character to a ""e;", then an attacker could expand the original string by a factor of 6, which could have implications for the application itself *or* the back end. - Steve
Current thread:
- Re: SQL Injection, (continued)
- Re: SQL Injection David Cameron (Jun 02)
- RE: SQL Injection Imperva Application Defense Center (Jun 02)
- RE: SQL Injection stevenr (Jun 02)
- Re: SQL Injection Steven M. Christey (Jun 03)
- Re: SQL Injection The Crocodile (Jun 04)
- RE: SQL Injection stevenr (Jun 06)
- RE: SQL Injection The Crocodile (Jun 06)
- Re: SQL Injection Jeff Williams (Jun 08)
- Re: SQL Injection saphyr (Jun 09)
- RE: SQL Injection The Crocodile (Jun 06)
- Request for comments - French readers saphyr (Jun 08)
- Re: SQL Injection Steven M. Christey (Jun 08)
- RE: SQL Injection Michael Howard (Jun 09)
- RE: SQL Injection or XML gcb33 (Jun 09)
- RE: SQL Injection Michael Howard (Jun 09)
- RE: SQL Injection Michael Silk (Jun 09)
- RE: SQL Injection WebAppSecurity [Technicalinfo.net] (Jun 10)
- RE: SQL Injection stevenr (Jun 09)
- RE: SQL Injection Michael Silk (Jun 09)
- RE: SQL Injection V. Poddubniy (Jun 10)
- encryption over the web OPTUSBYS (Jun 14)
- Re: encryption over the web Sam (Jun 14)
- encryption over the web OPTUSBYS (Jun 14)