Eternal · Report #952501
Solr Injection in `user_id` parameter at :/v2/leaderboard_v2.json
Summary
@zzzhacker13 identified a Solr Injection on the user_id parameter at :/v2/leaderboard_v2.json. Our team analyzed internally and found that only fq={injection} was possible on the Solr endpoint, hence the Solr injection was of low impact since there was no way to escalate it to exfiltrate data, one could have just changed the filter query but it wasn't possible to update the fields or anything with these methods.
After the report from @zzzhacker13, the team started analyzing the endpoint and discovered an SQLi (boolean based blind SQLi) on another parameter in the same codebase. We went ahead and fixed the issue. The SQL injection, however, was critical as per our internal metrics, hence we considered this to be critical because it was discovered as an indirect effect of this report and rewarded the max bounty as per our policies.
| Action | Timeline (6 Aug, 2020) |
|---|---|
| Reported | 18:18 IST |
| Investigation started | 18:23 IST |
| Report validated | 18:30 IST |
| Initial contact | 18:56 IST |
| SQLi identified (internally) | 19:08 IST |
| Triaged | 19:12 IST |
| Patch PR released and merged | 19:40 IST |
| Patch deployed | 22:00 IST |
| Severity updated | 22:51 IST |
| Rewarded | 23:12 IST |
Thanks, Zomato Security Team
How it was found
The write-up for this report has not been downloaded yet, or the program disclosed it without one. Read it on HackerOne.