Here's a detailed write-up of the EAP bug that affected all Apple devices (except watchOS), CVE-2019-6203. It includes a deep dive into MSCHAPv2 https://sensepost.com/blog/2019/understanding-peap-in-depth/ … there's some code at https://github.com/sensepost/understanding-eap … too
I am. Not sure how to approach next steps though. Because we’d need a way to scale EAP state machine tests across multiple devices. A fuzzing rig and several devices might be one way. But I’m not sure the intermediate steps to get there just yet. Any ideas?
-
-
There are techniques to extract a simplified state machine from implementations using black-box testing (with open source code available for that). Might be interesting to use that as a first step, and then use traditional fuzzing in each discovered state.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.