[FD] Grindr v2.1.1 iOS & Account System - Breach Attack Vulnerability

Document Title: =============== Grindr v2.1.1 iOS & Account System - Breach Attack Vulnerability References (Source): ==================== http://ift.tt/1FJUPu0 Release Date: ============= 2015-05-03 Vulnerability Laboratory ID (VL-ID): ==================================== 1420 Common Vulnerability Scoring System: ==================================== 6.7 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://ift.tt/1dXsnmS ) Abstract Advisory Information: ============================== The Vulnerability Laboratory Research Team discovered the well known Breach Attack issue in the official Grindr v2.1.1 iOS mobile application and connected account system. Vulnerability Disclosure Timeline: ================================== 2015-01-23: Researcher Notification & Coordination (Benjamin Kunz Mejri - Evolution Security) 2015-01-23: Vendor Notification (Grinder - Bug Bounty Program) 2015-02-12: 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) Discovery Status: ================= Published Exploitation Technique: ======================= Remote Severity Level: =============== High Technical Details & Description: ================================ The grindr v2.1.1 & connected account system is vulnerable to the famous `breach attack`. Remote and local attackers can leverage data leaked by compression to recover targeted sections of the plain-text, inject partial plain-text into application-side or client-side victim requests or aeasure the data size of encrypted traffic of the mobile application and connected account system. The following conditions must match to become a target of the issue ... - Become served from a server that uses HTTP-level compression - Reflection of user-inputs in HTTP responses (context body) - Reflect a secret data (token, csrf-x) in HTTP response bodies The vulnerability affects the ./user module of the server online-service. The following issues are matching to grant the successful exploitation ... - We verified that the page content is served via HTTPS protocol - We verified that the server is using the HTTP-level compression - We verified that URL encoded GET input locale was reflected into the HTTP response context body - We verified that the HTTP response contains in the body a secret token named authenticity_token that is already known as broken of the reports due to the pentest Proof of Concept (PoC): =======================

Source: Gmail -> IFTTT-> Blogger