In July 2015, @hussain submitted a report where a GET request to an internal API endpoint (
/core/api/Map) disclosed details of public maps in a Mapbox user's account. The disclosed information included the name, description, map identifier, geographic center, map layers, date created, and date last modified of all of the public maps in a Mapbox user's account.
No private maps were exposed as a result of this report as the private maps feature was not available until February 2016. No Mapbox user account data such as email address or billing information was disclosed. This vulnerability only affected public maps stored on www.mapbox.com. Data dynamically loaded on to a Mapbox map via XHR or other means was not affected.
Hussain reported success with the following requests on www.mapbox.com:
To take advantage of this vulnerability, an attacker had to supply a valid Mapbox username. They would then make a request to the
/core/api/Map endpoint with the query string
We patched this vulnerability by requiring the value of the
account query string parameter to match the account name of the user that authenticated the request to this endpoint.
We have chosen partial disclosure of this report due to the presence of sensitive information in the researcher's original report. API Bug :- Ability to detect users account information