- Status Closed
-
Assigned To
cbay - Private
Opened by waloodi_109 - 26.11.2024
Last edited by cbay - 26.11.2024
FS#110 - Unveiling an IDOR Vulnerability in Email Verification Workflows
Unveiling an IDOR Vulnerability in Email Verification Workflows:
Hello Team, I hope you are doing well. Well, i found a idor vuln in email verification workflow in your doamin.
The Vulnerability
1. Step 1: Create an Account with a Fake Email (Email 1)
Like many web services, the platform I was testing does not required users to verify their email addresses upon registration. I created an account using a random, unverified email address, let’s call it email1@example.com.
2. Step 2: Change the Email Address to a New One (Email 2)
Next, I went to the account settings and attempted to change the email address to a new one, email2@example.com, without verifying email1@example.com. The system allowed me to enter a new email.
3. Step 3: IDOR Exploitation
Here’s where things got interesting. I can use email2@example.com without any verification or any notification which was not sent to that email2@example.com for verification. But due to an IDOR vulnerability, the system skipped this step entirely and automatically considered email2@example.com as verified
This meant that I, as an attacker, could verify someone else’s email (Email 2) that I had no control over, effectively gaining control of that account’s new email without ever needing access to it.
The Impact
This IDOR vulnerability presents significant risks, including:
Account Takeover: By exploiting this flaw, an attacker can hijack accounts by swapping the victim’s email with one of their own.
Phishing and Fraud: Attackers could use the new email to perform phishing attacks, tricking users into divulging sensitive information.
Loss of Control: Users might lose control over their accounts since the new email is verified without their knowledge or consent.
Root Cause
The root cause of this vulnerability lies in the system’s failure to validate the ownership of the new email address before considering it verified. Once the first email is verified, the system should force a re-verification of any newly entered email addresses to prevent this kind of exploitation.
How to Prevent It
Here are a few recommendations to mitigate this type of IDOR vulnerability:
Re-verify New Emails: Ensure that when users attempt to change their email addresses, the new email must be verified before it becomes active.
Strict Access Control: Always implement strong access controls to ensure that a user cannot modify objects (in this case, email IDs) they do not own.
Thorough Input Validation: Validate user inputs and ensure proper checks for email ownership before performing any sensitive actions.
Security Audits: Regularly conduct security audits and penetration testing to identify potential IDOR vulnerabilities and other security flaws.
Thank You,
Waleed Anwar
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
Hello,
What do you mean exactly by "the system considered that email as verified", since we don't verify emails?
Kind regards,
Cyril
As, we consider it to use it that why i wrote verified but it's a serious issue you can consider it
If your report is about the lack of email validation, it's already been reported before.
it's not a lack of verification, it's about idor in email verification, i can takeover anyuser email to add in my profile without any notification and verification was sent to there email.
I don't understand what you mean. You can change your email address to any (non already taken) email address, just like when you sign up. There's no "takeover" whatsoever.
but, there is no notification and verification link was sent to that email,please have a look on it
Read this https://medium.com/@manishadz/unveiling-an-idor-vulnerability-in-email-verification-workflows-1b2fe666a475
So as I said, your report is about the lack of email validation, which was already reported.