URL filter bypass in Enterprise Grid

Disclosed: 2020-02-14 00:18:18 By akaki To slack
Low
Vulnerability Details
# URL filter bypass in Enterprise Grid ## Description Slack Enterprise Grid seems to be able to add arbitrary column to the profile of the account. In my company there is a おすすめランチ (My Favorite Lunch) column, and we can set the URL of the website and Display text. {F429131} {F429132} Only the `http:` or `https:` scheme can be set in the URL, and other schemes can not be set by input validation. {F429133} However, since input validation exists on the client side, we can bypass this validation by changing the profile setting request. ```diff POST /api/users.profile.set HTTP/1.1 Host: example-corp.slack.com ... -----------------------------7110134921404748136166706634 Content-Disposition: form-data; name="profile" -{"real_name":"Akaki Tsunoda","title":"","phone":"03-9999-0000","fields":{"XfABVBP467":{"value":"https://www.mcdonalds.com","alt":"McDonald's"}}} +{"real_name":"Akaki Tsunoda","title":"","phone":"03-9999-0000","fields":{"XfABVBP467":{"value":"tel://03-9999-0000","alt":"McDonald's"}}} -----------------------------7110134921404748136166706634 ... ``` {F429134} I took screenshots on browser, so an illegal URL is displayed, but it is not displayed in mobile apps. ## Impact In the case of using the `tel:` scheme, the victim who clicked on the link included in the attacker's profile inadvertently call the attacker. In the future attackers may exploit Slack or other app's deep linking (Custom URL Scheme). **Note:** I could not execute JavaScript because I could not use `javascript:` or `data:` scheme by server side input validation.
Actions
View on HackerOne
Report Stats
  • Report ID: 500348
  • State: Closed
  • Substate: resolved
  • Upvotes: 31
Share this report