Closed
Bug 784363
Opened 13 years ago
Closed 12 years ago
https://support.mozilla.org/en-US/users/api/usernames?term=test parsing usernames
Categories
(support.mozilla.org :: General, defect)
support.mozilla.org
General
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: eusebiu.blindu, Unassigned)
Details
(Whiteboard: [site:support.mozilla.org])
User Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.79 Safari/537.1
Steps to reproduce:
Go to
https://support.mozilla.org/en-US/users/api/usernames?term=test
https://support.mozilla.org/en-US/users/api/usernames?term=a
https://support.mozilla.org/en-US/users/api/usernames?term=b
https://support.mozilla.org/en-US/users/api/usernames?term=c
https://support.mozilla.org/en-US/users/api/usernames?term=d
...
https://support.mozilla.org/en-US/users/api/usernames?term=z
https://support.mozilla.org/en-US/users/api/usernames?term=1
https://support.mozilla.org/en-US/users/api/usernames?term=2
..
https://support.mozilla.org/en-US/users/api/usernames?term=9
https://support.mozilla.org/en-US/users/api/usernames?term=ab
Actual results:
usernames are listed
Expected results:
This can be used to parse large numbers of usernames that can be afterwards attacked using bruteforce
There should be another token in the api calling
Updated•12 years ago
|
Whiteboard: [site:support.mozilla.org]
Comment 1•12 years ago
|
||
usernames are not considered to be private. You can spider the site to collect them all if you wanted. In fact we indicate "Your username will be shown next to your question in our public support forums." during registration.
Comment 2•12 years ago
|
||
You must already be logged in to use this API, and the username itself isn't private info, as Ricky said.
Bruteforce protection should be at the log-in site, not here.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Comment 3•9 years ago
|
||
These bugs are all resolved, so I'm removing the security flag from them.
Group: websites-security
You need to log in
before you can comment on or make changes to this bug.
Description
•