4.9 • 696 Ratings
🗓️ 17 March 2023
⏱️ 7 minutes
🧾️ Download transcript
Click on a timestamp to play from that location
0:00.0 | Hello and welcome to the Friday, March 17th, 2020, |
0:04.5 | edition of the Sands and at Storm Center's Stormcast. My name is Johannes Ulrich, |
0:10.2 | and today I'm recording from Jacksonville, Florida. |
0:14.1 | Today we got a great Malware Reverse Engineering diary from Xavier. |
0:19.8 | Xavier is writing about an Excel spreadsheet that he found. |
0:23.6 | The spreadsheet is mostly in Chinese, looks like some kind of invoice, and it's interesting |
0:30.5 | in that it uses, well, not a totally uncommon, but a little bit unusual these days, a way |
0:37.2 | of actually executing a code. It's not going |
0:40.7 | the normal macro route or such. Instead, it's using the relatively old now, but sadly still |
0:48.8 | used and sometimes effective equation editor vulnerability. Now, in order to exploit this vulnerability, we don't have |
0:56.7 | like visual basic or something like this in the Excel spreadsheet. Instead, we do have some |
1:03.8 | shell code, so essentially a bytecode. And Xavier walks you through how to analyze this type of code, how to get started, how to find it, |
1:14.1 | and then also how to run it through the shell code debugger, which I believe Xavier has written about before to actually figure out what's going on with this code and what it is trying to accomplish, which also |
1:28.6 | then points to the equation editor vulnerability as the actual exploit being used in order to |
1:35.7 | start this particular software. But you see, for example, also IP address and such that are |
1:42.2 | becoming pretty apparent as you're looking at this code. |
1:46.7 | The advantage, of course, is, well, you could just run this particular Excel spreadsheet, |
1:52.0 | but that's always a little bit risky. |
1:54.1 | You may also not have the right old version of Excel sitting around in order to quickly execute this particular piece of malware. |
2:03.4 | So sometimes it's safer and often also more conclusive if you're reverse analyzing the actual |
2:10.9 | code. |
2:11.7 | It's always easy to miss something if you're just executing the code because you may not trigger all the particular |
... |
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.