Welcome Guest. | Log In| Register | Membership Benefits
  • Email this page E-mail this page
  • |  Print Print this page
  • |   Bookmark and Share

How to Cheat Hardware Memory Access

Researcher Joanna Rutkowska will demonstrate how to derail forensics' search for malware in the OS

Feb 27, 2007 | 02:05 AM

By Kelly Jackson Higgins
DarkReading

Finding rootkits planted in a machine can be like searching for a needle in a haystack, and it's about to get even harder: Researcher Joanna Rutkowska will demonstrate a proof-of-concept at Black Hat DC this week that lets an attacker taint the forensics investigator's best tool for detecting wily rootkits -- hardware-based memory access.

Rutkowksa will show how an attacker could prevent forensics investigators from getting a real image of the memory where the malware resides. "Even if they somehow find out that the system is compromised, they will be unable to get the real image of memory containing the malware, and consequently, they will be unable to analyze it," says Rutkowska, senior security researcher for COSEINC.

Researchers and forensics investigators today rely more on reading hardware-based memory to get an accurate picture of the OS to help detect malware, mainly because it's difficult to find rootkits in today's complex operating systems.

"All rootkit detectors on the market today can be seen as more or less random 'hacks' that check only some limited number of well-known places in the OS," Rutkowska says.

Plus if the system has already been compromised, you can't trust any programs executing on it -- not even the rootkit detector program itself, she says. So hardware-based memory access has emerged as the best way to get a real look at what's going on.

Rutkowska wouldn't reveal details on just how she "cheats" the so-called hardware Direct Memory Access (DMA) forensics method -- she says to tune into her presentation on Wednesday. But she says her POC will disprove the conventional wisdom that the DMA approach is secure.

"I believe that this is going to be the first public presentation of how malware can cheat hardware-based memory acquisition," she says.

There are only a few hardware memory-acquisition cards out there for forensics investigators, including ones from BBN and Komuku, as well as Grand Idea Studio's Tribble, but some investigators instead use a FireWire connection to get RAM images, Rutkowska says.

Rutkowska used FireWire and AMD64-based systems in her research but says it's likely the attack would also work on an Intel-based machine. "The attack itself is not based on any implementation flaw -- it uses only documented features of AMD-based systems, and I anticipate that similar features are present on Intel systems as well."

— Kelly Jackson Higgins, Senior Editor, Dark Reading

  • Black Hat Inc.


  • Subscribe to RSS










    Bugs
    ENTERPRISE VULNERABILITIES
    Vulnerability:suse linux
    Published:2010-01-22
    Severity:High
    Description:SUSE Linux Enterprise 10 SP3 (SLE10-SP3) configures postfix to listen on all network interfaces, which might allow remote attackers to bypass intended access restrictions.
    Vulnerability:ie
    Published:2010-01-22
    Severity:High
    Description:The URL validation functionality in Microsoft Internet Explorer 7 and 8 does not properly process input parameters, which allows remote attackers to execute arbitrary local programs via a crafted URL, aka "URL Validation Vulnerability."
    Vulnerability:bind
    Published:2010-01-22
    Severity:Medium
    Description:ISC BIND 9.0.x through 9.3.x, 9.4 before 9.4.3-P5, 9.5 before 9.5.2-P2, 9.6 before 9.6.1-P3, and 9.7.0 beta does not properly validate DNSSEC (1) NSEC and (2) NSEC3 records, which allows remote attackers to add the Authenticated Data (AD) flag to a forged NXDOMAIN response for an existing domain.
    Vulnerability:ie
    Published:2010-01-22
    Severity:High
    Description:Microsoft Internet Explorer 6, 6 SP1, 7, and 8 does not properly handle objects in memory, which allows remote attackers to execute arbitrary code by accessing an object that (1) was not properly initialized or (2) is deleted, leading to memory corruption, aka "Uninitialized Memory Corruption Vulnerability," a different vulnerability than CVE-2009-2530 and CVE-2009-2531.
    Vulnerability:ie
    Published:2010-01-22
    Severity:High
    Description:Microsoft Internet Explorer 8 does not properly handle objects in memory, which allows remote attackers to execute arbitrary code by accessing an object that (1) was not properly initialized or (2) is deleted, leading to memory corruption, aka "Uninitialized Memory Corruption Vulnerability," a different vulnerability than CVE-2009-3671, CVE-2009-3674, and CVE-2010-0246.


    Briefing Centers
    POWERFUL INFORMATION
    AT YOUR FINGERTIPS
    (SPONSORED LINKS)