<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>stopthehacker.com &#187; XSS</title>
	<atom:link href="http://www.stopthehacker.com/tag/xss/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.stopthehacker.com</link>
	<description>Jaal, LLC</description>
	<lastBuildDate>Wed, 21 Jul 2010 22:21:37 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Youtube Hit with HTML Injection Attack</title>
		<link>http://www.stopthehacker.com/2010/07/04/youtube-hit-by-html-injection/</link>
		<comments>http://www.stopthehacker.com/2010/07/04/youtube-hit-by-html-injection/#comments</comments>
		<pubDate>Sun, 04 Jul 2010 18:00:20 +0000</pubDate>
		<dc:creator>anirban</dc:creator>
				<category><![CDATA[Report]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[sanitization']]></category>
		<category><![CDATA[XSS]]></category>
		<category><![CDATA[youtube]]></category>

		<guid isPermaLink="false">http://www.stopthehacker.com/?p=1912</guid>
		<description><![CDATA[YouTube is reported to have been hit by hackers. They have exploited a loophole in the way YouTube lets users post comments. More information can be found in the Google Support Forum and on Slashdot.
Analysis
It seems that when someone places a piece of JavaScript in the comment section, beginning with the &#60;script&#62; tag, YouTube&#8217;s comment [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.youtube.com" target="_blank">YouTube</a> is reported to have been hit by hackers. They have exploited a loophole in the way YouTube lets users post comments. More information can be found in the <a href="http://www.google.com/support/forum/p/youtube/thread?tid=2059b45a2a699910&amp;hl=en" target="_blank">Google Support Forum</a> and on <a href="http://slashdot.org/story/10/07/04/1530234/YouTube-Hit-By-HTML-Injection-Vulnerability" target="_blank">Slashdot</a>.</p>
<p><strong>Analysis</strong><br />
It seems that when someone places a piece of JavaScript in the comment section, beginning with the &lt;script&gt; tag, YouTube&#8217;s comment sanitization policy correctly escapes the &lt;script&gt; tag itself. Unfortunately, the data which follows this tag is not removed, but is displayed on the screen. This allows a clever hacker to inject HTML directly into the page, modifying the page itself and allowing all types of security issues.</p>
<p>This incident highlights the impact of security issues like Cross Site Scripting (XSS). These vulnerabilities should not be treated lightly, since a Web Application Filter (WAF) cannot protect you from new attacks like this one. WAFs can only protect you from what they already know.</p>
<p><strong>About stopthehacker.com</strong><br />
At <a href="http://www.stopthehacker.com/" target="_self">stopthehacker.com</a>, we work hard to help you combat attacks by malicious hackers. If you would like to work with us, please drop us an <a href="http://www.stopthehacker.com/contact/" target="_self">email</a>. You can also visit our <a href="http://www.stopthehacker.com/services/" target="_self">services</a> page to find out how we can help you. In fact, you can even sign up for our <a href="http://www.stopthehacker.com/services/blacklist-monitoring/" target="_blank">Free Blacklist Monitoring</a> service!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.stopthehacker.com/2010/07/04/youtube-hit-by-html-injection/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Top Banks Suffering from Multiple Vulnerabilities</title>
		<link>http://www.stopthehacker.com/2009/11/25/top-banks-suffering-from-multiple-vulnerabilities/</link>
		<comments>http://www.stopthehacker.com/2009/11/25/top-banks-suffering-from-multiple-vulnerabilities/#comments</comments>
		<pubDate>Wed, 25 Nov 2009 17:15:27 +0000</pubDate>
		<dc:creator>anirban</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Report]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[2009]]></category>
		<category><![CDATA[banks]]></category>
		<category><![CDATA[security hole]]></category>
		<category><![CDATA[US]]></category>
		<category><![CDATA[vulnerabilities]]></category>
		<category><![CDATA[XSS]]></category>

		<guid isPermaLink="false">http://www.stopthehacker.com/?p=633</guid>
		<description><![CDATA[Solid financial institutions are the cornerstone of any successful economy. These institutions need to maintain the highest levels of security to protect sensitive customer data from becoming prey to malicious interests. Given the fact that these giants of industry have emergency response and security teams and that they spend hundreds of thousands of dollars a [...]]]></description>
			<content:encoded><![CDATA[<p>Solid financial institutions are the cornerstone of any successful economy. These institutions need to maintain the highest levels of security to protect sensitive customer data from becoming prey to malicious interests. Given the fact that these giants of industry have emergency response and security teams and that they spend hundreds of thousands of dollars a year on everything from general IT infrastructure to buying a plethora of security products. It is surprising to see that these top banks and financial institutions are not as locked down and airtight as one should expect.</p>
<p>We at StopTheHacker.com have conducted a study to ascertain if these top financial institutions are really secure or not. The findings, including a graphical summary, are also available in a PDF report attached at the end of this article.</p>
<dl id="attachment_693" class="wp-caption aligncenter" style="width: 546px;">
<dt class="wp-caption-dt"><img class="size-full wp-image-693" title="Graph of the Security Level of the Top US Banks, 2009 (fix)" src="http://www.stopthehacker.com/wp-content/uploads/2009/11/bank-graph2.png" alt="Security Level of Top US Financial Institutions in 2009" width="536" height="371" /></dt>
<dd class="wp-caption-dd">Security Level of Top US Financial Institutions in 2009</dd>
</dl>
<p>The results were astonishing: 13 out of 14 websites had at least one critical vulnerability. In more detail, we highlight some key results below:</p>
<ol>
<li>On average, there are 1.5 critical security issues in each financial institution</li>
<li>On average, there are 1.2 important security issues in each financial institution</li>
<li>On average, there are 7.9 general security issues in each financial institution</li>
<li>The highest company valuation in total assets does not correlate to the highest security</li>
<li>The financial institution in our set with the least valuation had zero critical security holes</li>
</ol>
<p>The identified vulnerabilities are very serious: critical security issues/holes are widely seen as major security concerns by security experts, and security standards.</p>
<p>The most prevalent vulnerability among all of those discovered, allows a hacker to spawn what is known as a shell, more commonly known as the command-prompt, and thereby remotely executing harmful commands on the web server. Other vulnerabilities range from major Cross Site Scripting (XSS) vulnerabilities, which can enable hacker to steal credentials of website visitors, to a plethora of concerns with various software installations used on these systems.</p>
<p>For more information, please feel free to <a href="/contact/">contact us</a>.</p>
<ul>
<li><a href="/wp-content/uploads/2009/11/bank-vulnerabilities-2009-v2.pdf">Download the Whitepaper</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.stopthehacker.com/2009/11/25/top-banks-suffering-from-multiple-vulnerabilities/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
