The Style parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the Style 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.
Issue background
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 defence is to double up any single quotation marks appearing within user input before incorporating that input into a SQL query. This defence 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 defence 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 defence to be bypassed.
Another often cited defence 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.
Request 1
GET /ard/stylesheet/onestyle.asp?AID=1825&Style=eNEWSTitle%2CeNEWSItemRow%2CeNEWSBody%2CeNEWSHeading%2CeNEWSHeading%3Ahover%2CeNEWSTitle%3Ahover' HTTP/1.1 Host: www.simonandco.net Proxy-Connection: keep-alive Referer: http://www.simonandco.net/ard/rss/summary.asp?AID=1825 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept: text/css,*/*;q=0.1 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: ASPSESSIONIDSQQTBQCR=BCJGDPAAKCIFAFNOHKEBEKFE
If the HttpOnly attribute is set on a cookie, then the cookie's value cannot be read or set by client-side JavaScript. This measure can prevent certain client-side attacks, such as cross-site scripting, from trivially capturing the cookie's value via an injected script.
Issue remediation
There is usually no good reason not to set the HttpOnly flag on all cookies. Unless you specifically require legitimate client-side scripts within your application to read or set a cookie's value, you should set the HttpOnly flag by including this attribute within the relevant Set-cookie directive.
You should be aware that the restrictions imposed by the HttpOnly flag can potentially be circumvented in some circumstances, and that numerous other serious attacks can be delivered by client-side script injection, aside from simple cookie stealing.
The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /ard/rhcl.asp?AID=1825&Source=http%3A//www.simonandco.net/ HTTP/1.1 Host: www.simonandco.net Proxy-Connection: keep-alive Referer: http://www.simonandco.net/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Menu</title> <meta name="vs_defaultClientScript" content="JavaScript"> <meta name="vs_targetSchema" co ...[SNIP]...
The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /ard/rss/summary.asp?AID=1825 HTTP/1.1 Host: www.simonandco.net Proxy-Connection: keep-alive Referer: http://www.simonandco.net/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 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
The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.
When a web browser makes a request for a resource, it typically adds an HTTP header, called the "Referer" header, indicating the URL of the resource from which the request originated. This occurs in numerous situations, for example when a web page loads an image or script, or when a user clicks on a link or submits a form.
If the resource being requested resides on a different domain, then the Referer header is still generally included in the cross-domain request. If the originating URL contains any sensitive information within its query string, such as a session token, then this information will be transmitted to the other domain. If the other domain is not fully trusted by the application, then this may lead to a security compromise.
You should review the contents of the information being transmitted to other domains, and also determine whether those domains are fully trusted by the originating application.
Today's browsers may withhold the Referer header in some situations (for example, when loading a non-HTTPS resource from a page that was loaded over HTTPS, or when a Refresh directive is issued), but this behaviour should not be relied upon to protect the originating URL from disclosure.
Note also that if users can author content within the application then an attacker may be able to inject links referring to a domain they control in order to capture data from URLs used within the application.
Issue remediation
The application should never transmit any sensitive information within the URL query string. In addition to being leaked in the Referer header, such information may be logged in various locations and may be visible on-screen to untrusted parties.
The response contains the following links to other domains:
http://service.click4text.co.uk/
http://www.clt-totalsolution.co.uk/
Request
GET /ard/comment.asp?AID=1825 HTTP/1.1 Host: www.simonandco.net Proxy-Connection: keep-alive Referer: http://www.simonandco.net/contact.htm User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 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: ASPSESSIONIDSQQTBQCR=BCJGDPAAKCIFAFNOHKEBEKFE
Response
HTTP/1.1 200 OK Date: Sat, 16 Apr 2011 00:03:16 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Length: 7881 Content-Type: text/html Cache-control: private
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html> <head> <title>Ask us a Question - Simon & Co, UK</title> <meta name="description" content="Ask us a Question - Simon & ...[SNIP]... <cftcloak><a href="http://service.click4text.co.uk" accesskey="T" title="Text Only">Text Only</a> ...[SNIP]... <p class="small" align="center"><a href="http://www.clt-totalsolution.co.uk/" target="_blank" class="small" title="CLT totalSOLUTION is the complete website solution for solicitors and law firms.">powered by <b> ...[SNIP]...
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>RSS News Feed</title> <meta name="vs_defaultClientScript" content="JavaScript"> <meta name="vs_targetS ...[SNIP]... <marquee width="100%" loop=Infinite scrolldelay=150><a href='http://feedproxy.google.com/~r/Reuters/UKWorldNews/~3/YIRokZgtVYo/uk-libya-idUKLDE71Q0MP20110415' target=_blank class='eNEWSTitle'>Obama says Libya in stalemate, but "Gaddafi will go"</a> <a href='http://feedproxy.google.com/~r/Reuters/UKWorldNews/~3/iSjgCUTSCPo/uk-syria-idUKTRE73E33220110415' target=_blank class='eNEWSTitle'>Syria protests reach capital, Yemen leader seeks talks</a> <a href='http://feedproxy.google.com/~r/Reuters/UKWorldNews/~3/V0cLGcgEeDE/uk-algeria-bouteflika-speech-idUKTRE73E7RI20110415' target=_blank class='eNEWSTitle'>Algeria president to launch major political reforms</a> <a href='http://feedproxy.google.com/~r/Reuters/UKWorldNews/~3/13KWG7WlVwo/uk-japan-nuclear-workers-idUKTRE73E5EX20110415' target=_blank class='eNEWSTitle'>Japan says 28 plant workers got high radiation doses</a> <a href='http://feedproxy.google.com/~r/Reuters/UKWorldNews/~3/mQ7yjTzfjj0/uk-egypt-mubarak-idUKTRE73E5FG20110415' target=_blank class='eNEWSTitle'>Mubarak to be moved to Egypt army hospital in days</a> <a href='http://feedproxy.google.com/~r/Reuters/UKWorldNews/~3/qCOvM7gRTIw/uk-ivorycoast-un-idUKTRE73E7I220110415' target=_blank class='eNEWSTitle'>U.N. says Ivory Coast's Gbagbo has been well treated</a> <a href='http://feedproxy.google.com/~r/Reuters/UKWorldNews/~3/4qXW0Rj6O7o/uk-warcrimes-gotovina-idUKTRE73E2B920110415' target=_blank class='eNEWSTitle'>Warcrimes court jails ex-Croatian general for 24 years</a> <a href='http://feedproxy.google.com/~r/Reuters/UKWorldNews/~3/vD82WGOmqZE/uk-yemen-idUKTRE73D45120110415' target=_blank class='eNEWSTitle'>Yemen's Saleh calls for talks as protests escalate</a> <a href='http://feedproxy.google.com/~r/Reuters/UKWorldNews/~3/QDf87OXxWEk/uk-palestinians-italy-kidnap-idUKTRE73E00H20110415' target=_blank class='eNEWSTitle'>Qaeda sympathisers kill abducted Italian activist</a> <a href='http://feedproxy.google.com/~r/Reuters/UKWorldNews/~3/h2yZmchz5MM/uk-ivorycoast-idUKTRE73D50R20110415' target=_blank class='eNEWSTitle'>U.N. defends role in Ivory Coast Gbagbo ouster</a> ...[SNIP]...
4. Email addresses disclosedpreviousnext There are 3 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).
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html><!-- InstanceBegin template="/Templates/main.dwt" codeOutsideHTMLIsLocked="false" --> <head> <meta http-equiv="Content-Type" co ...[SNIP]... <a href="mailto:info@simonandco.net">info@simonandco.net</a> ...[SNIP]...
The following email address was disclosed in the response:
info@simonandco.net
Request
GET /ard/comment.asp?AID=1825 HTTP/1.1 Host: www.simonandco.net Proxy-Connection: keep-alive Referer: http://www.simonandco.net/contact.htm User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 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: ASPSESSIONIDSQQTBQCR=BCJGDPAAKCIFAFNOHKEBEKFE
Response
HTTP/1.1 200 OK Date: Sat, 16 Apr 2011 00:03:16 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Length: 7881 Content-Type: text/html Cache-control: private
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html> <head> <title>Ask us a Question - Simon & Co, UK</title> <meta name="description" content="Ask us a Question - Simon & ...[SNIP]... <a href="mailto:info@simonandco.net">info@simonandco.net</a> ...[SNIP]...
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.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Menu</title> <meta name="vs_defaultClientScript" content="JavaScript"> <meta name="vs_targetSchema" co ...[SNIP]...
GET /favicon.ico HTTP/1.1 Host: www.simonandco.net Proxy-Connection: keep-alive Accept: */* User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 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: ASPSESSIONIDSQQTBQCR=BCJGDPAAKCIFAFNOHKEBEKFE
Response
HTTP/1.1 404 Not Found Date: Fri, 15 Apr 2011 22:11:59 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Length: 2330 Content-Type: text/html Cache-control: private
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <HEAD> <META NAME="ROBOTS" CONTENT="NOARCHIVE"> <title>404 - Site Error</title> <meta name="robots" content="noindex ...[SNIP]...
Report generated by XSS.CX at Sat Apr 16 07:42:18 CDT 2011.