This is part 2 of the article on MS08-078.
Below I'll talk about what this particular invocation of the exploit carried in terms of payloads.
Guide for CIOs, CFOs, and CISOs on why traditional security defenses are failing and how losing the security battle can hurt your business
Inside look at stopping zero-day attacks and advanced persistent threats with FireEye
Look into the changing nature of today's advanced targeted attacks and why traditional IT security is inadequate
Deep dive into spear phishing attacks and what is needed to combat this type of advanced threat
Insight into how FireEye is able to combat even the most sophisticated threats
Overview of the FireEye product family which protects against advanced cyber attacks
This is part 2 of the article on MS08-078.
Below I'll talk about what this particular invocation of the exploit carried in terms of payloads.
Often times I'm asked what actually happens to a system when the browser is exposed to a modern web exploit. By "web exploit", I'm referring to the type of exploit where your browser only need visit a site - no user interaction (like opening a file) is necessary. I thought it might be interesting to take a look at a real-world implementation of the new IE exploit (MS08-078) to see what the payload was. I'm going to break this up into two posts just because of the size of the screenshots.
Copyright © 2006-2014 FireEye, Inc. All rights reserved. Privacy & Cookies Policy | Site Map | Site Credits
