A Blog by Jonathan Low

 

Apr 23, 2018

When You Go To a Security Conference And Its Mobile App Leaks Your Data

Awkward... JL

Sean Gallagher reports in ars technica:

A mobile app built by a third party for the RSA security conference in San Francisco was found to have a few security issues—including hard-coded security keys and passwords that allowed a researcher to extract the conference's attendee list. The conference organizers acknowledged the vulnerability on Twitter, but they say that only the first and last names of 114 attendees were exposed. The vulnerability was discovered by a security engineer who tweeted discoveries during an examination of the  app
A mobile application built by a third party for the RSA security conference in San Francisco this week was found to have a few security issues of its own—including hard-coded security keys and passwords that allowed a researcher to extract the conference's attendee list. The conference organizers acknowledged the vulnerability on Twitter, but they say that only the first and last names of 114 attendees were exposed.
The vulnerability was discovered (at least publicly) by a security engineer who tweeted discoveries during an examination of the RSA conference mobile app, which was developed by Eventbase Technology. Within four hours of the disclosure, Eventbase had fixed the data leak—an API call that allowed anyone to download data with attendee information.
Accessing the attendee list required registering an account for the application, logging in, and then grabbing a token from an XML file stored by the application. Since registration for the application only required an email address, anyone who could dump the files from their Android device could obtain the token and then insert it
into a Web-based application interface call to download attendee names. While the SQLite database downloaded was encrypted, another API call provided that key.
Another SQLite database that can still be pulled down via the application's APIs is not encrypted, and it contains more personal information, including names, addresses, phone numbers, company names, and social media account links. Ars looked at that database, and it appears to contain only vendor and speaker data, so it's likely intentionally insecure because it's less sensitive.
This is the second time an RSA mobile application has leaked attendee data. In 2014, an application built by another developer, QuickMobile, was found by Gunter Ollmann (who was at that time at IOactive) to have a SQLite database containing personal information on registered attendees.

0 comments:

Post a Comment