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

Black Hat Researcher Hacks Biometric System

'Biologger' steals fingerprint, other biometric data

Mar 31, 2008 | 08:45 AM

By Kelly Jackson Higgins
DarkReading

If you think biometric scans are necessarily secure, think again: A European researcher has built a biometric keylogger that can capture fingerprint or other scans.

The so-called Biologger intercepts biometric data sent between a biometric scanner and its processing server, says Matt Lewis, a researcher with Information Risk Management, who demonstrated the tool and released proof-of-concept source code for it last week at Black Hat Europe in Amsterdam.

“It is the biometric equivalent of a traditional keylogger,” Lewis says. Biologger easily captures the biometric traffic, which then can be taken offline for the attacker to analyze and to find ways to subvert the biometric system, he says, adding that an attacker could use that information to recreate a user’s raw biometric image.

The attacker then could use that biometric to stage a spoofing attack, or to open a locked door, for instance, he says. “For example, if the system is a physical access control solution, then it may be possible to replay control signals that open locked doors, without the requirement for the presence of a valid biometric."

Lewis says an attacker could configure Biologger in several ways -- for sniffing biometric devices in a domain; as an inline wire tap or proxy device; for ARP poisoning; and as a memory-resident keylogger on a host. But planting Biologger in the victim network isn’t so easy: “Biologging as an attack vector is trivial. The difficult part might be getting the Biologger onto a network," he says.

“This could be done through physical means, or if the circumstances permitted, through exploitation of vulnerabilities via the Internet."

So what exactly is Biologger exploiting? The fact that many biometric systems don’t encrypt biometric data during the authentication process, according to Lewis. “Strong encryption of all biometric-related data during all transactions is the best way to defend against the attacks described in my paper,” he says. “This includes encryption over the network, and when storing biometric data in back-end databases.”

Lewis says biometrics isn’t about security: “Biometrics can work incredibly well under the right circumstances. It is just important that proper security controls are placed around biometric systems, as the biometric component alone cannot be relied upon for security."

Biologger is also aimed at building a penetration testing tool for biometric systems, he says -- capturing the traffic would be the core component of such a test.

Lewis says the Biologger source code he released is merely a POC of a proxy that captures data. “The aim of the POC was to highlight the simplicity of biologging, and how strong encryption would go a long way in protecting against the types of attacks that can be executed as a result of intercepted and unencrypted biometric data."

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

  • 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)