![]() Issue #1 - ADB Client Stack Buffer Overflow Two issues were discovered during the audit: a stack buffer overflow and a failure to opt into security hardening features present in modern compilers. When used on a multi-user system, these design decisions leave much to be desired. Many developers commonly run the ADB Server with root privileges and ADB Client as a normal user. Since the Server listens on a TCP port, other users on a multi-user system can use the server to communicate with connected devices. Though default versions of Android >= 4.2.2 require authentication between the ADB Server and ADB Daemon, no authentication is required between the Client and Server. The communications channels can be summarized in the following ASCII diagram: Still, some commands like “adb devices” operate entirely within the host computer (between the Client and Server only). When using various options within the client, communications go through the ADB Server and to the ADB Daemon. It is the “adb” command that is used by a developer (or within various developer tools) to access an Android device. The ADB Client runs on the development machine too. Among other things, it implements port forwarding and maintaining a persistent connection to devices connected to the host computer. This component is mostly transparent to the user and is only visible when first running the “adb” command or when using the “start-server” and “kill-server” commands. The ADB Server runs on the development machine. As the name of the setting suggests, it enables communicating with the device over USB, but also supports using a TCP port for communications. Whether or not it runs is controlled by the “USB Debugging” setting inside an Android device’s settings menu. The ADB Daemon runs on an Android device. The architecture of ADB is broken into three components. ![]() It is perhaps the most instrumental tool since it facilitates communication between a host computer (the development machine) and an Android device. BackgroundĪndroid Debug Bridge (ADB) is an official development tool provided by Google. When combined together, these issues can allow an unprivileged local user to gain access to the account of someone that uses the ADB tool. Two Security Issues Found in the Android SDK Tools byĭuring an audit of the Android ADB source code, two security issues within the Android SDK Platform Tools were discoverd. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |