4.9 • 696 Ratings
🗓️ 21 June 2016
⏱️ 5 minutes
🧾️ Download transcript
Click on a timestamp to play from that location
| 0:00.0 | Hello, welcome to the Tuesday, June 21st, 2016 edition of the Santernut Storm Center's Stormcast. |
| 0:07.5 | My name is Johannes Ulrich, and the day I'm recording from Jackson, Florida. |
| 0:12.0 | Lately Swift, the international money transfer system, of course, was in the news quite a bit because some banks got compromised and the system was used for illicit |
| 0:24.6 | money transfers. Well, of course, with any news like that, we typically do see Malever tag on to |
| 0:33.8 | that news. In this latest case, we saw quite a number of email messages today that claimed |
| 0:41.7 | to be a swift payment notice with an attachment. The attachment itself looked like a PDF. |
| 0:48.9 | You couldn't really read it, so you were enticed to click on the link instead to actually see |
| 0:53.6 | what's happening, which |
| 0:54.7 | would then download a straight executable. |
| 0:58.8 | And as usual, the executable itself was hosted on a compromised word press instance. |
| 1:05.6 | That one instance, of course, has been shut down now, but there are likely others still going around. |
| 1:12.4 | Virus totals score on this particular attachment wasn't great. |
| 1:16.3 | It was six out of 55 when we originally saw this particular matter. |
| 1:23.1 | But of course, an executable like this should never make it to an end user as a simple email attachment. |
| 1:30.2 | Any kind of mail filter should quarantine executables that are attached to emails. |
| 1:37.3 | And OpenSL fixed a number of integer overflow vulnerabilities that have been reported by Redhead. |
| 1:45.7 | Now at this point the fix is only available via the GitHub repository for OpenSSL and via some |
| 1:54.4 | of the Linux distributions I don't see right now an actual fix on the open Zell side. |
| 2:01.6 | The latest version they have up there is still the update from May, but this may change soon. |
| 2:09.6 | It's not clear how many of these issues were actually exploitable. |
| 2:13.6 | Inager overflows are tricky, but the basic problem here is that if you do pointer arithmetic |
| 2:21.3 | and add integers together and you exceed the maximum amount of memory attressible, it may |
... |
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.