× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. October 2009

RE: SQL Problem

-----Message d'origine-----
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de Brian Piotrowski

An injection attack occurs when you embed additional SQL
commands into an external SQL statement. Taking Charles'
example, if you have:

wSQL = 'select * from XYZ where fld2 = ' + QUOTE +
inFld2Value + QUOTE;

An injection attack could occur by adding additional commands
within the inFld2Value parameter. So if inFld2Value had a
value of "a';DROP TABLE users; select * from users where
t='", it would have the potential to not find anything in the
first statement and then attempt to drop a table named users
and then attempt to query the users table.


But what happens here :
wSQL = 'select * from XYZ where fld2 = ?';
/exec SQL prepare C1 from :wSQL;
/exec SQL open C1 using :inFld2Value;

when inFld2Value had a value of "a';DROP TABLE users;select * from users where t='" ?

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.