4.9 • 696 Ratings
🗓️ 15 October 2018
⏱️ 6 minutes
🧾️ Download transcript
Click on a timestamp to play from that location
| 0:00.0 | Hello, welcome to the Monday, October 15th, 2018 edition of the Sandtonet Storm Center's Stormcast. My name is Johannes Ulrich, and I'm recording from McLean, Virginia. |
| 0:13.1 | I have mentioned several times in this podcast how important it is to track dependencies in your applications, particular third-party libraries that |
| 0:25.3 | you are including in your code. Now often the focus here is open source libraries, but it |
| 0:32.5 | affects commercial libraries just as well. One reason example is branch.io. |
| 0:39.3 | Branch.io allows mobile applications to track users and essentially get things like |
| 0:46.8 | refer statistics and the like, and apparently their library suffered from a cross-site |
| 0:52.7 | scripting vulnerability. |
| 1:01.6 | This issue was first discovered at the dating site Tinder, but then as it became known that branch.io's code was actually the vulnerable code. |
| 1:05.4 | It turned out that many, many other sites are affected by the same vulnerability, potentially affecting hundreds |
| 1:13.5 | of millions of users. |
| 1:15.4 | Now, you may say, hey, it's just a cross-site scripting vulnerability, but don't underestimate |
| 1:20.8 | cross-site scripting vulnerabilities. |
| 1:22.3 | This particular vulnerability was exploitable on personal profile pages, so this could certainly be used |
| 1:30.2 | to either leak personal information or to even take over accounts. And pacemaker manufacturer |
| 1:38.4 | metronic is in the news again regarding the programmers for their pacemakers. This is actually an older vulnerability. |
| 1:47.3 | I believe it was discovered back in February and it affects these programmers. So it doesn't |
| 1:52.5 | affect the pacemaker itself, but these programmers are used to configure pacemakers. |
| 1:59.8 | And up to now, it was possible to remotely update these programmers. |
| 2:04.6 | But apparently this update process wasn't secure. |
| 2:09.6 | Now, the original fix was to just use a VPN for the update. |
| 2:15.6 | And the way this apparently worked was that the programmer did establish a VPN |
| 2:20.1 | connection to Metronics Software Delivery Network and then the update happened. The problem was |
... |
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.