Loading HuntDB...

Unauthorized access to the slack channel via inside.gratipay.com/appendices/chat

None
G
Gratipay
Submitted None
Reported by 7h0r4pp4n

Vulnerability Details

Technical details and impact analysis

Improper Authentication - Generic
# Summary It is possible to force send invites for gratipay slack channel to arbitary email ids with no bruteforce limit. This is done by modifying the `coc` parameter to `1` in the POST data sent from https://inside.gratipay.com/appendices/chat # Description Sending a post request with `coc` parameter set to `1` appears to be bypassing some validation that is being done in the server. Without the same, the server responds with `Woot. Check your email` to the requests. **Request** ``` POST /invite HTTP/1.1 Host: gratipay-slackin.herokuapp.com Content-Type: application/json Content-Length: 36 {"coc":1,"email":"[email protected]"} ``` **Response** ``` HTTP/1.1 400 Bad Request Server: Cowboy Connection: keep-alive X-Powered-By: Express Content-Type: application/json; charset=utf-8 Content-Length: 93 Date: Sat, 06 May 2017 22:33:39 GMT Via: 1.1 vegur {"msg":"You have already been invited to Slack. Check for an email from [email protected]."} ``` Even though the response is a `400 Bad Request`, an invite email is received from `"Slack" <[email protected]>` with the subject `Paul Kuruvilla has invited you to join a Slack team`. Whatever the validation may be, this allows invites to be forced sent to arbitary email ids with no brute force limit. # Steps To Reproduce * Send the post data with an arbitary email id * An invite to the gratipay slack channel `gratipay.slack.com` will be received at that email account # Supporting References: * https://gratipay.slack.com/team/dobum

Report Details

Additional information and metadata

State

Closed

Substate

Informative

Submitted

Weakness

Improper Authentication - Generic