You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you make a request through this package to the Mailchimp API, and the API returns an error, the Error JSON contains the Basic Auth token. You can extract this token and make requests without knowing the API key.
My question/issue is: Does Mailchimp return the Auth token by itself, or is it included by this package to the error response? If so: why? Including the Auth token in your error response creates a security issue, where your access token can be stolen.
Let me know, thanks ;)
The text was updated successfully, but these errors were encountered:
The rejected error contains the full response object from request, which could contain data that should not be exposed the the client.
I would be hesitant to change the error content, as much existing error handling depends on it. I would also argue to always be careful when returning raw errors to the client.
I think the best solution would be to have user friendly message on the error, that is safe and useful to send to end users. I will gladly accept a PR for that :)
When you make a request through this package to the Mailchimp API, and the API returns an error, the Error JSON contains the Basic Auth token. You can extract this token and make requests without knowing the API key.
My question/issue is: Does Mailchimp return the Auth token by itself, or is it included by this package to the error response? If so: why? Including the Auth token in your error response creates a security issue, where your access token can be stolen.
Let me know, thanks ;)
The text was updated successfully, but these errors were encountered: