A Dangerous Device
Our stories are based on real events encountered by Raxis engineers. Some details have been altered or omitted to protect customer identities.
Over the years our team has tested everything from Appstore classics to one-off vertical use cases stacked to the selfie-cam with proprietary code, and sometimes even specialized hardware. This was one such occasion where we assessed an internal point of sales application running on a custom Android-based device.
While testing apps on a proprietary device, our team discovered that the device allowed USB debugging, which let our testers attach an **Android Debug Bridge (ADB)**and execute commands at the operating system level, outside of the application’s security controls. This misconfiguration, along with a missing critical patch, allowed our team to escalate privileges to root on the device and to extract application files. Using these exposures, our team bypassed our customer’s proprietary application view to run any commands they wished on the device.
At first glance, you might assume that custody affords security. After all, only employes had authorized access and credentials to the devices. The applications on this device took payment info such as credit cards for processing as well as customer Personally Identifiable Information (PII). With these flaws, a malicious employee could configure the device to use an intermediary proxy to intercept sensitive data from the device or deliver other localized payloads. While conducting the on-site assessment, our team also observed the devices stored unprotected and openly accessible when not in use. Brazen customers could take them, make some nefarious changes, and then return them to later reap the rewards.