You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "Resend Verification Email" feature on the Rocket.Chat profile page can be exploited to send an unlimited number of verification emails in a short period of time. By copying the network request triggered by the "Resend" button and programmatically executing it in a loop (e.g., 1000 times), the server sends a verification email for each request without any rate limiting or throttling in place. This can result in email spam and potentially overload the mail server, leading to degraded performance or service disruption.
Hello Is this issue fixed ? If not please reply I will be happy to help
Actually, one pr have been made to fix this issue, but if you'd like, you can still explore the codebase and the issue yourself. Feel free to review the code if you wish.
Uh oh!
There was an error while loading. Please reload this page.
Description:
The "Resend Verification Email" feature on the Rocket.Chat profile page can be exploited to send an unlimited number of verification emails in a short period of time. By copying the network request triggered by the "Resend" button and programmatically executing it in a loop (e.g., 1000 times), the server sends a verification email for each request without any rate limiting or throttling in place. This can result in email spam and potentially overload the mail server, leading to degraded performance or service disruption.
Steps to reproduce:
Navigate to: https://open.rocket.chat/account/profile
Below the email input, there's a "Resend Verification Email" button.
Click the button 3–4 times — you’ll receive the same number of verification emails.
Open your browser’s Network tab, and copy the fetch or cURL request for the resend action.
Using the browser console (or any script environment), run the same request in a loop (e.g., 1000 times).
Example:
Expected behavior:
Ideally, add protections like:
Minimum cooldown period (e.g., 3 email per X minutes)
CAPTCHA after repeated requests
Backend rate limiting and abuse prevention
Actual behavior:
The server sends a separate email for every request, even if they are triggered in rapid succession.
There are no rate limits, cooldowns, or CAPTCHA to prevent abuse.
This allows an attacker to flood the mail server, potentially causing performance degradation or a denial-of-service condition.
Server Setup Information:
Client Setup Information
Additional context
Relevant logs:
The text was updated successfully, but these errors were encountered: