Hackers Found a Way to Open Any of 3 Million Hotel Keycard Locks in Seconds (www.wired.com)
from floofloof@lemmy.ca to technology@lemmy.ml on 21 Mar 2024 17:04
https://lemmy.ca/post/17883450

#technology

threaded - newest

mipadaitu@lemmy.world on 21 Mar 2024 17:22 next collapse

Paywall

When thousands of security researchers descend on Las Vegas every August for what’s come to be known as “hacker summer camp,” the back-to-back Black Hat and Defcon hacker conferences, it’s a given that some of them will experiment with hacking the infrastructure of Vegas itself, the city’s elaborate array of casino and hospitality technology. But at one private event in 2022, a select group of researchers were actually invited to hack a Vegas hotel room, competing in a suite crowded with their laptops and cans of Red Bull to find digital vulnerabilities in every one of the room’s gadgets, from its TV to its bedside VoIP phone.

One team of hackers spent those days focused on the lock on the room’s door, perhaps its most sensitive piece of technology of all. Now, more than a year and a half later, they’re finally bringing to light the results of that work: a technique they discovered that would allow an intruder to open any of millions of hotel rooms worldwide in seconds, with just two taps.

Today, Ian Carroll, Lennert Wouters, and a team of other security researchers are revealing a hotel keycard hacking technique they call Unsaflok. The technique is a collection of security vulnerabilities that would allow a hacker to almost instantly open several models of Saflok-brand RFID-based keycard locks sold by the Swiss lock maker Dormakaba. The Saflok systems are installed on 3 million doors worldwide, inside 13,000 properties in 131 countries.

By exploiting weaknesses in both Dormakaba’s encryption and the underlying RFID system Dormakaba uses, known as MIFARE Classic, Carroll and Wouters have demonstrated just how easily they can open a Saflok keycard lock. Their technique starts with obtaining any keycard from a target hotel—say, by booking a room there or grabbing a keycard out of a box of used ones—then reading a certain code from that card with a $300 RFID read-write device, and finally writing two keycards of their own. When they merely tap those two cards on a lock, the first rewrites a certain piece of the lock’s data, and the second opens it.

“Two quick taps and we open the door,” says Wouters, a researcher in the Computer Security and Industrial Cryptography group at the KU Leuven University in Belgium. “And that works on every door in the hotel.”

A video of the researchers demonstrating their lock-hacking technique. (The pattern of lights shown on the lock is redacted at one point at the researchers’ request to avoid revealing a detail of their technique they agreed with Dormakaba not to make public.)Video: Ian Carroll

Wouters and Carroll, an independent security researcher and founder of travel website Seats.aero, shared the full technical details of their hacking technique with Dormakaba in November 2022. Dormakaba says that it’s been working since early last year to make hotels that use Saflok aware of their security flaws and to help them fix or replace the vulnerable locks. For many of the Saflok systems sold in the last eight years, there’s no hardware replacement necessary for each individual lock. Instead, hotels will only need to update or replace the front desk management system and have a technician carry out a relatively quick reprogramming of each lock, door by door.

Wouters and Carroll say they were nonetheless told by Dormakaba that, as of this month, only 36 percent of installed Safloks have been updated. Given that the locks aren’t connected to the internet and some older locks will still need a hardware upgrade, they say the full fix will still likely take months longer to roll out, at the very least. Some older installations may take years.

“We have worked closely with our partners to identify and implement an immediate mitigation for this vulnerability, along with a longer-term solution,” Dormakaba wrote to WIRED in a statement, though it declined to detail what that “immediate mitigation” might be. “Our customers and partners all take security very seriously, and we are confident all reasonable steps will be taken to address this matter in a responsible way.”

The technique to hack Dormakaba’s locks that Wouters and Carroll’s research group discovered involves two distinct kinds of vulnerabilities: One that allows them to write to its keycards, and one that allows them to know what data to write to the cards to successfully trick a Saflok lock into opening. When they analyzed Saflok keycards, they saw that they use the MIFARE Classic RFID system, which has been known for more than a decade to have vulnerabilities that allow hackers to write to keycards, though the brute-force process can take as long as 20 seconds. They then cracked a part of Dormakaba’s own encryption system, its so-called key derivation function, which allowed them to write to its cards far faster. With either of those tricks, the researchers could then copy a

wildbus8979@sh.itjust.works on 21 Mar 2024 18:05 next collapse

RedBull? I can tell the journalist wasn’t in the room, everybody knows Club Mate and Jolt Cola are the drinks of hackers ;)

LostXOR@fedia.io on 21 Mar 2024 19:32 next collapse

A $300 RFID read/writer? Seems way too expensive, I remember buying one for under $10 for my Arduino a while back.

wildbus8979@sh.itjust.works on 22 Mar 2024 00:47 collapse

They’re probably talking about a Proxmark.

bradorsomething@ttrpg.network on 21 Mar 2024 21:22 collapse

I attended a talk on this at Defcon in… 2009 maybe?

Are we still talking about this?

BuryMyHorse@lemmy.world on 21 Mar 2024 18:06 next collapse

Sick! Would a Chameleon Ultra also work?

sylver_dragon@lemmy.world on 21 Mar 2024 18:21 next collapse

From the unsaflok.com site:

Dormakaba uses a Key Derivation Function (KDF) to derive the keys for some of the Saflok MIFARE Classic sectors. This proprietary KDF only uses the card’s Unique IDentifier (UID) as an input.
Knowledge of the KDF allows an attacker to easily read and clone a Saflok MIFARE Classic card. However, the KDF by itself is not sufficient for an attacker to create arbitrary Saflok keycards.

Security is hard. Cryptography is even harder. Don’t roll your own algorithms, it’s just asking for a problem. And given that “oversight”, I’d bet that the rest of the kill chain involves equally bad encryption or hashing being used on the cards.

ramble81@lemm.ee on 21 Mar 2024 21:02 collapse

I’m curious, for a non-network connected lock, how could you ensure that it’s secured with time bound parameters like they list?

Now that I’m thinking about it I guess each lock would have a private key and a CMOS of sorts to keep time. The writer could then write have the public key of each room and that could have a timestamp as part of the encrypted payload. I guess to take it further you could reverse it too with that payload having a private key of the writer and the locks could verify the private key against a public key of the writer. At that point each writer would have to have the public key of all locks, and each lock would have the public key of each writer.

At that point your payload to encode would be a timestamp of expiration and any sort of “checksum” or PSK to verify it was made by a valid writer?

August27th@lemmy.ca on 21 Mar 2024 21:41 collapse

Look up JSON Web Tokens, they work how this would need to work.

don@lemm.ee on 21 Mar 2024 20:13 next collapse

Corporate shareholders: is it cheap? Yes? Do I ever stay there? No? tfw I don’t give a fuck lol

zeusbottom@sh.itjust.works on 21 Mar 2024 21:53 next collapse

In 2011 I was aghast when I learned a popular keycard / biometric system used FTP to pull down its cleartext list of acceptable keys from the server.

The username was something like ADMIN and the password was PASS.

And no, that wasn’t the FTP command; that was the password.

So I’m not surprised that there are still problems with these devices.

edit: more complete thought

NOPper@lemmy.world on 21 Mar 2024 23:07 collapse

To be fair to manufacturers for once here, this kind of this is usually due to users not properly securing these systems. The industry is still way behind on proper infosec but they’ve come a long way the last 10 years or so.

7heo@lemmy.ml on 21 Mar 2024 21:55 collapse

Without paywall.