The Pos parameter appears to be vulnerable to LDAP injection attacks.
The payloads f15a9610b11188dc)(sn=* and f15a9610b11188dc)!(sn=* were each submitted in the Pos 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.
Request 1
GET /BurstingPipe/BannerSource.asp?FlightID=1845278&Page=&PluID=0&Pos=f15a9610b11188dc)(sn=* HTTP/1.1 Host: bs.serving-sys.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: U=bc24f152-c049-433d-b700-d0e64725117e3F803g; A2=ewqR9KRX02WG0000a2wErH; eyeblaster=BWVal=&BWDate=&debuglevel=&FLV=10.1102&RES=128&WMPV=0; B2=72wu0a2wErH; u2=bc24f152-c049-433d-b700-d0e64725117e3F803g; E2=02WGa2wErH; C3=0ujua2wErH0000001_; u3=1; D3=0uju00Z3a2wErH;
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.
The value of the eyeblaster cookie is copied into the Set-Cookie response header. The payload ee0e5%0d%0a3b4b745c958 was submitted in the eyeblaster cookie. This caused a response containing an injected HTTP header.
Request
GET /BurstingPipe/BannerRedirect.asp HTTP/1.1 Host: bs.serving-sys.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: U=bc24f152-c049-433d-b700-d0e64725117e3F803g; A2=ewqR9KRX02WG0000a2wErH; eyeblaster=BWVal=&BWDate=&debuglevel=&FLV=10.1102&RES=128&WMPV=0ee0e5%0d%0a3b4b745c958; B2=72wu0a2wErH; u2=bc24f152-c049-433d-b700-d0e64725117e3F803g; E2=02WGa2wErH; C3=0ujua2wErH0000001_; u3=1; D3=0uju00Z3a2wErH;
The value of the rtu request parameter is copied into the Location response header. The payload b60f3%0d%0aef0067e8470 was submitted in the rtu parameter. This caused a response containing an injected HTTP header.
The value of the Pos request parameter is copied into the Set-Cookie response header. The payload c3ded%0d%0a061668c0d26 was submitted in the Pos parameter. This caused a response containing an injected HTTP header.
Request
GET /BurstingPipe/BannerSource.asp?FlightID=1845278&Page=&PluID=0&Pos=c3ded%0d%0a061668c0d26 HTTP/1.1 Host: bs.serving-sys.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: U=bc24f152-c049-433d-b700-d0e64725117e3F803g; A2=ewqR9KRX02WG0000a2wErH; eyeblaster=BWVal=&BWDate=&debuglevel=&FLV=10.1102&RES=128&WMPV=0; B2=72wu0a2wErH; u2=bc24f152-c049-433d-b700-d0e64725117e3F803g; E2=02WGa2wErH; C3=0ujua2wErH0000001_; u3=1; D3=0uju00Z3a2wErH;
The value of the eyeblaster cookie is copied into the Set-Cookie response header. The payload d61b4%0d%0ae9c46d450 was submitted in the eyeblaster cookie. This caused a response containing an injected HTTP header.
Request
GET /BurstingPipe/BannerSource.asp HTTP/1.1 Host: bs.serving-sys.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: U=bc24f152-c049-433d-b700-d0e64725117e3F803g; A2=ewqR9KRX02WG0000a2wErH; eyeblaster=BWVal=&BWDate=&debuglevel=&FLV=10.1102&RES=128&WMPV=0d61b4%0d%0ae9c46d450; B2=72wu0a2wErH; u2=bc24f152-c049-433d-b700-d0e64725117e3F803g; E2=02WGa2wErH; C3=0ujua2wErH0000001_; u3=1; D3=0uju00Z3a2wErH;
The value of the eyeblaster cookie is copied into the Set-Cookie response header. The payload 5b643%0d%0abe53509c9b2 was submitted in the eyeblaster cookie. This caused a response containing an injected HTTP header.
Request
GET /BurstingPipe/BurstingInteractionsPipe.asp HTTP/1.1 Host: bs.serving-sys.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: U=bc24f152-c049-433d-b700-d0e64725117e3F803g; A2=ewqR9KRX02WG0000a2wErH; eyeblaster=BWVal=&BWDate=&debuglevel=&FLV=10.1102&RES=128&WMPV=05b643%0d%0abe53509c9b2; B2=72wu0a2wErH; u2=bc24f152-c049-433d-b700-d0e64725117e3F803g; E2=02WGa2wErH; C3=0ujua2wErH0000001_; u3=1; D3=0uju00Z3a2wErH;
The value of the flv request parameter is copied into the Set-Cookie response header. The payload 14044%0d%0a1c3e7027c8c was submitted in the flv parameter. This caused a response containing an injected HTTP header.
The value of the res request parameter is copied into the Set-Cookie response header. The payload f230f%0d%0a9649663b7fd was submitted in the res parameter. This caused a response containing an injected HTTP header.
The value of the wmpv request parameter is copied into the Set-Cookie response header. The payload 430ae%0d%0a4dd012c671c was submitted in the wmpv parameter. This caused a response containing an injected HTTP header.
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 the h request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload e9027%3balert(1)//a4a47d04ec4 was submitted in the h parameter. This input was echoed as e9027;alert(1)//a4a47d04ec4 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
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.
The value of the w request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload 11b37%3balert(1)//b7af2428148 was submitted in the w parameter. This input was echoed as 11b37;alert(1)//b7af2428148 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
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.
The application publishes a Flash cross-domain policy which allows access from any domain.
Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.
Issue background
The Flash cross-domain policy controls whether Flash client components running on other domains can perform two-way interaction with the domain which publishes the policy. If another domain is allowed by the policy, then that domain can potentially attack users of the application. If a user is logged in to the application, and visits a domain allowed by the policy, then any malicious content running on that domain can potentially gain full access to the application within the security context of the logged in user.
Even if an allowed domain is not overtly malicious in itself, security vulnerabilities within that domain could potentially be leveraged by a third-party attacker to exploit the trust relationship and attack the application which allows access.
Issue remediation
You should review the domains which are allowed by the Flash cross-domain policy and determine whether it is appropriate for the application to fully trust both the intentions and security posture of those domains.
Request
GET /crossdomain.xml HTTP/1.0 Host: bs.serving-sys.com
Response
HTTP/1.1 200 OK Content-Length: 100 Content-Type: text/xml Last-Modified: Thu, 21 Aug 2008 15:23:00 GMT Accept-Ranges: bytes ETag: "0e2c3cba13c91:b0d" P3P: policyref=http://www.eyeblaster.com/p3p/Eyeblaster-served-p3p2.xml,CP="NOI DEVa OUR BUS UNI" X-Powered-By: ASP.NET Connection: close
A cookie's domain attribute determines which domains can access the cookie. Browsers will automatically submit the cookie in requests to in-scope domains, and those domains will also be able to access the cookie via JavaScript. If a cookie is scoped to a parent domain, then that cookie will be accessible by the parent domain and also by any other subdomains of the parent domain. If the cookie contains sensitive data (such as a session token) then this data may be accessible by less trusted or less secure applications residing at those domains, leading to a security compromise.
Issue remediation
By default, cookies are scoped to the issuing domain and all subdomains. If you remove the explicit domain attribute from your Set-cookie directive, then the cookie will have this default scope, which is safe and appropriate in most situations. If you particularly need a cookie to be accessible by a parent domain, then you should thoroughly review the security of the applications residing on that domain and its subdomains, and confirm that you are willing to trust the people and systems which support those applications.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /BurstingPipe/BannerSource.asp?FlightID=1845278&Page=&PluID=0&Pos=2841 HTTP/1.1 Host: bs.serving-sys.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: U=bc24f152-c049-433d-b700-d0e64725117e3F803g; A2=ewqR9KRX02WG0000a2wErH; eyeblaster=BWVal=&BWDate=&debuglevel=&FLV=10.1102&RES=128&WMPV=0; B2=72wu0a2wErH; u2=bc24f152-c049-433d-b700-d0e64725117e3F803g; E2=02WGa2wErH; C3=0ujua2wErH0000001_; u3=1; D3=0uju00Z3a2wErH;
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
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 cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /BurstingPipe/BannerRedirect.asp?FlightID=1845278&Page=&PluID=0&Pos=2841 HTTP/1.1 Host: bs.serving-sys.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: U=bc24f152-c049-433d-b700-d0e64725117e3F803g; A2=ewqR9KRX02WG0000a2wErH; eyeblaster=BWVal=&BWDate=&debuglevel=&FLV=10.1102&RES=128&WMPV=0; B2=72wu0a2wErH; u2=bc24f152-c049-433d-b700-d0e64725117e3F803g; E2=02WGa2wErH; C3=0ujua2wErH0000001_; u3=1; D3=0uju00Z3a2wErH;
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /BurstingPipe/BannerRedirect.asp HTTP/1.1 Host: bs.serving-sys.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: U=bc24f152-c049-433d-b700-d0e64725117e3F803g; A2=ewqR9KRX02WG0000a2wErH; eyeblaster=BWVal=&BWDate=&debuglevel=&FLV=10.1102&RES=128&WMPV=0; B2=72wu0a2wErH; u2=bc24f152-c049-433d-b700-d0e64725117e3F803g; E2=02WGa2wErH; C3=0ujua2wErH0000001_; u3=1; D3=0uju00Z3a2wErH;
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /BurstingPipe/BannerSource.asp HTTP/1.1 Host: bs.serving-sys.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: U=bc24f152-c049-433d-b700-d0e64725117e3F803g; A2=ewqR9KRX02WG0000a2wErH; eyeblaster=BWVal=&BWDate=&debuglevel=&FLV=10.1102&RES=128&WMPV=0; B2=72wu0a2wErH; u2=bc24f152-c049-433d-b700-d0e64725117e3F803g; E2=02WGa2wErH; C3=0ujua2wErH0000001_; u3=1; D3=0uju00Z3a2wErH;
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /BurstingPipe/BannerSource.asp?FlightID=1845278&Page=&PluID=0&Pos=2841 HTTP/1.1 Host: bs.serving-sys.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: U=bc24f152-c049-433d-b700-d0e64725117e3F803g; A2=ewqR9KRX02WG0000a2wErH; eyeblaster=BWVal=&BWDate=&debuglevel=&FLV=10.1102&RES=128&WMPV=0; B2=72wu0a2wErH; u2=bc24f152-c049-433d-b700-d0e64725117e3F803g; E2=02WGa2wErH; C3=0ujua2wErH0000001_; u3=1; D3=0uju00Z3a2wErH;
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The file robots.txt is used to give instructions to web robots, such as search engine crawlers, about locations within the web site which robots are allowed, or not allowed, to crawl and index.
The presence of the robots.txt does not in itself present any kind of security vulnerability. However, it is often used to identify restricted or private areas of a site's contents. The information in the file may therefore help an attacker to map out the site's contents, especially if some of the locations identified are not linked from elsewhere in the site. If the application relies on robots.txt to protect access to these areas, and does not enforce proper access control over them, then this presents a serious vulnerability.
Issue remediation
The robots.txt file is not itself a security threat, and its correct use can represent good practice for non-security reasons. You should not assume that all web robots will honour the file's instructions. Rather, assume that attackers will pay close attention to any locations identified in the file. Do not rely on robots.txt to provide any kind of protection over unauthorised access.
Request
GET /robots.txt HTTP/1.0 Host: bs.serving-sys.com
Response
HTTP/1.1 200 OK Content-Length: 28 Content-Type: text/plain Last-Modified: Mon, 16 Jan 2006 20:19:44 GMT Accept-Ranges: bytes ETag: "0b02b30da1ac61:761" P3P: policyref=http://www.eyeblaster.com/p3p/Eyeblaster-served-p3p2.xml,CP="NOI DEVa OUR BUS UNI" X-Powered-By: ASP.NET Connection: close
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.
The response contains the following Content-type statement:
Content-Type: text/html
The response states that it contains HTML. However, it actually appears to contain script.
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.