In view of the fact that this error pops up in so many systems I take over, I have often gone down the wrong path following the red herring as it were when in fact the answer to this is very common.

Bespoke systems are the usual suspects. Developers will have told the system what to do when newline, carriage returns and tab characters are entered in the data. Those who are security-conscious will also make their system escape apostrophes (') and double-quotes ("). But who can honestly build a system that thinks of everything from day one?

Check all required values to escape have been escaped. In all my cases this has been the percent sign (%) but I'm listing what needs to be escaped in SQL for future use:

Character   Description
\0An ASCII NUL (0x00) character.
\'A single quote (“'”) character.
\"A double quote (“"”) character.
\bA backspace character.
\nA newline (linefeed) character.
\rA carriage return character.
\tA tab character.
\ZASCII 26 (Control+Z).
\\A backslash (“\”) character.
\%A “%” character.
\_A “_” character.

An alternative in SQL to escape apostrophes is to change these to paired apostrophes, so:
  1.  INSERT INTO myTable VALUES ('1', 'It\'s amazing!'); 
  3.  -- equally valid 
  4.  INSERT INTO myTable VALUES ('1', 'It''s amazing!'); 
Bear this in mind when you're implementing anti-injection security features.

Add comment