how google was pwned: in-depth look into the aurora attacks

15
In-Depth Look into the Aurora Attacks

Upload: northeast-ohio-information-security-forum

Post on 08-Jun-2015

1.985 views

Category:

Technology


1 download

DESCRIPTION

Presented at the February 2010 meeting of the Northeast Ohio Information Security Forum by Josh Kelley, Enterprise Security Analyst for a Fortune 1000 company.

TRANSCRIPT

Page 1: How Google Was Pwned: In-Depth Look into the Aurora Attacks

In-Depth Look into the Aurora Attacks

Page 2: How Google Was Pwned: In-Depth Look into the Aurora Attacks

What makes Aurora Impressive

It weaves together targeted Social Engineering attacks, Zero-Day exploits, and malware to successfully compromise the networks of over 20 major international corporations including the almighty Google.

Page 3: How Google Was Pwned: In-Depth Look into the Aurora Attacks

Two Separate Attack Vectors

 Social Engineering – Focused and precise

 Zero-day exploits – Internet Explorer

Page 4: How Google Was Pwned: In-Depth Look into the Aurora Attacks

Social Engineering Vector

 Several key things were done to increase the success of the spear-phishing emails:  Certain individuals within the companies

were targeted.   Friends of the targeted individuals were

targeted as well.   The targets are thought to have elevated

privileges within the companies (Sysadmins, developers, etc.)

Page 5: How Google Was Pwned: In-Depth Look into the Aurora Attacks

The Zero-Day Exploit

 Microsoft Security Bulletin MS10-002

 Affects Internet Explorer 5, 6, 7, and 8

 HTML Object Memory Corruption

Page 6: How Google Was Pwned: In-Depth Look into the Aurora Attacks

Why it works

  IE has a bug in handling deleted objects

 Allows the attacker to inject malicious code that was in previously deleted object.

Page 7: How Google Was Pwned: In-Depth Look into the Aurora Attacks

The heap spray

 Attacker utilizes heap spray technique to put the payload in memory

Page 8: How Google Was Pwned: In-Depth Look into the Aurora Attacks

Core of the exploit

Page 9: How Google Was Pwned: In-Depth Look into the Aurora Attacks

Exploit Flow

 HTML loads the image   JavaScript deletes it (Function EV1)  Then replaces it with a memory address

(Function EV2)  Which hits the Heap Spray  And executes the payload

Page 10: How Google Was Pwned: In-Depth Look into the Aurora Attacks

DEP in a nutshell

 Data Execution Prevention (DEP) renders buffer overflows harder to exploit due to the fact it adjusts stacks to read-only.

 DEP was often surprisingly hard to bypass in browser exploits and typically made heap spray attacks fairly difficult if not impossible.

Page 11: How Google Was Pwned: In-Depth Look into the Aurora Attacks

ASLR in a nut shell

 Most exploits heavily rely off of hijacking execution flow and typically are very reliant on memory addresses.

 ASLR randomizes the memory addresses each reboot so that the attacker can’t typically predict the memory address to head over to.

Page 12: How Google Was Pwned: In-Depth Look into the Aurora Attacks

Scary Stuff

 The Aurora Attack Bypassed Data Execution Prevention (DEP)

Page 13: How Google Was Pwned: In-Depth Look into the Aurora Attacks

Even Worse

 DEP + Address Space Location Randomization (ASLR) was just recently bypassed on Windows 7 + IE 8

 The once impossible to bypass, can now be bypassed.

Page 14: How Google Was Pwned: In-Depth Look into the Aurora Attacks

So what this means…

 Focused and organized attacks are on the rise….

 Attackers will continue to get in through the easiest route.

 A combination of zero-days and the human element was the root cause for the success of this attack.

Page 15: How Google Was Pwned: In-Depth Look into the Aurora Attacks

How to prevent

 This exploit has already been patched, make sure you update.

  IE is a large target, consider moving to Firefox with No-Script enabled.

 Kernel hooking HIPS could have potentially stopped this attack.