Didier Stevens

Tuesday 8 November 2011

White Hat Shellcode Workshop: Enforcing Permanent DEP

Filed under: Shellcode — Didier Stevens @ 21:12

Here’s a video of an exercise in my White Hat Shellcode Workshop I gave at Brucon in September.

7 Comments »

  1. What did you use for video capture and text annotation? Nice video btw

    Comment by Jkp — Wednesday 9 November 2011 @ 4:46

  2. That’s fascinating – thank you. I’ve been looking forward to seeing a demo because, regrettably, I couldn’t attend Brucon.

    I know that you’ve published simple-shellcode-generator.py and intended publishing create-remote-thread.py after Brucon. I’m keen to replicate your experiments – do you know when you’ll publish this code? I also saw some slides of the workshop and there was a package “shellcode-workshop.zip”. Do you plan publishing that too?

    I realise that you created this material for the workshop and quite understand it if you decide to delay publication.

    Comment by Iain — Wednesday 9 November 2011 @ 19:32

  3. @Jkp I use VMware Workstation’s Capture Movie feature. And video + subs is produced with avisynth.

    Comment by Didier Stevens — Wednesday 9 November 2011 @ 20:02

  4. @Iain If you search a bit on the Brucon site, you’ll find all you need…

    Comment by Didier Stevens — Wednesday 9 November 2011 @ 20:03

  5. Got the package Didier – thank you. I’ll have a play around with it this weekend!

    Comment by Iain — Thursday 10 November 2011 @ 11:53

  6. I’ve had an interesting time playing around with the code and seeing some of the possibilities. I’m sure some real-life situations will pop into my head where I can use white hat shellcode!

    I realise that CreateRemoteThread is flagged by AVs and, as far as I know, it is still available in Windows 7. I have a couple of questions:

    I assume that, if an application needs to use this API, the AV will flag it as a problem so are there any alternatives that software developers can use? What about alternative methods of DLL injection?

    If CreateRemoteThread is still available in Windows 7, why? Have Microsoft left it there for legacy purposes? Given the fact that AV pick it up if it’s used, what’s the point it being there?

    Comment by Iain — Friday 30 December 2011 @ 14:04

  7. @Iain I’ve not seen a lot of AV products identifying executables that call CreateRemoteThread malware. But there are security products that monitor calls to CreateRemoteThread.

    Comment by Didier Stevens — Saturday 31 December 2011 @ 13:15


RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Connecting to %s

Theme: Rubric. Blog at WordPress.com.

Follow

Get every new post delivered to your Inbox.

Join 86 other followers