This post documents my negative experience with the servers.guru vulnerability disclosure / bug bounty process. I am writing this publicly because private communication led nowhere, and I believe security researchers deserve honesty and transparency.
The Short Version
-
I submitted two legitimate security vulnerabilities
-
Both had real-world impact
-
Both were clearly explained with reproduction steps
-
No payment was made
-
No convincing technical justification was given
You can decide what that says about the program.
Vulnerability #1: OTP Reuse (Authentication Broken)
Category: Authentication / Logic Flaw
Severity: High
servers.guru implemented OTP in a way that defeats the entire purpose of OTP.
What Was Wrong
The same OTP could be reused multiple times instead of being invalidated after first use.
This is not a “best practice” issue.
This is OTP 101.
Why This Matters
-
OTPs are meant to be one-time
-
Reuse allows replay attacks
-
Any intercepted or logged OTP becomes reusable
-
This directly weakens account security
I provided:
-
Step-by-step reproduction
-
Clear explanation of impact
-
Proof that the OTP was reusable
Despite this, the issue was dismissed and unpaid.
Vulnerability #2: CSRF on Email Change (Account Takeover Vector)
Category: CSRF
Severity: High
The email change endpoint lacked proper CSRF protection.
What This Enables
If a logged-in user visits a malicious page, an attacker can:
-
Change the victim’s email address
-
Trigger password resets
-
Lock the victim out of their account
This is a classic account takeover scenario.
What I Provided
-
Proof-of-concept
-
Attack scenario
-
Clear explanation of impact
The response?
No reward. No meaningful explanation.
The Real Problem: Process & Accountability
Bug bounty programs live or die by trust.
In this case:
-
Reports were submitted responsibly
-
Vulnerabilities were real and reproducible
-
Communication lacked clarity
-
Rejections felt arbitrary and dismissive
When programs accept reports, fix issues, but refuse to compensate researchers without technical justification, it sends a clear mess
Your time and expertise are disposable.
Why This Feels Bad Faith
Let’s be blunt:
-
OTP reuse is not debatable
-
CSRF on email change is not theoretical
-
These are not “informational” issues
-
These are not “out of scope” tricks
If this is how valid reports are handled, calling it a “bug bounty program” is misleading.
Advice to Other Researchers
Based on my experience:
-
Do not assume good faith
-
Document everything
-
Be prepared for rejection regardless of validity
-
Decide carefully whether servers.guru is worth your time
Your effort may not be respected
Comments
Post a Comment