I originally came across Wiegand as part of my Attacking Proximity Card Access Systems talk where I demonstrated attacks against each of the components involved in access control systems. Later on someone told me about Zac Franken, who created Gecko, a sort of Wiegand man in the middle tool. This blog post will implement and expand on Franken's tool using an Arudino.
On the WireWiegand is used to transmit data from the access card reader to the backend controller for processing. It's a super simple protocol consisting of two wires:
DATA1. When the reader wants to send a zero, it lowers
DATA0and whenever it wants to send a one it lowers
DATA1. Here's what it looks like within an logic analyzer. I've written the one's and zero's in green and translated them to the card values printed on the back of a proximity card.
AccessingIn a non-lab environment the wires are physically accessible anywhere between the reader and the controller. For a completely unauthenticated user, the easiest way is to pop off the cover of the reader which will expose the two screws. Remove the screws, pull the reader away from the wall, and you'll be able to access the wires. They're usually colored green for
DATA0and white for
DATA1. You can also use the power wires (red and black) to power your Arduino.
Capturing Card Values (Skimming)The first attack that's possible is to capture valid card values as they're being transmitted. The values can then be stored on a memory card off the Arudino or even transmitted wirelessly. The Gecko tool skimmed card values, then when a special replay card was provided, it would repeat a stored card value to the controller.
The Arduino code to implement this is pretty simple. Mike Cook created some basic code that places an interrupt on the wires, so when there is a change, the interrupt function will be called. I leveraged this technique in my Arduino code too. The skimmed card values are sent via the Arduino's serial interface.
The Skimmer is implemented in the emulator code in the next section.
Emulating Card ValuesSomething that's obvious but for some reason overlooked is that with direct access to the Wiegand interface, you can bypass all reader-level security. For instance, there are certain proximity cards that implement RFID authentication, encryption, and replay protection. In most cases this security is in place to protect the card value stored on the card. If you can somehow obtain a card value, it can be replayed via wiegand without ever considering the reader to human interface. This even extends to biometrics.
Furthermore, if you add a wireless component to your Arudino setup, you can wirelessly provide those card values. Here's the code:
Brute Forcing ValuesAnother interesting idea is brute forcing values. There may be times that you have a valid (or once valid) card value and you need a card value with higher privileges (e.g. access to restricted areas). Due to the way certain card formats (e.g. 26-bit format) distribute card values, with knowledge of one card, you could determine other card values with a simple incremental brute force. This technique can be also be applied to the reader interface, but because of the delay between reads, you can only get about one read a second. Using the Weigand interface, you can get 5!
Here's the code:
Fuzzing!Don't forget that both the controller and the backend system process the values received via Wiegand. This gives us two potential targets to fuzz. Although the test cases are pretty limited: length, raising DATA0 and DATA1 at the same time, raising the two for a long time, etc... It's still worthwhile to fuzz - if you get a crash, you can potentially implement the trigger in a RFID or magstripe card, and crash the system from reader's interface!!
I implemented a basic fuzzer using the Arudino:
Yup Wiegand is fun, although a bit outdated. Many of the newer contactless protocols and devices with any real clout do a full Diffie-Hellman (or something similar) before sharing the secret. Some of the cards even have embedded JVMs that power up with the inductance charge...they then are responsible for all that logic.ReplyDelete
Wiegand can be a little annoying because the term is used for so many different things - yea the card to reader wiegand is definitely dated and have been replaced by much better, more secure technologies. However, most systems actually still leverage wiegand for the reader to controller stuff. Since this is after the reader to card security, it's still a devastating point of attack. Until they extend the tunnels that are between the card and the reader (RFID interface) all the way to the backend (or at least the controller) then they're only partially resolving the problem.Delete
Readers all have micro switch protection or magnetic potetcion in order to detect tampingReplyDelete
That's not true where I work! I HIPAA facility no less. Some readers are Mullion readers and are not tamper protected.Delete
The Large HID prox readers that do have tampers are not implemented.
As a feature, a Man in the middle with Bluetooth to playback valid cards recorded. monitor your valid read line to verify valid reads.
I think the CISSP at our company would foul his drawers.
Worked in the Access industry over 15 years now. See alot of readers and test alot of them. Most have switches, magnetic, and even light detecting. but like all things its only good when users actually hook them up. Extra work, extra hassle, very rarely have I seen or heard of them in use. Obviously the more secure the location the more likely to add this but just one more thing to set up. Sort of along the lines of people using 12345 as a password...Delete