Vulnerability

hmaddy

Verified User
Joined
Apr 17, 2019
Messages
288
Got one email like this.??? So how can i review and block this type of vulnerability

Hi Team.

I am a security researcher and I have found a bug in your website https://abcs.com/
The details of it are as follows:-

CLICK-JACKING.

Description :

Click-jacking, also known as a "UI redress attack" is when an attacker uses multiple transparent or opaque layers to trick a user into clicking on a button or link on another page when they were intending to click on the top level page. Thus, the attacker is "hijacking" clicks meant for their page and routing them to another page, most likely owned by another application, domain, or both.

Using a similar technique, keystrokes can also be hijacked. With a carefully crafted combination of style-sheets, I-frames, and text boxes, a user can be led to believe they are typing in the password to their email or bank account, but are instead typing into an invisible frame controlled by the attacker.

Impacts:

1. Tricking a user into unknowingly clicking on things and then gaining access to his account
2. An attacker can gain access to the credentials of users and use those credentials for booking and payment.
3. Adding events to their profile they are interested in attending.
4. editing their star rating on reviews
5. Using their bank account details to books in hotels whereas the bill will go to their bank account.
6. Bookmarking unwanted business.

POC:

<html>

<head>

</head>

<body>

<h1>Click-Jacking In Your Site</h1>

<iframe src=" https://abcs.com/clients/clientarea.php "height="800" width="1300">

</iframe>

</body>

</html>

Waiting for your reply.
 
It's a whmcs vulrnability i assume, nothing related to DA itself.

I got two of these forwarded in the past from clients, exactrly the same as this one
 
This is typically an application layer thing. You can mitigate it in your website coding (php for example), or in htaccess.

Just found these in Google, do your own reseach.

Includes PHP examples:

htaccess examples:
 
If it is real mail and real site aplication problem then look into that site and the aplication as the tips above.

For wordpress you have a lot also complete htaccess examples for example search the web with duckduckiegogo ;) ( not with bigslurper Googie)



IN DA GUI custombuild you have options as modsecurity and Snuffleupagus

pic some... htaccess
Code:
Header always set X-Frame-Options "SAMEORIGIN"
    Header set X-XSS-Protection "1; mode=block"
    # Content-Security-Policy: script-src 'self'
     Header set Content-Security-Policy: "frame-ancestors 'self' https://yuorsite;"
    # Header set Content-Security-Policy "default-src 'self' https:"; "script-src https://yuorsite"
    # Header set Content-Security-Policy-Report-Only: "default-src: https:"
    #    Header set Access-Control-Allow-Origin "*"
    #Header set Content-Security-Policy "default-src https: 'self'; script-src https: 'self'; child-src https: 'self'; connect-src https: 'self'; style-src https: 'unsafe-inline' 'self'; font-src https: 'self'; media-src https: 'self'; img-src https: 'self' data:;"
    Header set X-Content-Type-Options "nosniff"  
    Header set Referrer-Policy "no-referrer"
    Header set Referrer-Policy "strict-origin-when-cross-origin"
    #    Header always set Permissions-Policy "geolocation=(),midi=(),sync-xhr=(),microphone=(),camera=(),magnetometer=(),gyroscope=(),fullscreen=(),payment=()"
    Header always set Permissions-Policy "microphone=(),camera=(),magnetometer=(),gyroscope=()"
    Header append Vary Accept env=REDIRECT_accept
 
Back
Top