Perimeter

3/23/2007
07:45 AM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

New RFID Attack Opens the Door

Proof-of-concept lets intruder gain entry into the building by faking RFID readers with SQL injection

Be careful of who walks up to your building and swipes an ID card: New proof-of-concept code will soon be released that lets attackers hack RFID readers and walk right in as if they work there.

The attack uses SQL injection to fake the back-end RFID reader into admitting the cardholder into the building, says Joshua Perrymon, hacking director for PacketFocus Security Solutions and the researcher who wrote the POC. Perrymon -- who's taking a cue from the recent Black Hat RFID flap and won't name RFID vendor names -- says he's tested it on a few RFID vendors' systems, but the exploit will work on most any of them. (See HID Lists RFID Security Steps, HID, IOActive Butt Heads Again, and Black Hat Cancels RFID Demo.)

The RFID databases don't validate the input they receive from the swiped cards, he says, which leaves them wide open for hacks. "I was noticing the back-end database is the same across all products -- I haven't seen any using input validation" to confirm the data they've swiped is legitimate, he says. "It doesn't really matter who the vendor is... In any building you go to with this, bang, you gain access."

Perrymon was able to fake out the readers by injecting SQL characters that appear to be legit into various brands of 1356 Mhz RFID cards. The SQL injection code looks legit when an intruder swipes his card, so he gains entry into the building. "In the user-data section, it uses numeric characters, but we're using brackets and SQL statements... That's standard with a SQL injection in an application."

Conventional attack methods on RFID such as SQL injection haven't been studied much so far, Perrymon says. Most of the attention has been on cracking RFID cryptography and RFID cloning, such as IOActive's research, which was yanked from the Black Hat DC briefing agenda after threats of a patent lawsuit by RFID vendor HID.

Perrymon used an RFID writer to copy a SQL injection statement to the card. Unlike cloning, which copies the user's ID and facility code, this attack uses SQL injection code. "The beauty of this is I'm using off-the-shelf stuff, and there's no reverse-engineering."

Perrymon says adding input validation to these products would be simple for RFID vendors, and he's hoping his work will pressure the vendors to fix the problem. "I want vendors to put in input validation in the reader or database," he says. "Preferably the reader."

But this attack is not for any script kiddie. "You have to be pretty skilled in RFID to understand all the components," says Perrymon, whose company does penetration testing and social engineering exploits. He plans to release the POC soon.

— Kelly Jackson Higgins, Senior Editor, Dark Reading

  • PacketFocus Security Solutions
  • IOActive
  • HID Global Corp. Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

    Comment  | 
    Print  | 
    More Insights
  • Comments
    Oldest First  |  Newest First  |  Threaded View
    Why CISOs Need a Security Reality Check
    Joel Fulton, Chief Information Security Officer for Splunk,  6/13/2018
    Cisco Talos Summit: Network Defenders Not Serious Enough About Attacks
    Curtis Franklin Jr., Senior Editor at Dark Reading,  6/13/2018
    Four Faces of Fraud: Identity, 'Fake' Identity, Ransomware & Digital
    David Shefter, Chief Technology Officer at Ziften Technologies,  6/14/2018
    Register for Dark Reading Newsletters
    White Papers
    Video
    Cartoon
    Current Issue
    Flash Poll
    Twitter Feed
    Dark Reading - Bug Report
    Bug Report
    Enterprise Vulnerabilities
    From DHS/US-CERT's National Vulnerability Database
    CVE-2018-8030
    PUBLISHED: 2018-06-20
    A Denial of Service vulnerability was found in Apache Qpid Broker-J versions 7.0.0-7.0.4 when AMQP protocols 0-8, 0-9 or 0-91 are used to publish messages with size greater than allowed maximum message size limit (100MB by default). The broker crashes due to the defect. AMQP protocols 0-10 and 1.0 a...
    CVE-2018-1117
    PUBLISHED: 2018-06-20
    ovirt-ansible-roles before version 1.0.6 has a vulnerability due to a missing no_log directive, resulting in the 'Add oVirt Provider to ManageIQ/CloudForms' playbook inadvertently disclosing admin passwords in the provisioning log. In an environment where logs are shared with other parties, this cou...
    CVE-2018-11701
    PUBLISHED: 2018-06-20
    FastStone Image Viewer 6.2 has a User Mode Write AV at 0x005cb509, triggered when the user opens a malformed JPEG file that is mishandled by FSViewer.exe. Attackers could exploit this issue for DoS (Access Violation) or possibly unspecified other impact.
    CVE-2018-11702
    PUBLISHED: 2018-06-20
    FastStone Image Viewer 6.2 has a User Mode Write AV at 0x00578cb3, triggered when the user opens a malformed JPEG file that is mishandled by FSViewer.exe. Attackers could exploit this issue for DoS (Access Violation) or possibly unspecified other impact.
    CVE-2018-11703
    PUBLISHED: 2018-06-20
    FastStone Image Viewer 6.2 has a User Mode Write AV at 0x00402d6a, triggered when the user opens a malformed JPEG file that is mishandled by FSViewer.exe. Attackers could exploit this issue for DoS (Access Violation) or possibly unspecified other impact.