The value of the c request parameter is copied into the Location response header. The payload 3690c%0d%0a1a9836ae15c was submitted in the c 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 /ad?c=RhmTmvF0v0C6AZspIIWveWN0Im0fysTH31JY4UqlsUQ8lz18BCOULwciAi30lx5LMPzBmPTAaphQv7AZU9Kg52S6m38Ac8DgUfVTKS3d+ZM=!http://ad.doubleclick.net/jump/N3671.CentroNetwork/B5159652.2;abr=!ie4;abr=!ie5;sz=300x250;pc=[TPAS_ID];ord=2803508621?3690c%0d%0a1a9836ae15c HTTP/1.1 Host: ad.afy11.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: f=AgECAAAAAAALqJELwX83TQyokQsDfjdN; s=1,2*4d2913f5*YxNSVIeEeL*XkHked9a5WVEwm102ii7WMtfCA==*; c=AQEEAAAAAACarxAA-hMpTQAAAAAAAAAAAAAAAAAAAAD1EylNAQABANG4BtXoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACzbLjU6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGXzrQE5fjdNAAAAAAAAAAAAAAAAAAAAAAN+N00CAAIAdaTl1OgAAADlRP3U6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAF+9sdToAAAAD7221OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAkqJXAPN-N00AAAAAAAAAAAAAAAAAAAAAvn83TQEAAgARpOXU6AAAAHWk5dToAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAX72x1OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAxZEByjtDTQAAAAAAAAAAAAAAAAAAAADUO0NNAQABAHVvC9XoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADfTrnU6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==; a=AZ7s9B85IkyRNDgbVDU-vg;
Response
HTTP/1.0 302 Moved Temporarily Connection: close Server: AdifyServer Location: http://ad.doubleclick.net/jump/N3671.CentroNetwork/B5159652.2;abr=!ie4;abr=!ie5;sz=300x250;pc=[TPAS_ID];ord=2803508621?3690c 1a9836ae15c P3P: policyref="http://ad.afy11.net/privacy.xml", CP=" NOI DSP NID ADMa DEVa PSAa PSDa OUR OTRa IND COM NAV STA OTC"
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: ad.afy11.net
Response
HTTP/1.1 200 OK Content-Type: text/xml Last-Modified: Mon, 05 Feb 2007 18:48:56 GMT Accept-Ranges: bytes ETag: "e732374a5649c71:0" Server: Microsoft-IIS/7.5 X-Powered-By: ASP.NET Date: Fri, 28 Jan 2011 16:39:29 GMT Connection: close Content-Length: 201
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Issue background
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.
Request
GET /ad?asId=1000004165407&sd=2x300x250&ct=15&enc=0&nif=0&sf=0&sfd=0&ynw=0&anw=1&rand=86551686&rk1=26330496&rk2=1296251850.357&pt=0 HTTP/1.1 Host: ad.afy11.net Proxy-Connection: keep-alive Referer: http://www.bostonherald.com/includes/processAds.bg?position=Middle2&companion=Top,x14,x15,x16,Middle,Middle1,Middle2,Bottom&page=bh.heraldinteractive.com%2Fhome 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.237 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: a=AZ7s9B85IkyRNDgbVDU-vg; s=1,2*4d2913f5*YxNSVIeEeL*XkHked9a5WVEwm102ii7WMtfCA==*; c=AQEDAAAAAACarxAA-hMpTQAAAAAAAAAAAAAAAAAAAAD1EylNAQABANG4BtXoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACzbLjU6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGXzrQE5fjdNAAAAAAAAAAAAAAAAAAAAAAN+N00CAAIAdaTl1OgAAADlRP3U6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAF+9sdToAAAAD7221OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAkqJXAPN-N00AAAAAAAAAAAAAAAAAAAAAvn83TQEAAgARpOXU6AAAAHWk5dToAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAX72x1OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=; f=AgECAAAAAAALqJELwX83TQyokQsDfjdN
Response
HTTP/1.0 200 OK Connection: close Cache-Control: no-cache, must-revalidate Server: AdifyServer Content-Type: text/html; charset=utf-8 Content-Length: 1767 Set-Cookie: c=AQEEAAAAAACarxAA-hMpTQAAAAAAAAAAAAAAAAAAAAD1EylNAQABANG4BtXoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACzbLjU6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGXzrQE5fjdNAAAAAAAAAAAAAAAAAAAAAAN+N00CAAIAdaTl1OgAAADlRP3U6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAF+9sdToAAAAD7221OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAkqJXAPN-N00AAAAAAAAAAAAAAAAAAAAAvn83TQEAAgARpOXU6AAAAHWk5dToAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAX72x1OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAxZEByjtDTQAAAAAAAAAAAAAAAAAAAADUO0NNAQABAHVvC9XoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADfTrnU6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==; path=/; expires=Sat, 31-Dec-2019 00:00:00 GMT; domain=afy11.net; P3P: policyref="http://ad.afy11.net/privacy.xml", CP=" NOI DSP NID ADMa DEVa PSAa PSDa OUR OTRa IND COM NAV STA OTC"
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.
GET /ad?asId=1000004165407&sd=2x300x250&ct=15&enc=0&nif=0&sf=0&sfd=0&ynw=0&anw=1&rand=38178276&rk1=15197426&rk2=1296251850.36&pt=0 HTTP/1.1 Host: ad.afy11.net Proxy-Connection: keep-alive Referer: http://www.bostonherald.com/includes/processAds.bg?position=Middle1&companion=Top,x14,x15,x16,Middle,Middle1,Middle2,Bottom&page=bh.heraldinteractive.com%2Fhome 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.237 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: a=AZ7s9B85IkyRNDgbVDU-vg; s=1,2*4d2913f5*YxNSVIeEeL*XkHked9a5WVEwm102ii7WMtfCA==*; c=AQEDAAAAAACarxAA-hMpTQAAAAAAAAAAAAAAAAAAAAD1EylNAQABANG4BtXoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACzbLjU6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGXzrQE5fjdNAAAAAAAAAAAAAAAAAAAAAAN+N00CAAIAdaTl1OgAAADlRP3U6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAF+9sdToAAAAD7221OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAkqJXAPN-N00AAAAAAAAAAAAAAAAAAAAAvn83TQEAAgARpOXU6AAAAHWk5dToAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAX72x1OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=; f=AgECAAAAAAALqJELwX83TQyokQsDfjdN
Response
HTTP/1.0 200 OK Connection: close Cache-Control: no-cache, must-revalidate Server: AdifyServer Content-Type: text/html; charset=utf-8 Content-Length: 1767 Set-Cookie: c=AQEEAAAAAACarxAA-hMpTQAAAAAAAAAAAAAAAAAAAAD1EylNAQABANG4BtXoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACzbLjU6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGXzrQE5fjdNAAAAAAAAAAAAAAAAAAAAAAN+N00CAAIAdaTl1OgAAADlRP3U6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAF+9sdToAAAAD7221OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAkqJXAPN-N00AAAAAAAAAAAAAAAAAAAAAvn83TQEAAgARpOXU6AAAAHWk5dToAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAX72x1OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADy5OcAyjtDTQAAAAAAAAAAAAAAAAAAAABbc0NNAQABAHVvC9XoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADfTrnU6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==; path=/; expires=Sat, 31-Dec-2019 00:00:00 GMT; domain=afy11.net; P3P: policyref="http://ad.afy11.net/privacy.xml", CP=" NOI DSP NID ADMa DEVa PSAa PSDa OUR OTRa IND COM NAV STA OTC"
GET /ad?asId=1000004165407&sd=2x300x250&ct=15&enc=0&nif=0&sf=0&sfd=0&ynw=0&anw=1&rand=86551686&rk1=26330496&rk2=1296251850.357&pt=0 HTTP/1.1 Host: ad.afy11.net Proxy-Connection: keep-alive Referer: http://www.bostonherald.com/includes/processAds.bg?position=Middle2&companion=Top,x14,x15,x16,Middle,Middle1,Middle2,Bottom&page=bh.heraldinteractive.com%2Fhome 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.237 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: a=AZ7s9B85IkyRNDgbVDU-vg; s=1,2*4d2913f5*YxNSVIeEeL*XkHked9a5WVEwm102ii7WMtfCA==*; c=AQEDAAAAAACarxAA-hMpTQAAAAAAAAAAAAAAAAAAAAD1EylNAQABANG4BtXoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACzbLjU6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGXzrQE5fjdNAAAAAAAAAAAAAAAAAAAAAAN+N00CAAIAdaTl1OgAAADlRP3U6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAF+9sdToAAAAD7221OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAkqJXAPN-N00AAAAAAAAAAAAAAAAAAAAAvn83TQEAAgARpOXU6AAAAHWk5dToAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAX72x1OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=; f=AgECAAAAAAALqJELwX83TQyokQsDfjdN
Response
HTTP/1.0 200 OK Connection: close Cache-Control: no-cache, must-revalidate Server: AdifyServer Content-Type: text/html; charset=utf-8 Content-Length: 1767 Set-Cookie: c=AQEEAAAAAACarxAA-hMpTQAAAAAAAAAAAAAAAAAAAAD1EylNAQABANG4BtXoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACzbLjU6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGXzrQE5fjdNAAAAAAAAAAAAAAAAAAAAAAN+N00CAAIAdaTl1OgAAADlRP3U6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAF+9sdToAAAAD7221OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAkqJXAPN-N00AAAAAAAAAAAAAAAAAAAAAvn83TQEAAgARpOXU6AAAAHWk5dToAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAX72x1OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAxZEByjtDTQAAAAAAAAAAAAAAAAAAAADUO0NNAQABAHVvC9XoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADfTrnU6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==; path=/; expires=Sat, 31-Dec-2019 00:00:00 GMT; domain=afy11.net; P3P: policyref="http://ad.afy11.net/privacy.xml", CP=" NOI DSP NID ADMa DEVa PSAa PSDa OUR OTRa IND COM NAV STA OTC"
The response contains the following link to another domain:
http://d3.zedo.com/jsc/d3/fo.js
Request
GET /ad?asId=1000004165407&sd=2x300x250&ct=15&enc=0&nif=0&sf=0&sfd=0&ynw=0&anw=1&rand=38178276&rk1=15197426&rk2=1296251850.36&pt=0 HTTP/1.1 Host: ad.afy11.net Proxy-Connection: keep-alive Referer: http://www.bostonherald.com/includes/processAds.bg?position=Middle1&companion=Top,x14,x15,x16,Middle,Middle1,Middle2,Bottom&page=bh.heraldinteractive.com%2Fhome 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.237 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: a=AZ7s9B85IkyRNDgbVDU-vg; s=1,2*4d2913f5*YxNSVIeEeL*XkHked9a5WVEwm102ii7WMtfCA==*; c=AQEDAAAAAACarxAA-hMpTQAAAAAAAAAAAAAAAAAAAAD1EylNAQABANG4BtXoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACzbLjU6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGXzrQE5fjdNAAAAAAAAAAAAAAAAAAAAAAN+N00CAAIAdaTl1OgAAADlRP3U6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAF+9sdToAAAAD7221OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAkqJXAPN-N00AAAAAAAAAAAAAAAAAAAAAvn83TQEAAgARpOXU6AAAAHWk5dToAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAX72x1OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=; f=AgECAAAAAAALqJELwX83TQyokQsDfjdN
Response
HTTP/1.0 200 OK Connection: close Cache-Control: no-cache, must-revalidate Server: AdifyServer Content-Type: text/html; charset=utf-8 Content-Length: 750 P3P: policyref="http://ad.afy11.net/privacy.xml", CP=" NOI DSP NID ADMa DEVa PSAa PSDa OUR OTRa IND COM NAV STA OTC"
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.
GET /ad?asId=1000004165407&sd=2x300x250&ct=15&enc=0&nif=0&sf=0&sfd=0&ynw=0&anw=1&rand=38178276&rk1=15197426&rk2=1296251850.36&pt=0 HTTP/1.1 Host: ad.afy11.net Proxy-Connection: keep-alive Referer: http://www.bostonherald.com/includes/processAds.bg?position=Middle1&companion=Top,x14,x15,x16,Middle,Middle1,Middle2,Bottom&page=bh.heraldinteractive.com%2Fhome 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.237 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: a=AZ7s9B85IkyRNDgbVDU-vg; s=1,2*4d2913f5*YxNSVIeEeL*XkHked9a5WVEwm102ii7WMtfCA==*; c=AQEDAAAAAACarxAA-hMpTQAAAAAAAAAAAAAAAAAAAAD1EylNAQABANG4BtXoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACzbLjU6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGXzrQE5fjdNAAAAAAAAAAAAAAAAAAAAAAN+N00CAAIAdaTl1OgAAADlRP3U6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAF+9sdToAAAAD7221OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAkqJXAPN-N00AAAAAAAAAAAAAAAAAAAAAvn83TQEAAgARpOXU6AAAAHWk5dToAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAX72x1OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=; f=AgECAAAAAAALqJELwX83TQyokQsDfjdN
Response
HTTP/1.0 200 OK Connection: close Cache-Control: no-cache, must-revalidate Server: AdifyServer Content-Type: text/html; charset=utf-8 Content-Length: 1767 Set-Cookie: c=AQEEAAAAAACarxAA-hMpTQAAAAAAAAAAAAAAAAAAAAD1EylNAQABANG4BtXoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACzbLjU6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGXzrQE5fjdNAAAAAAAAAAAAAAAAAAAAAAN+N00CAAIAdaTl1OgAAADlRP3U6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAF+9sdToAAAAD7221OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAkqJXAPN-N00AAAAAAAAAAAAAAAAAAAAAvn83TQEAAgARpOXU6AAAAHWk5dToAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAX72x1OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADy5OcAyjtDTQAAAAAAAAAAAAAAAAAAAABbc0NNAQABAHVvC9XoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADfTrnU6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==; path=/; expires=Sat, 31-Dec-2019 00:00:00 GMT; domain=afy11.net; P3P: policyref="http://ad.afy11.net/privacy.xml", CP=" NOI DSP NID ADMa DEVa PSAa PSDa OUR OTRa IND COM NAV STA OTC"
GET /ad?asId=1000004165407&sd=2x300x250&ct=15&enc=0&nif=0&sf=0&sfd=0&ynw=0&anw=1&rand=86551686&rk1=26330496&rk2=1296251850.357&pt=0 HTTP/1.1 Host: ad.afy11.net Proxy-Connection: keep-alive Referer: http://www.bostonherald.com/includes/processAds.bg?position=Middle2&companion=Top,x14,x15,x16,Middle,Middle1,Middle2,Bottom&page=bh.heraldinteractive.com%2Fhome 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.237 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: a=AZ7s9B85IkyRNDgbVDU-vg; s=1,2*4d2913f5*YxNSVIeEeL*XkHked9a5WVEwm102ii7WMtfCA==*; c=AQEDAAAAAACarxAA-hMpTQAAAAAAAAAAAAAAAAAAAAD1EylNAQABANG4BtXoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACzbLjU6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGXzrQE5fjdNAAAAAAAAAAAAAAAAAAAAAAN+N00CAAIAdaTl1OgAAADlRP3U6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAF+9sdToAAAAD7221OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAkqJXAPN-N00AAAAAAAAAAAAAAAAAAAAAvn83TQEAAgARpOXU6AAAAHWk5dToAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAX72x1OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=; f=AgECAAAAAAALqJELwX83TQyokQsDfjdN
Response
HTTP/1.0 200 OK Connection: close Cache-Control: no-cache, must-revalidate Server: AdifyServer Content-Type: text/html; charset=utf-8 Content-Length: 1767 Set-Cookie: c=AQEEAAAAAACarxAA-hMpTQAAAAAAAAAAAAAAAAAAAAD1EylNAQABANG4BtXoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACzbLjU6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGXzrQE5fjdNAAAAAAAAAAAAAAAAAAAAAAN+N00CAAIAdaTl1OgAAADlRP3U6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAF+9sdToAAAAD7221OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAkqJXAPN-N00AAAAAAAAAAAAAAAAAAAAAvn83TQEAAgARpOXU6AAAAHWk5dToAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAX72x1OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAxZEByjtDTQAAAAAAAAAAAAAAAAAAAADUO0NNAQABAHVvC9XoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADfTrnU6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==; path=/; expires=Sat, 31-Dec-2019 00:00:00 GMT; domain=afy11.net; P3P: policyref="http://ad.afy11.net/privacy.xml", CP=" NOI DSP NID ADMa DEVa PSAa PSDa OUR OTRa IND COM NAV STA OTC"
The response dynamically includes the following script from another domain:
http://d3.zedo.com/jsc/d3/fo.js
Request
GET /ad?asId=1000004165407&sd=2x300x250&ct=15&enc=0&nif=0&sf=0&sfd=0&ynw=0&anw=1&rand=38178276&rk1=15197426&rk2=1296251850.36&pt=0 HTTP/1.1 Host: ad.afy11.net Proxy-Connection: keep-alive Referer: http://www.bostonherald.com/includes/processAds.bg?position=Middle1&companion=Top,x14,x15,x16,Middle,Middle1,Middle2,Bottom&page=bh.heraldinteractive.com%2Fhome 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.237 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: a=AZ7s9B85IkyRNDgbVDU-vg; s=1,2*4d2913f5*YxNSVIeEeL*XkHked9a5WVEwm102ii7WMtfCA==*; c=AQEDAAAAAACarxAA-hMpTQAAAAAAAAAAAAAAAAAAAAD1EylNAQABANG4BtXoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACzbLjU6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGXzrQE5fjdNAAAAAAAAAAAAAAAAAAAAAAN+N00CAAIAdaTl1OgAAADlRP3U6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAF+9sdToAAAAD7221OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAkqJXAPN-N00AAAAAAAAAAAAAAAAAAAAAvn83TQEAAgARpOXU6AAAAHWk5dToAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAX72x1OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=; f=AgECAAAAAAALqJELwX83TQyokQsDfjdN
Response
HTTP/1.0 200 OK Connection: close Cache-Control: no-cache, must-revalidate Server: AdifyServer Content-Type: text/html; charset=utf-8 Content-Length: 750 P3P: policyref="http://ad.afy11.net/privacy.xml", CP=" NOI DSP NID ADMa DEVa PSAa PSDa OUR OTRa IND COM NAV STA OTC"
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Issue background
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.
Request
GET /ad?asId=1000004165407&sd=2x300x250&ct=15&enc=0&nif=0&sf=0&sfd=0&ynw=0&anw=1&rand=86551686&rk1=26330496&rk2=1296251850.357&pt=0 HTTP/1.1 Host: ad.afy11.net Proxy-Connection: keep-alive Referer: http://www.bostonherald.com/includes/processAds.bg?position=Middle2&companion=Top,x14,x15,x16,Middle,Middle1,Middle2,Bottom&page=bh.heraldinteractive.com%2Fhome 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.237 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: a=AZ7s9B85IkyRNDgbVDU-vg; s=1,2*4d2913f5*YxNSVIeEeL*XkHked9a5WVEwm102ii7WMtfCA==*; c=AQEDAAAAAACarxAA-hMpTQAAAAAAAAAAAAAAAAAAAAD1EylNAQABANG4BtXoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACzbLjU6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGXzrQE5fjdNAAAAAAAAAAAAAAAAAAAAAAN+N00CAAIAdaTl1OgAAADlRP3U6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAF+9sdToAAAAD7221OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAkqJXAPN-N00AAAAAAAAAAAAAAAAAAAAAvn83TQEAAgARpOXU6AAAAHWk5dToAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAX72x1OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=; f=AgECAAAAAAALqJELwX83TQyokQsDfjdN
Response
HTTP/1.0 200 OK Connection: close Cache-Control: no-cache, must-revalidate Server: AdifyServer Content-Type: text/html; charset=utf-8 Content-Length: 1767 Set-Cookie: c=AQEEAAAAAACarxAA-hMpTQAAAAAAAAAAAAAAAAAAAAD1EylNAQABANG4BtXoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACzbLjU6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGXzrQE5fjdNAAAAAAAAAAAAAAAAAAAAAAN+N00CAAIAdaTl1OgAAADlRP3U6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAF+9sdToAAAAD7221OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAkqJXAPN-N00AAAAAAAAAAAAAAAAAAAAAvn83TQEAAgARpOXU6AAAAHWk5dToAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAX72x1OgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAxZEByjtDTQAAAAAAAAAAAAAAAAAAAADUO0NNAQABAHVvC9XoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADfTrnU6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==; path=/; expires=Sat, 31-Dec-2019 00:00:00 GMT; domain=afy11.net; P3P: policyref="http://ad.afy11.net/privacy.xml", CP=" NOI DSP NID ADMa DEVa PSAa PSDa OUR OTRa IND COM NAV STA OTC"
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: ad.afy11.net
Response
HTTP/1.1 200 OK Content-Type: text/plain Last-Modified: Fri, 06 Jul 2007 06:09:38 GMT Accept-Ranges: bytes ETag: "78f7133c94bfc71:0" Server: Microsoft-IIS/7.5 X-Powered-By: ASP.NET Date: Fri, 28 Jan 2011 16:39:29 GMT Connection: close Content-Length: 30