On the Insecurities of Mobile D2D File Sharing Applications

Andrei Bytes, Jay Prakash, Jianying Zhou, Tony Q. S. Quek

Abstract

Researchers analyzed the top six Android device-to-device (D2D) file-sharing apps—serving over 1.8 billion users—and discovered 17 new CVEs. The study reveals a dangerous trend: developers are systematically sacrificing encryption and authentication to provide a "seamless" one-click user experience, often leaving user data exposed to anyone in physical proximity.

Introduction

Device-to-Device (D2D) communication, primarily via Wi-Fi Direct, allows users to swap large files quickly without consuming cellular data. However, the native Wi-Fi Direct protocol is notoriously complex, requiring manual PIN entries or button presses that often frustrate users. To stay competitive and capture the "Next Billion Users" (NBU) in emerging markets, app developers have created custom workarounds to make pairing "invisible."

The complex multi-step discovery process of native Wi-Fi Direct.

This paper investigates the hidden cost of this convenience. The authors set out to determine if these "usability favors"—such as skipping password prompts or automatically setting up hotspots—create critical security holes that allow attackers to sniff traffic, inject malicious code, or remotely steal files.

Methodology

The researchers employed a dual-track approach combining rigorous security auditing with human-centric usability testing:

  1. Vulnerability Analysis:
    • Static Analysis: Reverse-engineering apps to identify hard-coded credentials, insecure API calls (like remote storage binding), and vulnerable embedded web server components (e.g., NanoHTTPD).
  2. Dynamic Analysis: Hooking into Java and Android APIs during runtime to inspect cryptography handling and network sockets. The team also used word-list generation to detect clear-text leaks of filenames or hardware addresses.
  3. Usability Study:
    • A study with 43 participants (engineering students and potential NBU users) tasked them with sharing files using various methods.
  4. The System Usability Scale (SUS) and User Journey Mapping (UJM) were used to quantify "pain points," such as the cognitive load of remembering a PIN versus the ease of a QR scan.
  5. Quantification Framework: The authors proposed a new methodology to calculate a "usability score" during the protocol design phase, assigning weights to user interactions (e.g., a simple tap costs 0.1, while recalling a password costs 0.8).

Key Insights and Vulnerabilities

The study focused on the six most-downloaded D2D applications: SHAREit, Xender, Xiaomi MiDrop, Files by Google, Zapya, and SuperBeam. Several critical security patterns emerged:

  • The "Silent Fallback" Trap: When Wi-Fi Direct fails, apps often silently drop back to creating a standard Wi-Fi Access Point. To maintain ease of use, they frequently disable all security (Security: None) or use hard-coded, predictable passwords.
  • Predictable Credentials: Several apps use hard-coded algorithms to derive passwords from the device's hostname, allowing an attacker to independently predict credentials and join the network undetected.
  • Embedded Backdoors: Most analyzed apps (except Files by Google) run background web servers for PC-to-mobile sharing. These servers often lack access control and are vulnerable to Path Traversal and Cross-Site Scripting (XSS).
SHAREit defaulting to 'Security: None' during hotspot setup to simplify the user experience.

Results

The research identified and reported 17 Common Vulnerabilities and Exposures (CVEs). Key findings include:

  • Lack of Encryption: Despite marketing claims, 5 out of 6 apps transmit data unencrypted at the application layer. Only Files by Google consistently used encryption.
  • Remote File Access: In apps like Xender and SHAREit, vulnerabilities allowed for remote file retrieval and the unauthorized upload of malicious files to a victim's device without notification.
  • Quantified UX: UJM analysis confirmed that "insecure" methods (QR codes or automatic pairing) had significantly fewer pain points than secure manual hotspot methods, explaining why developers gravitate toward vulnerable implementations.

Conclusion

The paper argues that security researchers must provide protocol designers with tools to quantify usability before an app is built to prevent the conflict between security and convenience. While the study focuses on Android, it highlights a broader need for better OS-level APIs, like LocalOnlyHotspot, to help developers provide secure D2D connections without resorting to insecure custom workarounds.

Summary updated

Abstract

The number of active users of Wi-Fi Direct Device-to-Device file sharing applications on Android has exceeded 1.8 billion. Wi-Fi Direct, also known as Wi-Fi P2P, is commonly used for peer-to-peer, high-speed file transfer between mobile devices, as well as a close proximity connection mode for wireless cameras, network printers, TVs and other IoT and mobile devices. For its end users, such type of direct file transfer does not incur cellular data charges. However, despite the popularity of such applications, we observe that the software vendors tend to prioritize the ease of user flow over the security in their implementations, which leads to serious security flaws. We perform a comprehensive security analysis in the context of security and usability and report our findings in the form of 17 Common Vulnerabilities and Exposures (CVE) which have been disclosed to the corresponding vendors. To address the similar flaws at the early stage of the application design, we propose a joint consideration of security and usability for such applications and their protocols that can be visualized in form of a customised User Journey Map (UJM).
BibTeX
@misc{bytes2020insecurities,
  author = {Andrei Bytes and Jay Prakash and Jianying Zhou and Tony Q. S. Quek},
  title = {{On the Insecurities of Mobile D2D File Sharing Applications}},
  year = {2020},
  eprint = {2002.03144},
  archivePrefix = {arXiv},
  url = {https://arxiv.org/abs/2002.03144},
}
Figure