Android: Bypassing HTTPS certificate pinning
This project is unavailable since it already has been assigned to a seminar student.
Has the smartphone in your pocket become the driver of your daily life? Did you ever wonder which data the installed apps leak in the background?
We are on a mission to reveal the hidden secrets in the (sometimes) nasty byte code of Android apps from professional developers. However, inspections have become a non-trivial task, because many developers started to rely on improved security for data transmissions (HTTPS).
A few problems you'll be confronted with:
- Live-patching of certificate validation measures in apps
(so that they will ignore incomplete chains of trust)
- App configuration patching
(our own certificates need to be implanted and exposed to the operating system)
- Anti-tampering protection
State of the art
There exist tools which can remove security measures on the fly during execution , or statically by manipulating the compiled app code . However, static measures suffer from inherent limitations, e.g., the manipulated apps require a proper resigning which is not possible without the developer's private key.
We found that no tool provides a ``does it all\'' solution.
In this seminar project, we want to explore the possibility of bypassing HTTPS encryption, and if possible, implement strategies against such protections.
Your task will consist of:
- Manual investigation of web communication in Android apps
- Manual patching of apps to override the HTTPS security controls
- Automation of the manual patching
Guiding research questions
- How does HTTPS enforce security?
- What makes a certificate secure?
- How can we override HTTPS security controls in Android apps?
- How can we manipulate Java classes during run time?
 Frida, a hybrid framework for mobile app investigation
 Objection, a framework based on Frida to attack HTTPS protection measures
 Explanation on how Android apps can be repackaged to execute arbitrary commands