Grindr v2.1.1 iOS Bounty #1 - (Session) Auth Bypass Vulnerabilities
Vulnerability Laboratory ID (VL-ID):
Common Vulnerability Scoring System:
Product & Service Introduction:
Grindr, which first launched in 2009, has exploded into the largest and most popular all-male location-based social network out there.
With more than 5 million guys in 192 countries around the world -- and approximately 10,000 more new users downloading the app
every day -- you’ll always find a new date, buddy, or friend on Grindr. Grindr is a simple app that uses your mobile device’s
location-based services to show you the guys closest to you who are also on Grindr. How much of your info they see is
entirely your call.
(Copy of the Vendor Homepage: http://grindr.com/learn-more )
Abstract Advisory Information:
The Vulnerability Laboratory Research team discovered a redirect vulnerability and a token auth bypass issue in the official Grindr v.2.1.1 iOS mobile web-application.
Vulnerability Disclosure Timeline:
2015-01-22: Researcher Notification & Coordination (Benjamin Kunz Mejri - Evolution Security)
2015-01-22: Vendor Notification (Grinder - Bug Bounty Program)
2015-02-04: Vendor Response/Feedback (Grinder - Bug Bounty Program)
2015-04-01: Vendor Fix/Patch (Grindr Developer Team - Reward: x & Manager: x)
2015-05-04: Public Disclosure (Vulnerability Laboratory)
Product: Grinder - iOS Mobile Web Application (API) 2.2.1
Technical Details & Description:
Multiple web vulnerabilities has been discovered in the official Grindr v2.1.1 iOS mobile web-application.
The first issue is that due to the password change the app is allowed to request through the browser the service.
Attacker with a privileged account can request via POST and intercept the request to get a valid token.
After the token has been saved the attacker is able to change the email value. After changing the email value the
attacker is able to get access to another users/administrator account. To exploit the bug the session needs to be tampered,
the request needs to be intercepted, stoped to store the valid token. After the token is stored the attacker can use an
mobile application tamper to inject the new email value. The fail was that the token is not connected to the session itself
but the request requires only a valid token. In the password change module were the same problem occurs is no token available
in the request that send you through the iOS safari browser to the account system.
[+] Email Change
[+] Password Change
The second issue is located in the file location but in the redirect_url parameter. Remote attackers can inject external sources
to redirect a victim through the application to another malicious external source. The bug is in the same location which allows
remote attackers or local privileged user accounts to exploit the vulnerability in combination with the token and email issue above.
Proof of Concept (PoC):
The session token reset auth bypass issue can be exploited by local low privileged user accounts without user interaction.
Email Change PoC:
Password Change PoC: NO TOKEN REQUIRED!!!!
The redirect web vulnerability that is exploitable in the success module can be exploited remote accounts without low or medium user interaction.
Solution - Fix & Patch:
The token vulnerability can be patched by a secure implementation that disallows to review or to capture the session information.
A valid token is not allowed to reset other account and needs to be connected to the session id information and co. to prevent an account system compromise.
The redirect web vulnerability cna be patched by a secure parse and encode of the vulnerable redirect_url value in the success module.
Restrict the request and disallow external source to prevent exploitation.
The security risk of the token issue in the reset and change function is estimated as critical
The security risk of the redirect web vulnerability in the account system success is estimated as medium.
The issue can be combined with the token vulnerability to compromise the account system.
Credits & Authors:
Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri ([email protected]) [www.vulnerability-lab.com]
Disclaimer & Information:
The information provided in this advisory is provided as it is without any warranty. Vulnerability Lab disclaims all warranties, either expressed
or implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability-Lab or its suppliers are not liable
in any case of damage, including direct, indirect, incidental, consequential loss of business profits or special damages, even if Vulnerability-Lab
or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for
consequential or incidental damages so the foregoing limitation may not apply. We do not approve or encourage anybody to break any vendor licenses,
policies, deface websites, hack into databases or trade with fraud/stolen material.
Domains: www.vulnerability-lab.com - www.vuln-lab.com - www.evolution-sec.com
Contact: [email protected] - [email protected] - [email protected]
Section: magazine.vulnerability-db.com - vulnerability-lab.com/contact.php - evolution-sec.com/contact
Social: twitter.com/#!/vuln_lab - facebook.com/VulnerabilityLab - youtube.com/user/vulnerability0lab
Feeds: vulnerability-lab.com/rss/rss.php - vulnerability-lab.com/rss/rss_upcoming.php - vulnerability-lab.com/rss/rss_news.php
Programs: vulnerability-lab.com/submit.php - vulnerability-lab.com/list-of-bug-bounty-programs.php - vulnerability-lab.com/register/
Any modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability Laboratory. Permission to
electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other media, are reserved by
Vulnerability-Lab Research Team or its suppliers. All pictures, texts, advisories, source code, videos and other information on this website
is trademark of vulnerability-lab team & the specific authors or managers. To record, list (feed), modify, use or edit our material contact
([email protected] or [email protected]) to get a permission.
Copyright © 2015 | Vulnerability Laboratory - [Evolution Security GmbH]™
-- VULNERABILITY LABORATORY - RESEARCH TEAM SERVICE: www.vulnerability-lab.com CONTACT: [email protected] PGP KEY: http://www.vulnerability-lab.com/keys/admin@vulnerability-lab.