Therefore I reverse engineered two apps that are dating.

Therefore I reverse engineered two apps that are dating.

Image and video clip drip through misconfigured S3 buckets

Typically for photos or any other asserts, some form of Access Control List (ACL) is in position. A common way of implementing ACL would be for assets such as profile pictures

The main element would act as a “password” to get into the file, in addition to password would simply be offered users who require use of the image. When it comes to an app that is dating it’s going to be whoever the profile is presented to.

I’ve identified several misconfigured buckets that are s3 The League throughout the research. All photos and videos are unintentionally made general general general public, with metadata such as which user uploaded them so when. Generally the application would obtain the pictures through Cloudfront, a CDN on top associated with the S3 buckets. Unfortunately the s3 that is underlying are severely misconfigured.

Side note: as much as i can inform, the profile UUID is arbitrarily produced server-side if the profile is done. Making sure that part is not likely to be really easy to imagine. The filename is managed because of the customer; any filename is accepted by the server. In your client app its hardcoded to upload.jpg .

The seller has since disabled listObjects that are public. Nevertheless, we nevertheless think there must be some randomness into the key. A timestamp cannot act as key.

internet protocol address doxing through website website link previews

Link preview is something this is certainly difficult to get appropriate in great deal of messaging apps. You can find typically three techniques for website website link previews:

The League utilizes recipient-side website link previews. Whenever a note includes a web link to an image that is external the web link is fetched on user’s unit as soon as the message is seen. This will effortlessly enable a harmful transmitter to submit an external image URL pointing to an attacker managed host, obtaining recipient’s internet protocol address as soon as the message is exposed.

A much better solution could be in order to connect the image within the message if it is delivered (sender-side preview), or have actually the server fetch the image and place it when you look at the message (server-side preview). Server-side previews enables anti-abuse scanning that is additional. It may be an improved choice, but nevertheless perhaps maybe perhaps not bulletproof.

Zero-click session hijacking through talk

The software will often connect the authorization header to demands which do not need verification, such as for instance Cloudfront GET needs. It will likewise happily give fully out the bearer token in requests to domains that are external some cases.

Those types of instances could be the image that is external in chat messages. We already know just the software makes use of recipient-side link previews, therefore the demand to your outside resource is performed in recipient’s context. The authorization header is roofed when you look at the GET demand to your image that is external. Therefore the bearer token gets leaked towards the outside domain. When a harmful sender delivers a picture website website link pointing to an assailant managed host, not merely do they get recipient’s internet protocol address, however they additionally obtain victim’s session token. It is a vulnerability that is critical it permits session hijacking.

Observe that unlike phishing, this assault will not need the victim to go through the website link. If the message containing the image website website website website link is seen, the software automatically leaks the session token to your attacker.

This indicates to be always a bug pertaining to the reuse of a international OkHttp customer object. It might be most useful if the designers make certain the software just attaches authorization bearer header in needs to your League API.


I didn’t find any especially interesting weaknesses in CMB, but that will not suggest CMB is more safe compared to the League. (See Limitations and future research). Used to do locate a few safety dilemmas within the League, none of that have been especially hard to find out or exploit. I assume it is actually the mistakes that are common make over and over repeatedly. OWASP top anybody?

As customers we must be aware with which companies we trust with your information.

Vendor’s reaction

I did so get a prompt reaction from The League after giving them a contact alerting them regarding the findings. The S3 bucket setup had been swiftly fixed. One other weaknesses had been patched or at the least mitigated in just a couple weeks.

I do believe startups could undoubtedly provide bug bounties. It really is a good motion, and even more importantly, platforms like HackerOne offer scientists an appropriate way to the disclosure of weaknesses. Regrettably neither of this two apps when you look at the post has program that is such.

Restrictions and research that is future

This scientific studies are maybe maybe perhaps maybe not comprehensive, and may never be regarded as a safety review. A lot of the tests on this page had been done in the community IO degree, and hardly any on the customer it self. Particularly, we did not test for remote rule execution or buffer type that is overflow. In future research, we’re able to look more in to the protection associated with customer applications.

This may be through with powerful analysis, making use of techniques such as for example:

« »

Comments are closed.