1 / 18

How Did I Steal Your Database

How Did I Steal Your Database. Mostafa Siraj. @mostafasiraj. Agenda. Noooo, it kills suspense. DISCLAIMER. Hacking websites is ILLEGAL This presentation is meant for educational purposes ONLY Only use this stuff on YOUR website and YOUR account. SQL Injection. What is it?

elu
Download Presentation

How Did I Steal Your Database

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. How Did I Steal Your Database Mostafa Siraj @mostafasiraj

  2. Agenda Noooo, it kills suspense

  3. DISCLAIMER • Hacking websites is ILLEGAL • This presentation is meant for educational purposes ONLY • Only use this stuff on YOUR website and YOUR account

  4. SQL Injection What is it? The application dynamically generates an SQL query based on user input, but it does not sufficiently prevent that input from modifying the intended structure of the query.

  5. SQL Injection Example, Bypassing Logon • Original SQL Query • String sqlQuery = "SELECT * FROM user WHERE name = '" + username +"' AND • pass='" + password + "'“ • ….. • Setting username to Mostafa & password to ' OR '1'= '1 produces • SELECT * FROM user WHERE name = 'Mostafa' AND pass='' OR '1'='1' • Attacker is logged on without Authentication

  6. Not only your web app and DB are at risk • Depending on the DB, an attacker can access the operating system • MS SQL Server: Execute OS command xp_cmdshell • Set username to '; exec master.dbo.xp_cmdshell "dir";-- produces • SELECT * FROM user WHERE • name=''; exec master.dbo.xp_cmdshell "dir"; -- • Note: dir list directory content

  7. Let's play Hide and Seek • Original: SELECT * FROM user WHERE name=''; exec master.dbo.xp_cmdshell "dir"; -- • Defender: Disallow double quotes: • Attacker: SELECT * FROM user WHERE name=''; exec master.dbo.xp_cmdshell dir; -- • Defender: Filter out string “xp_cmdshell” • Attacker: ';declare @a varchar(1000); set @a = 'master.dbo.xp_' + 'cmdshell dir'; exec (@a);-- • Defender: Filter out “xp”, “cmd”, “shell”, …. • Attacker: ';declare @a varchar(1000); set @a = reverse('rid llehsdmc_px.obd.retsam'); exec (@a);--

  8. Finding SQL Injection Bugs

  9. Finding SQL Injection Bugs • Submit single quotation mark and observe the result • Submit two single quotation and observe the result • Identify the database (e.g. • Oracle: ‘||’FOO • MS-SQL: ‘+’FOO • MySQL: ‘ ‘FOO [note the space btw the 2 quotes]

  10. Finding SQL Injection Bugs • For multistate processes, complete all the states before observing the results • For search fields try using the wildcard character %

  11. Finding SQL Injection Bugs • For numeric data, if the original value was 2 try submitting • 1+1 or 3-1 • If successful try using SQL-specific keywords, e.g. • 67-ASCII(‘A’) • If single quotes are filtered try • 51-ASCII(1) [note ASCII(1)=49]

  12. Inject into different statement types • You can do the same for all SQL statements (INSERT, UPDATE or DELETE) • Watch out when injecting in UPDATE or DELETE

  13. Demo WebGoat

  14. Demo HacmeBank

  15. Demo Using UNION Operator

  16. Demo MS-SQL Error

  17. Solution • Validate the input -accept only known good- • Process SQL queries using prepared statements, parameterized queries, or stored procedures. • Enforce least privilege • Avoid detailed error messages • Show care when using stored procedures (e.g. exec)

  18. Thank You @mostafasiraj

More Related