Therefore I reverse engineered two dating apps.

posted in: News | 0

Therefore I reverse engineered two dating apps.

And I also got a zero-click session hijacking along with other enjoyable weaknesses

On this page I reveal a number of my findings throughout the reverse engineering regarding the apps Coffee Meets Bagel additionally the League. I’ve identified a few critical weaknesses through the research, all of these have now been reported to your vendors that are affected.


In these unprecedented times, a lot more people are escaping in to the world that is digital deal with social distancing. Of these right times cyber-security is much more essential than in the past. From my experience that is limited few startups are mindful of security recommendations. The businesses in charge of a big selection of dating apps are no exclusion. We began this small scientific study to see exactly how secure the dating apps that are latest are.

Accountable disclosure

All severity that is high disclosed in this article have now been reported into the vendors. Because of the time of publishing, matching patches have now been released, and I also have actually individually confirmed that the repairs have been in destination.

I shall perhaps perhaps maybe not offer details within their proprietary APIs unless appropriate.

The prospect apps

We picked two popular apps that are dating on iOS and Android os.

Coffee Suits Bagel

Coffee satisfies Bagel or CMB for brief, established in 2012, is renowned for showing users a number that is limited of each and every day. They are hacked as soon as in 2019, with 6 million records taken. Leaked information included a name that is full current email address, age, enrollment date, and sex. CMB happens to be gaining interest in the past few years, and makes a great candidate with this task.

The League

The tagline when it comes to League application is intelligently” that is“date. Launched time in 2015, it’s a members-only application, with acceptance and fits according to LinkedIn and Twitter pages. The software is more selective and expensive than its options, it is protection on par utilizing the cost?

Testing methodologies

I take advantage of a variety of fixed analysis and analysis that is dynamic reverse engineering. For fixed analysis we decompile the APK, mostly utilizing apktool and jadx. For powerful analysis an MITM is used by me system proxy with SSL proxy capabilities.

A lot of the evaluating is performed in a very rooted Android emulator operating Android os 8 Oreo. Tests that want more capabilities are done on a proper Android os unit operating Lineage OS 16 (predicated on Android os Pie), rooted with Magisk.

Findings on CMB

Both apps have great deal of trackers and telemetry, but i suppose that is simply their state of this industry. CMB has more trackers compared to the League though.

See whom disliked you on CMB with this specific one simple trick

The API carries a pair_action industry in almost every bagel object which is an enum because of the after values:

There is an API that given a bagel ID returns the object that is bagel. The bagel ID is shown into the batch of day-to-day bagels. Therefore if you would like see if some body has refused you, you might decide to try listed here:

This might be a safe vulnerability, however it is funny that this industry is exposed through the API it is unavailable through the software.

Geolocation information leak, not actually

CMB shows other users’ longitude and latitude up to 2 decimal places, which will be around 1 square mile. Luckily this given info is perhaps perhaps not real-time, and it’s also just updated whenever a person chooses to update their location. (we imagine this can be used by the application for matchmaking purposes. I’ve maybe maybe perhaps not confirmed this theory.)

Nevertheless, this field is thought by me might be concealed through the reaction.

Findings on The League

Client-side produced verification tokens

The League does something pretty unusual within their login flow:

The UUID that becomes the bearer is entirely client-side generated. even Worse, the host doesn’t validate that the bearer value is an actual UUID that is valid. It may cause collisions as well as other issues.

I suggest changing the login model so that the token that is bearer created server-side and provided for the client when the host gets the proper OTP through the customer.

Contact number drip via an unauthenticated API

Within the League there is an unauthenticated api that accepts a phone quantity as question parameter. The API leakages information in HTTP reaction code. If the telephone number is registered, it comes back 200 okay , but once the quantity isn’t registered, it comes back 418 we’m a teapot . It can be mistreated in a ways that are few e.g. mapping all the true figures under a location rule to see that is regarding the League and that is maybe not. Or it could cause embarrassment that is potential your coworker realizes you’re on the application.

It has because been fixed once the bug ended up being reported towards the merchant. Now the API merely returns 200 for several demands.

LinkedIn task details

The League integrates with LinkedIn to exhibit a user’s job and employer name to their profile. Often it goes a bit overboard collecting information. The profile API comes back job that is detailed information scraped from LinkedIn, such as the begin 12 months, end 12 months, etc.

Although the software does ask individual authorization to learn LinkedIn profile, an individual most likely will not expect the step-by-step place information become contained in their profile for everybody else to see. I actually do perhaps maybe maybe not believe that form of info is needed for the software to operate, and it may oftimes be excluded from profile information.

Leave a Reply

Your email address will not be published. Required fields are marked *