This show has been flagged as Explicit by the host.
WARNING AI GENERATED NOTES AHEAD YMMW
Here is a summary of the recorded training session regarding Android hacking from Hacker Public Radio, including web references for the main topics discussed.
The recording features a security consultant performing a live assessment of an Android application. The consultant uses a custom tool suite called "Jamboree" and various other utilities to test a location-sharing and vehicle management app. The session highlights the increasing complexity of mobile app security, specifically dealing with SSL pinning, encrypted traffic, and anti-tampering mechanisms 1 .
The assessment is conducted on a rooted Android emulator. The speaker utilizes several tools to set up the environment and intercept traffic:
logcat
) to extract user IDs and location data
1
.
The target application is built using Flutter and implements rigorous security controls, including SSL pinning, which prevents standard Man-in-the-Middle (MitM) attacks. The app's HTTP client ignores system and user-installed certificates, and it does not respect device Wi-Fi proxy settings 1 .
To overcome this:
iptables
commands to force all HTTP and HTTPS traffic through the proxy's IP address at the network layer, bypassing the app's proxy ignorance
1
.
1. Geolocation Spoofing
The consultant successfully spoofed the device's GPS location using emulator settings (e.g., setting the location to Puerto Rico or Costa Rica). The application accepted this falsified location data as valid, indicating a lack of server-side verification for location origin 1 .
2. Insecure Direct Object Reference (IDOR) / Broken Access Control
The most critical finding involves the app's user tracking feature.
user_id
.
adb logcat
logs, the consultant extracted their own
user_id
and the
user_id
of a second test account
1
.
user_id
with the target's ID. The server responded with the target's GPS coordinates. This confirms that an authenticated user can track any other user's real-time location if they possess the target's ID
1
.
curl
command to demonstrate the exploit
1
.
3. Potential Information Disclosure
The consultant began testing a feature that allows users to add vehicles by license plate. The concern is that querying a license plate might return excessive PII (Personally Identifiable Information), such as VIN numbers or registration details, beyond what the UI strictly requires (least privilege issue) 1 .
4. Access Control (Calendar Feature)
The consultant tested whether calendar events could be accessed by switching
user_id
parameters. This test resulted in a "401 Unauthorized" error, indicating that this specific endpoint had proper access control in place
1
.
Below are references for the main tools and concepts discussed in the training:
Unless otherwise stated, our shows are released under a Creative Commons Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0) license.
The HPR Website Design is released to the Public Domain.