Vulnerability Report (2) Clickjacking Lead to Account Takeover

Hi Team

I have detected that your website is vulnerable to this vulnerability

Vulnerability Type: Clickjacking Lead to Account Takeover

Severity: Critical

Issue:

Clickjacking (User Interface redress attack, UI redress attack, UI redressing) is a malicious technique of tricking a Web user into clicking on something different from what the user perceives they are clicking on, thus potentially revealing confidential information or taking control of their computer while clicking on seemingly innocuous web pages.

The server didn't return an X-Frame-Options header which means that this website could be at risk of a clickjacking attack. The X-Frame-Options HTTP response header can be used to indicate whether or not a browser should be allowed to render a page in a <frame> or <iframe>. Sites can use this to avoid clickjacking attacks, by ensuring that their content is not embedded into other sites.

This vulnerability affects Web Server.

Steps To Reproduce :

Here are the steps to reproduce the vulnerability

1.open notepad and paste the following code

<!DOCTYPE HTML>
<html lang="en-US">
<head>
<meta charset="UTF-8">
<title>i Frame</title>
</head>
<body>
<h3>This is clickjacking vulnerable</h3>
<iframe src="https://www.odoo.com/" frameborder="200 px" height="5000px" width="500px"></iframe>
</body>
</html>

2.save it as <anyname>.html eg s.html
3.and just simply open that..

4. Understanding the Remedial Action for Clickjacking

Clickjacking can be prevented using a host of client side browser plugins such as
• NoScript – http://noscript.net
• Web Protection Suite – http://www.comitari.com/Web_Protection_Suite
These plugins are recommended for daily browsing and can also protect users against additional client side attacks, such as XSS (Cross Site Scripting).
The above plugins are client side prevention techniques that should be taught to all application users; however, steps must also be taken from the developer’s end.

The following techniques can be used to aid in the prevention of clickjacking:

4.1. X-Frame-Options

The simplest of all the techniques that only requires a simple configuration setting; for example, this can be done within Apache using the following line:

<pre lang="JavaScript" line="1">Header always append X-Frame-Options DENY</pre>

4.2. FrameBusting JavaScript

This method utilizes JavaScript to “bust” iframes. This is done by checking if the current web page is the top web page (not within a frame) and if the web page is currently not the top page, then it becomes the top page.

The following example segment of code can be used to demonstrate this:

<pre lang="JavaScript" line="1">if (top.location.hostname != self.location.hostname){
top.location.href = self.location.href;
}</pre>

It should be noted that recent techniques have found to be able to bypass this clickjacking prevention technique as seen in the whitepaper by web application security researcher Collin Jackson – http://www.collinjackson.com/research/xssauditor.pdf.

4.3.Unique URL request

Similar to a CSRF nonce, this can be employed so attackers cannot deliver the attack URL easily.

4.4. CAPTCHAs

Similar to the way it prevents attackers from spamming a web form, this can be used as an additional layer of verification on each transaction.

4.5. Element Randomization

Generally it is possible to clickjack due to buttons and links being in a static area of the web page, allowing attackers to place invisible frames over them. A technique to prevent this from occurring is to randomize the links or buttons on load, thus preventing attackers from hard coding static iframes.

Proof of Concept :

image.png

Please let me know if you need more information. Looking after your response.

Regards,
Asif.


por Bug Hunter <[email protected]> - 06:12 - 30 abr. 2022

Seguimientos

  • Re: Vulnerability Report (2) Clickjacking Lead to Account Takeover
    Hi Team,

    It is hereby to remind you regarding my reports that I sent you last time. It would be a great pleasure to me provided you give me a favorable response. It has already been a long time, yet no reply. You are kindly being requested to look into those reports I sent you and please give me favorable responses as soon as possible.

    Looking forward to hearing from you.

    Sincerely,
    Asif.

    On Wed, 18 May 2022 at 00:59, Bug Hunter <[email protected]> wrote:
    Hi,

    I hope this email finds you well.

    I have recently sent some vulnerabilities to you and I did not hear any word from your side. So, It is requested that you please update me on my submitted discoveries. And I have found some more critical vulnerabilities that I want to send you.

    Looking forward to your response.

    Sincerely,
    Asif.

    On Mon, 9 May 2022 at 13:15, Bug Hunter <[email protected]> wrote:
    Hi,

    Any follow up on my vulnerability reports?

    Have a great day,

    Thanks,
    Asif.

    On Sat, 30 Apr 2022 at 15:11, Bug Hunter <[email protected]> wrote:
    Hi Team

    I have detected that your website is vulnerable to this vulnerability

    Vulnerability Type: Clickjacking Lead to Account Takeover

    Severity: Critical

    Issue:

    Clickjacking (User Interface redress attack, UI redress attack, UI redressing) is a malicious technique of tricking a Web user into clicking on something different from what the user perceives they are clicking on, thus potentially revealing confidential information or taking control of their computer while clicking on seemingly innocuous web pages.

    The server didn't return an X-Frame-Options header which means that this website could be at risk of a clickjacking attack. The X-Frame-Options HTTP response header can be used to indicate whether or not a browser should be allowed to render a page in a <frame> or <iframe>. Sites can use this to avoid clickjacking attacks, by ensuring that their content is not embedded into other sites.

    This vulnerability affects Web Server.

    Steps To Reproduce :

    Here are the steps to reproduce the vulnerability

    1.open notepad and paste the following code

    <!DOCTYPE HTML>
    <html lang="en-US">
    <head>
    <meta charset="UTF-8">
    <title>i Frame</title>
    </head>
    <body>
    <h3>This is clickjacking vulnerable</h3>
    <iframe src="https://www.odoo.com/" frameborder="200 px" height="5000px" width="500px"></iframe>
    </body>
    </html>

    2.save it as <anyname>.html eg s.html
    3.and just simply open that..

    4. Understanding the Remedial Action for Clickjacking

    Clickjacking can be prevented using a host of client side browser plugins such as
    • NoScript – http://noscript.net
    • Web Protection Suite – http://www.comitari.com/Web_Protection_Suite
    These plugins are recommended for daily browsing and can also protect users against additional client side attacks, such as XSS (Cross Site Scripting).
    The above plugins are client side prevention techniques that should be taught to all application users; however, steps must also be taken from the developer’s end.

    The following techniques can be used to aid in the prevention of clickjacking:

    4.1. X-Frame-Options

    The simplest of all the techniques that only requires a simple configuration setting; for example, this can be done within Apache using the following line:

    <pre lang="JavaScript" line="1">Header always append X-Frame-Options DENY</pre>

    4.2. FrameBusting JavaScript

    This method utilizes JavaScript to “bust” iframes. This is done by checking if the current web page is the top web page (not within a frame) and if the web page is currently not the top page, then it becomes the top page.

    The following example segment of code can be used to demonstrate this:

    <pre lang="JavaScript" line="1">if (top.location.hostname != self.location.hostname){
    top.location.href = self.location.href;
    }</pre>

    It should be noted that recent techniques have found to be able to bypass this clickjacking prevention technique as seen in the whitepaper by web application security researcher Collin Jackson – http://www.collinjackson.com/research/xssauditor.pdf.

    4.3.Unique URL request

    Similar to a CSRF nonce, this can be employed so attackers cannot deliver the attack URL easily.

    4.4. CAPTCHAs

    Similar to the way it prevents attackers from spamming a web form, this can be used as an additional layer of verification on each transaction.

    4.5. Element Randomization

    Generally it is possible to clickjack due to buttons and links being in a static area of the web page, allowing attackers to place invisible frames over them. A technique to prevent this from occurring is to randomize the links or buttons on load, thus preventing attackers from hard coding static iframes.

    Proof of Concept :

    image.png

    Please let me know if you need more information. Looking after your response.

    Regards,
    Asif.


    por Bug Hunter <[email protected]> - 04:05 - 31 may. 2022
  • Re: Vulnerability Report (2) Clickjacking Lead to Account Takeover
    Hi,

    I hope this email finds you well.

    I have recently sent some vulnerabilities to you and I did not hear any word from your side. So, It is requested that you please update me on my submitted discoveries. And I have found some more critical vulnerabilities that I want to send you.

    Looking forward to your response.

    Sincerely,
    Asif.

    On Mon, 9 May 2022 at 13:15, Bug Hunter <[email protected]> wrote:
    Hi,

    Any follow up on my vulnerability reports?

    Have a great day,

    Thanks,
    Asif.

    On Sat, 30 Apr 2022 at 15:11, Bug Hunter <[email protected]> wrote:
    Hi Team

    I have detected that your website is vulnerable to this vulnerability

    Vulnerability Type: Clickjacking Lead to Account Takeover

    Severity: Critical

    Issue:

    Clickjacking (User Interface redress attack, UI redress attack, UI redressing) is a malicious technique of tricking a Web user into clicking on something different from what the user perceives they are clicking on, thus potentially revealing confidential information or taking control of their computer while clicking on seemingly innocuous web pages.

    The server didn't return an X-Frame-Options header which means that this website could be at risk of a clickjacking attack. The X-Frame-Options HTTP response header can be used to indicate whether or not a browser should be allowed to render a page in a <frame> or <iframe>. Sites can use this to avoid clickjacking attacks, by ensuring that their content is not embedded into other sites.

    This vulnerability affects Web Server.

    Steps To Reproduce :

    Here are the steps to reproduce the vulnerability

    1.open notepad and paste the following code

    <!DOCTYPE HTML>
    <html lang="en-US">
    <head>
    <meta charset="UTF-8">
    <title>i Frame</title>
    </head>
    <body>
    <h3>This is clickjacking vulnerable</h3>
    <iframe src="https://www.odoo.com/" frameborder="200 px" height="5000px" width="500px"></iframe>
    </body>
    </html>

    2.save it as <anyname>.html eg s.html
    3.and just simply open that..

    4. Understanding the Remedial Action for Clickjacking

    Clickjacking can be prevented using a host of client side browser plugins such as
    • NoScript – http://noscript.net
    • Web Protection Suite – http://www.comitari.com/Web_Protection_Suite
    These plugins are recommended for daily browsing and can also protect users against additional client side attacks, such as XSS (Cross Site Scripting).
    The above plugins are client side prevention techniques that should be taught to all application users; however, steps must also be taken from the developer’s end.

    The following techniques can be used to aid in the prevention of clickjacking:

    4.1. X-Frame-Options

    The simplest of all the techniques that only requires a simple configuration setting; for example, this can be done within Apache using the following line:

    <pre lang="JavaScript" line="1">Header always append X-Frame-Options DENY</pre>

    4.2. FrameBusting JavaScript

    This method utilizes JavaScript to “bust” iframes. This is done by checking if the current web page is the top web page (not within a frame) and if the web page is currently not the top page, then it becomes the top page.

    The following example segment of code can be used to demonstrate this:

    <pre lang="JavaScript" line="1">if (top.location.hostname != self.location.hostname){
    top.location.href = self.location.href;
    }</pre>

    It should be noted that recent techniques have found to be able to bypass this clickjacking prevention technique as seen in the whitepaper by web application security researcher Collin Jackson – http://www.collinjackson.com/research/xssauditor.pdf.

    4.3.Unique URL request

    Similar to a CSRF nonce, this can be employed so attackers cannot deliver the attack URL easily.

    4.4. CAPTCHAs

    Similar to the way it prevents attackers from spamming a web form, this can be used as an additional layer of verification on each transaction.

    4.5. Element Randomization

    Generally it is possible to clickjack due to buttons and links being in a static area of the web page, allowing attackers to place invisible frames over them. A technique to prevent this from occurring is to randomize the links or buttons on load, thus preventing attackers from hard coding static iframes.

    Proof of Concept :

    image.png

    Please let me know if you need more information. Looking after your response.

    Regards,
    Asif.


    por Bug Hunter <[email protected]> - 04:00 - 17 may. 2022
  • Re: Vulnerability Report (2) Clickjacking Lead to Account Takeover
    Hi,

    Any follow up on my vulnerability reports?

    Have a great day,

    Thanks,
    Asif.

    On Sat, 30 Apr 2022 at 15:11, Bug Hunter <[email protected]> wrote:
    Hi Team

    I have detected that your website is vulnerable to this vulnerability

    Vulnerability Type: Clickjacking Lead to Account Takeover

    Severity: Critical

    Issue:

    Clickjacking (User Interface redress attack, UI redress attack, UI redressing) is a malicious technique of tricking a Web user into clicking on something different from what the user perceives they are clicking on, thus potentially revealing confidential information or taking control of their computer while clicking on seemingly innocuous web pages.

    The server didn't return an X-Frame-Options header which means that this website could be at risk of a clickjacking attack. The X-Frame-Options HTTP response header can be used to indicate whether or not a browser should be allowed to render a page in a <frame> or <iframe>. Sites can use this to avoid clickjacking attacks, by ensuring that their content is not embedded into other sites.

    This vulnerability affects Web Server.

    Steps To Reproduce :

    Here are the steps to reproduce the vulnerability

    1.open notepad and paste the following code

    <!DOCTYPE HTML>
    <html lang="en-US">
    <head>
    <meta charset="UTF-8">
    <title>i Frame</title>
    </head>
    <body>
    <h3>This is clickjacking vulnerable</h3>
    <iframe src="https://www.odoo.com/" frameborder="200 px" height="5000px" width="500px"></iframe>
    </body>
    </html>

    2.save it as <anyname>.html eg s.html
    3.and just simply open that..

    4. Understanding the Remedial Action for Clickjacking

    Clickjacking can be prevented using a host of client side browser plugins such as
    • NoScript – http://noscript.net
    • Web Protection Suite – http://www.comitari.com/Web_Protection_Suite
    These plugins are recommended for daily browsing and can also protect users against additional client side attacks, such as XSS (Cross Site Scripting).
    The above plugins are client side prevention techniques that should be taught to all application users; however, steps must also be taken from the developer’s end.

    The following techniques can be used to aid in the prevention of clickjacking:

    4.1. X-Frame-Options

    The simplest of all the techniques that only requires a simple configuration setting; for example, this can be done within Apache using the following line:

    <pre lang="JavaScript" line="1">Header always append X-Frame-Options DENY</pre>

    4.2. FrameBusting JavaScript

    This method utilizes JavaScript to “bust” iframes. This is done by checking if the current web page is the top web page (not within a frame) and if the web page is currently not the top page, then it becomes the top page.

    The following example segment of code can be used to demonstrate this:

    <pre lang="JavaScript" line="1">if (top.location.hostname != self.location.hostname){
    top.location.href = self.location.href;
    }</pre>

    It should be noted that recent techniques have found to be able to bypass this clickjacking prevention technique as seen in the whitepaper by web application security researcher Collin Jackson – http://www.collinjackson.com/research/xssauditor.pdf.

    4.3.Unique URL request

    Similar to a CSRF nonce, this can be employed so attackers cannot deliver the attack URL easily.

    4.4. CAPTCHAs

    Similar to the way it prevents attackers from spamming a web form, this can be used as an additional layer of verification on each transaction.

    4.5. Element Randomization

    Generally it is possible to clickjack due to buttons and links being in a static area of the web page, allowing attackers to place invisible frames over them. A technique to prevent this from occurring is to randomize the links or buttons on load, thus preventing attackers from hard coding static iframes.

    Proof of Concept :

    image.png

    Please let me know if you need more information. Looking after your response.

    Regards,
    Asif.


    por Bug Hunter <[email protected]> - 04:16 - 9 may. 2022