<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.owasp.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=JerryH</id>
		<title>OWASP - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.owasp.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=JerryH"/>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php/Special:Contributions/JerryH"/>
		<updated>2026-05-30T03:53:07Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.27.2</generator>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Clickjacking&amp;diff=49876</id>
		<title>Clickjacking</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Clickjacking&amp;diff=49876"/>
				<updated>2008-12-27T23:02:56Z</updated>
		
		<summary type="html">&lt;p&gt;JerryH: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Clickjacking, also known as a UI Redress Attack, is when an attacker uses multiple (often transparent) layers so when a user clicks on an area of the web page, they are inadvertently clicking on a button or link on another page.&lt;br /&gt;
&lt;br /&gt;
For example, imagine an attacker who builds a web site that has a button on it that says &amp;quot;click here for a free iPod&amp;quot;.  However, on top of that web page, the attacker has loaded in a iframe your mail account, and lined up exactly the &amp;quot;delete all messages&amp;quot; button directly on top of the &amp;quot;free iPod&amp;quot; button.  The victim tries to click on the &amp;quot;free iPod&amp;quot; button but instead actually clicked on the invisible &amp;quot;delete all messages&amp;quot; button.  In essence, the attacker has &amp;quot;hijacked&amp;quot; the user's click, hence the name &amp;quot;Clickjacking&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Using the same technique, keystrokes could also be hijacked, so a user believes they are typing in their password to their email or their bank account, but in reality they are typing into an invisible frame, possibly controlled by the attacker.&lt;br /&gt;
&lt;br /&gt;
One of the most notorious examples of Clickjacking was an attack against the Adobe Flash plugin settings page:&lt;br /&gt;
&lt;br /&gt;
http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager06.html&lt;br /&gt;
&lt;br /&gt;
By loading this page into an invisible iframe, an attacker could trick a user into altering the security settings of Flash, giving permission for any Flash animation to utilize the computer's microphone and camera.&lt;br /&gt;
&lt;br /&gt;
To prevent this from happening, Adobe added the following code to the web page:&lt;br /&gt;
&lt;br /&gt;
  if (top!=self){&lt;br /&gt;
        top.location.href=self.location.href;&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This code ensures the page cannot be embedded into an iframe, and therefore cannot be used as part of a clickjacking attack.&lt;/div&gt;</summary>
		<author><name>JerryH</name></author>	</entry>

	</feed>