3 ms·
How was this vulnerability able to be exposed in the first place if the API is communicating over SSL?
by blantonl 11y ago
How was this vulnerability able to be exposed in the first place if the API is communicating over SSL?
- peterkelly 11y agoYou can intercept your own SSL communications if you create your own certificate authority and add it to the list of trusted CAs on your device. You can then use this to generate SSL certificates for arbitrary domains, and by proxying traffic through your own machine you can grab the plaintext by impersonating the real site. Of course this will only work for devices you have added your CA to; you won't be able to intercept just anyone's traffic. There's an app for OS X called Charles, which automates this process for you, acting as a proxy and generating the fake certificates on-demand. See https://www.charlesproxy.com/documentation/using-charles/ssl-certificates/ https://www.charlesproxy.com/documentation/using-charles/ssl...
- joshmn 11y ago> There's an app for OS X called Charles, which automates this process for you, acting as a proxy and generating the fake certificates on-demand. It's a bit more difficult than just loading up an MITM and generating the certs; if they've pinned (which they have), you have to go a _bit_ deeper than _just_ using an MITM proxy.