4.9 • 696 Ratings
🗓️ 6 September 2016
⏱️ 6 minutes
🧾️ Download transcript
Click on a timestamp to play from that location
0:00.0 | Hello, welcome to the Wednesday, September 7th, 2016 edition of the Sansonet Storm Center's Stormcast. |
0:07.9 | My name is Johannes Ulrich Entertainment, recording from Jacksonville, Florida. |
0:12.8 | Google today released the September update for Android. |
0:16.9 | Now, the way they did it this time is they released three different updates and they assigned |
0:23.6 | three different dates to these updates so you know which update you have installed. |
0:29.6 | The first one is labeled with September 1st, but then again, it was released today and it does include the security patches that everybody should apply. |
0:41.2 | The second and the third one only applied to certain hardware components. |
0:46.0 | So if your Android phone doesn't use any of the affected hardware, then it may not need to have that particular security patch. |
0:56.0 | These two are then labeled September 5th and September 6th. |
1:01.0 | So by looking at the exact version date of your Android version, you can then deduct which one of these patches was applied, which of course is for the most part up to the OEM or the carrier you got your device from. |
1:18.6 | For Google Nexus owners, these updates should already be available. |
1:24.6 | Probably noteworthy here are two vulnerabilities that are addressed by the September |
1:29.8 | first patch, one in Lipute Hills, another one in good old favorite media server, both are |
1:36.2 | rated critical for their ability to lead to remote code execution. And SEC Consult did publish an update to a study they did about nine months ago. |
1:48.0 | In this study they crawled the internet for systems that use known default keys. |
1:55.0 | So essentially they connected to S-H servers, they connected to HDPS servers, and based on the public key they got back. |
2:02.6 | They were then able to deduct whether or not this public key was part of a key pair that is well known |
2:09.6 | because it is the default configuration for certain groups of devices. |
2:14.6 | Similar, of course, also for default passwords. |
2:18.0 | Back then a sec consult went to cert and they did a big notification of about 50 |
2:25.3 | different vendors trying to get them to fix the problem. |
2:30.1 | So now nine months later sec consult went back to see how did things change? |
... |
Please login to see the full transcript.
Disclaimer: The podcast and artwork embedded on this page are from SANS ISC Handlers, and are the property of its owner and not affiliated with or endorsed by Tapesearch.
Generated transcripts are the property of SANS ISC Handlers and are distributed freely under the Fair Use doctrine. Transcripts generated by Tapesearch are not guaranteed to be accurate.
Copyright © Tapesearch 2025.