The SessionId parameter appears to be vulnerable to LDAP injection attacks.
The payloads 9b2a2af292dc6160)(sn=* and 9b2a2af292dc6160)!(sn=* were each submitted in the SessionId parameter. These two requests resulted in different responses, indicating that the input may be being incorporated into a disjunctive LDAP query in an unsafe manner.
Issue background
LDAP injection arises when user-controllable data is copied in an unsafe way into an LDAP query that is performed by the application. If an attacker can inject LDAP metacharacters into the query, then they can interfere with the query's logic. Depending on the function for which the query is used, the attacker may be able to retrieve sensitive data to which they are not authorised, or subvert the application's logic to perform some unauthorised action.
Note that automated difference-based tests for LDAP 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.
Issue remediation
If possible, applications should avoid copying user-controllable data into LDAP queries. If this is unavoidable, then the data should be strictly validated to prevent LDAP injection attacks. In most situations, it will be appropriate to allow only short alphanumeric strings to be copied into queries, and any other input should be rejected. At a minimum, input containing any LDAP metacharacters should be rejected; characters that should be blocked include ( ) ; , * | & = and whitespace.
The name of an arbitrarily supplied request parameter is copied into the Location response header. The payload 5af73%0d%0a73a34eff1a3 was submitted in the name of an arbitrarily supplied request parameter. This caused a response containing an injected HTTP header.
Issue background
HTTP header injection vulnerabilities arise when user-supplied data is copied into a response header in an unsafe way. If an attacker can inject newline characters into the header, then they can inject new HTTP headers and also, by injecting an empty line, break out of the headers into the message body and write arbitrary content into the application's response.
Various kinds of attack can be delivered via HTTP header injection vulnerabilities. Any attack that can be delivered via cross-site scripting can usually be delivered via header injection, because the attacker can construct a request which causes arbitrary JavaScript to appear within the response body. Further, it is sometimes possible to leverage header injection vulnerabilities to poison the cache of any proxy server via which users access the application. Here, an attacker sends a crafted request which results in a "split" response containing arbitrary content. If the proxy server can be manipulated to associate the injected response with another URL used within the application, then the attacker can perform a "stored" attack against this URL which will compromise other users who request that URL in future.
Issue remediation
If possible, applications should avoid copying user-controllable data into HTTP response headers. If this is unavoidable, then the data should be strictly validated to prevent header injection attacks. In most situations, it will be appropriate to allow only short alphanumeric strings to be copied into headers, and any other input should be rejected. At a minimum, input containing any characters with ASCII codes less than 0x20 should be rejected.
Request
GET /myaccount/InitialINGDirect.html?command=displayLogin&device=web&locale=en_US&userType=Client&5af73%0d%0a73a34eff1a3=1 HTTP/1.1 Host: secure.ingdirect.com 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.10 (KHTML, like Gecko) Chrome/8.0.552.215 Safari/534.10 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: ING%5FDIRECT%5FUS%5FUserKey=o64%2Eg%2E0urj6h5jn04bxtq26g9ekmmsokka4%7C; op202displayosalandingpagegum=a03p08k0jd26c4l06t42fe019; ING_DIRECT_US_Promo=%99%64%68%74%bb%6c%68; __utma=60842100.731613379.1291523705.1291516564.1292024521.3; __utmc=60842100; __utmz=60842100.1292024521.3.3.utmcsr=Google|utmccn=OSA_Non_Brand|utmcmd=CPC|utmctr=orange%20bank; op202googlegum=a02g05g0bh26caj08f455da91; op202googleliid=a02g05g0bh26caj08f455da91; ING%5FDIRECT%5FUS%5FPromo=%99%8D%92%80%C2stmo; __utmb=60842100
If the secure flag is set on a cookie, then browsers will not submit the cookie in any requests that use an unencrypted HTTP connection, thereby preventing the cookie from being trivially intercepted by an attacker monitoring network traffic. If the secure flag is not set, then the cookie will be transmitted in clear-text if the user visits any HTTP URLs within the cookie's scope. An attacker may be able to induce this event by feeding a user suitable links, either directly or via another web site. Even if the domain which issued the cookie does not host any content that is accessed over HTTP, an attacker may be able to use links of the form http://example.com:443/ to perform the same attack.
Issue remediation
The secure flag should be set on all cookies that are used for transmitting sensitive data when accessing content over HTTPS. If cookies are used to transmit session tokens, then areas of the application that are accessed over HTTPS should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications.
The highlighted cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.
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.
The highlighted cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /myaccount/InitialINGDirect.html?command=displayLogin&device=web&locale=en_US&userType=Client HTTP/1.1 Host: secure.ingdirect.com 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.10 (KHTML, like Gecko) Chrome/8.0.552.215 Safari/534.10 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: ING%5FDIRECT%5FUS%5FUserKey=o64%2Eg%2E0urj6h5jn04bxtq26g9ekmmsokka4%7C; op202displayosalandingpagegum=a03p08k0jd26c4l06t42fe019; ING_DIRECT_US_Promo=%99%64%68%74%bb%6c%68; __utma=60842100.731613379.1291523705.1291516564.1292024521.3; __utmc=60842100; __utmz=60842100.1292024521.3.3.utmcsr=Google|utmccn=OSA_Non_Brand|utmcmd=CPC|utmctr=orange%20bank; op202googlegum=a02g05g0bh26caj08f455da91; op202googleliid=a02g05g0bh26caj08f455da91; ING%5FDIRECT%5FUS%5FPromo=%99%8D%92%80%C2stmo; __utmb=60842100
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 highlighted cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.
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.
The highlighted cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /myaccount/InitialINGDirect.html?command=displayLogin&device=web&locale=en_US&userType=Client HTTP/1.1 Host: secure.ingdirect.com 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.10 (KHTML, like Gecko) Chrome/8.0.552.215 Safari/534.10 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: ING%5FDIRECT%5FUS%5FUserKey=o64%2Eg%2E0urj6h5jn04bxtq26g9ekmmsokka4%7C; op202displayosalandingpagegum=a03p08k0jd26c4l06t42fe019; ING_DIRECT_US_Promo=%99%64%68%74%bb%6c%68; __utma=60842100.731613379.1291523705.1291516564.1292024521.3; __utmc=60842100; __utmz=60842100.1292024521.3.3.utmcsr=Google|utmccn=OSA_Non_Brand|utmcmd=CPC|utmctr=orange%20bank; op202googlegum=a02g05g0bh26caj08f455da91; op202googleliid=a02g05g0bh26caj08f455da91; ING%5FDIRECT%5FUS%5FPromo=%99%8D%92%80%C2stmo; __utmb=60842100
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.
<!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" xml:lang="en" lang="en"> < ...[SNIP]... <!-- Advertiser 'Traffic Buyer - ING Direct', Include user in segment 'ING Direct Login Page' - DO NOT MODIFY THIS PIXEL IN ANY WAY --> <img src="https://ad.yieldmanager.com/pixel?id=239884&t=2" width="1" height="1" /> <!-- End of segment tag --> ...[SNIP]... <NOSCRIPT> <IMG SRC="https://ad.doubleclick.net/activity;src=806653;type=gener917;cat=custo565;ord=1?" WIDTH=1 HEIGHT=1 BORDER=0> </NOSCRIPT> ...[SNIP]...
The response contains the following Content-type statement:
Content-Type: text/html;charset=UTF-8
The response states that it contains HTML. However, it actually appears to contain JSON.
Issue background
If a web response specifies an incorrect content type, then browsers may process the response in unexpected ways. If the specified content type is a renderable text-based format, then the browser will usually attempt to parse and render the response in that format. If the specified type is an image format, then the browser will usually detect the anomaly and will analyse the actual content and attempt to determine its MIME type. Either case can lead to unexpected results, and if the content contains any user-controllable data may lead to cross-site scripting or other client-side vulnerabilities.
In most cases, the presence of an incorrect content type statement 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 a message body, the application should include a single Content-type header which correctly and unambiguously states the MIME type of the content in the response body.
The server presented a valid, trusted SSL certificate. This issue is purely informational.
The server presented the following certificates:
Server certificate
Issued to:
secure.ingdirect.com
Issued by:
VeriSign Class 3 Extended Validation SSL SGC CA
Valid from:
Mon Jul 26 19:00:00 CDT 2010
Valid to:
Wed Jul 27 18:59:59 CDT 2011
Certificate chain #1
Issued to:
VeriSign Class 3 Extended Validation SSL SGC CA
Issued by:
VeriSign Class 3 Public Primary Certification Authority - G5
Valid from:
Tue Nov 07 18:00:00 CST 2006
Valid to:
Mon Nov 07 17:59:59 CST 2016
Certificate chain #2
Issued to:
VeriSign Class 3 Public Primary Certification Authority - G5
Issued by:
Class 3 Public Primary Certification Authority
Valid from:
Tue Nov 07 18:00:00 CST 2006
Valid to:
Sun Nov 07 17:59:59 CST 2021
Certificate chain #3
Issued to:
Class 3 Public Primary Certification Authority
Issued by:
Class 3 Public Primary Certification Authority
Valid from:
Sun Jan 28 18:00:00 CST 1996
Valid to:
Wed Aug 02 18:59:59 CDT 2028
Issue background
SSL helps to protect the confidentiality and integrity of information in transit between the browser and server, and to provide authentication of the server's identity. To serve this purpose, the server must present an SSL certificate which is valid for the server's hostname, is issued by a trusted authority and is valid for the current date. If any one of these requirements is not met, SSL connections to the server will not provide the full protection for which SSL is designed.
It should be noted that various attacks exist against SSL in general, and in the context of HTTPS web connections. It may be possible for a determined and suitably-positioned attacker to compromise SSL connections without user detection even when a valid SSL certificate is used.Report generated by XSS.CX at Fri Dec 10 18:18:59 CST 2010.