Risk Inside Facebook and Twitter Best Practice - Lack of Password Confirmation






There are many websites including Facebook and Twitter that are missing best practices. Lack of Password confirmation allows intruders to easily takeover the users account completely.



When any user wants to change the password, current password is asked for proceeding the request and for security purpose. This should also be implemented on other sensitive actions like email, phone no. and account deletion.



If any unauthorized user or hacker access your account through anyway like session hijacking or by exploiting XSS or CSRF attack then he can easily change your password and takeover the account completely.
So, the current password field is necessary because it prevents any unauthorized user from changing the email and password.
Facebook prevents this by asking current password when changing email and password but it's still possible to change the password without knowing current password.

It's very simple. Just add your mobile number then using 'forgot password' feature, reset the password.
So, without knowing current password we can change the password and completely takeover the facebook user account.


 So, password confirmation should also be implemented on mobile phone number.

The same bug also exist in Twitter. We can change twitter user password through Mobile phone number without knowing current password.

Another bug, when we change Email on Twitter, twitter asks current password but we can bypass this, in twitter subdomain ie mobile.twitter.com.
Try to change the email in mobile.twitter.com. Without knowing current password it's possible to change the email then we can easily reset the password through new email.





So, don't left your account open in any public place or anywhere because if anyone or any hacker access that device and the account then he can easily reset your account password and delete or completely takeover the account.

Comments

Post a Comment

Popular posts from this blog

XSS like a Pro

Image
Hello Friends, I'm gonna share my interesting finding here. Recently,  About two months ago,  I received a private invitation on Bugcrowd and the next day I started to look for bugs on that website because there was only one target (testing site) in scope and they provided me some credentials. I can't disclose the site name, so let's assume https://redacted.com First of all, I logged-in to that site (redacted.com) with the provided credentials and inspected the site around 15 minutes and tried to understand it. After that, I started to look for bugs and found multiple bugs mostly stored XSS. At that day, I had found a total 11 vulnerabilities. I reported them and received a bounty on each report. So, I'm not disclosing the bounties. Also, I'm not sharing my all findings but some. So,  At the beginning, I tried to change my default password and successfully changed my password to '1' which was the first bug that there is no password policy.
Read more

Email Spoofing for Beginners

Image
Hello Everyone, Greetings to all, In this article, I'll talk about email spoofing in a little depth. So, First of all What is Email Spoofing?  If you already know about email spoofing then congratulations But don't worry if u don't know about email spoofing. Email spoofing is a tactic used in phishing and spam campaigns because people are more likely to open an email when they think it has been sent by a legitimate source. It's not a new technique. It's a very old technique and still widely used in phishing and scamming. This article is going to be interesting and I'll try to short this long article as much simple as possible. Recently, my friend ask me How it's possible to spoof an email? So, there are a lot of questions related to this issue.  When a Domain is Spoofable? It is just as simple in an email as well because email protocols (SMTP) lack authentication. Anyone with a little basic knowledge can able to send an email wit
Read more

DoS on WAF Protected Sites by Abusing Cookie

Image
Hi Folks, Today, I'm gonna share one of my interesting finding in bug bounty. I occasionally hunt bugs in bug bounty in my free time. So, I don't have enough time to blog. But on someone request, I share some of my bug bounty findings here. I like to find some interesting and logical bugs. Recently, I found an interesting bug in many sites but I can't disclose the name of every website, one website 'Upwork' already patched this bug and resolved the report that's why I disclose the name. So, what's the bug?   Denial of Service (DoS) > Single user cookie based DoS There are a lot of websites using WAF like Cloudflare etc. When the Cookie sets with malicious characters(like"><script> alert(1)</script> mean  with XSS or SQLI payloads etc.) value, the site WAF like Cloudflare block us from accessing that website, we need to remove that cookie to access the site Many websites sets 'Referrer'
Read more