Uploaded March 2026 | Updated September 2026, 2 weeks ago
00:00 - Introduction
00:55 - Start of nmap
02:50 - Looking at the Javascript, which a lot of information about the webapp
03:10 - Looking at the pac4j jwt vulnerability (CVE-2026-29000)
05:30 - Looking for the JKS (RSA Public Key), going into the javascript and seeing there is an /api/auth/jwks endpoint
06:50 - Start of creating our python to create a forged JWE Token
15:00 - Troubleshooting our token, it isn't valid yet
18:30 - Crafted a valid token, now it is saying we have an invalid role, looking at the javascript to get the correct information
20:30 - Logged into the application, discovering a credential that lets us SSH into the box
22:30 - Poking at the source of the java app, finding more passwords but doesn't really help us
24:20 - Discovering a CA Private Key, with a note saying its valid for SSH, looking at SSH's config
25:50 - Generating a SSH Key, then signing it with the CA giving us the principal of "root" and logging in
28:30 - Little bit of extra information about SSH Key Signing, the AuthorizedPrincipalsFile
00:00 - Introduction
00:55 - Start of nmap
02:50 - Looking at the Javascript, which a lot of information about the webapp
03:10 - Looking at the pac4j jwt vulnerability (CVE-2026-29000)
05:30 - Looking for the JKS (RSA Public Key), going into the javascript and seeing there is an /api/auth/jwks endpoint
06:50 - Start of creating our python to create a forged JWE Token
15:00 - Troubleshooting our token, it isn't valid yet
18:30 - Crafted a valid token, now it is saying we have an invalid role, looking at the javascript to get the correct information
20:30 - Logged into the application, discovering a credential that lets us SSH into the box
22:30 - Poking at the source of the java app, finding more passwords but doesn't really help us
24:20 - Discovering a CA Private Key, with a note saying its valid for SSH, looking at SSH's config
25:50 - Generating a SSH Key, then signing it with the CA giving us the principal of "root" and logging in
28:30 - Little bit of extra information about SSH Key Signing, the AuthorizedPrincipalsFile







![Intercepting Android App Traffic with BurpSuite
00:00 - Introduction, talking about RouterSpace and why we cant just do what we did in that video
01:25 - Installing Genymotion, Virtual Box, and ADB; while talking about why I dont use Android Studio/AVD. Simply because genymotion just works.
02:05 - Make sure you upgrade your memory, processors, and enable Virtualization in your VM Settings!
02:30 - Running Genymotion and starting a Pixel 3 XL
03:37 - Converting BurpSuites Certificate to PEM Format with openssl x509 -inform der -in [name of cert] -out burp.pem
04:20 - Renaming the certificate to 9a5ba575.0, and showing how we got that name
06:00 - Starting the device and showing the certificate authorities
07:00 - Copying the certificate to /system/etc/security/cacerts/, and showing how to remount to rw
08:10 - Showing how to set the proxy through both the GUI and via ADB
09:50 - Installing GAPPS
10:30 - Showing how to unset the proxy from ADB
11:00 - Creating an alias to set and unset the proxy via adb
12:00 - Opening the google play store and logging in and install Wayzn to see if we can intercept traffic
15:20 - Showing we intercepted traffic from Wayzn, then installing Instagram
16:50 - Attempting to login to instagram and getting an error message
17:20 - Setting up Frida both on our computer and android device
19:20 - Showing Frida is working, getting ps output from the android device
19:55 - Downloading the instragram ssl pinning bypass script
21:20 - Using frida to start instagram and loading the script to bypass the SSL Checking
22:15 - Setting the proxy and showing us intercept instagram traffic Intercepting Android App Traffic with BurpSuite](https://i.ytimg.com/vi/xp8ufidc514/mqdefault.jpg)


