3 ms·
(Bug report at https://hackerone.com/reports/5200 https://hackerone.com/reports/5200) From Ryan McGeehan, director of security (user magoo): > This behavior
by peterwwillis 13y ago
(Bug report at https://hackerone.com/reports/5200 https://hackerone.com/reports/5200)
From Ryan McGeehan, director of security (user magoo):
> This behavior is mostly informational to an attacker and does not
> directly increase risk in any significant way
All information leaks are useful to an attacker. By themselves they are harmless, but can be combined with other information to successfully exploit a system.
From bug reporter Shubham Shah (user zero):
> This request can now be replayed unlimited times, with unlimited email
> addresses inputted. Coinbase does not limit the rate of POST requests
> to /transactions/request_money
This should not be possible at all. The reporter must have made a mistake and forgot to mention the X-CSRF-Token needs to be updated each time. If it didn't need to be updated, this would be a basic CSRF vuln.
All this being said, the real flaw here is the lack of rate limiting on transactions, for three reasons:
1. The spam will eventually mount up and ISPs will block their servers for days or weeks.
2. Their network and app stack is subject to DoS attacks unless they rate-limit transactions.
3. Harvesting of e-mail addresses would be stopped by basic rate limiting of email<->user queries.