Files

93 lines
3.0 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# LF_HIDFCBRUTE — HID Facility Code Bruteforce
> **Author:** ss23
> **Frequency:** LF (125 kHz)
> **Hardware:** RDV4 (requires flash for logging)
[Back to Standalone Modes Index](../../armsrc/Standalone/readme.md#individual-mode-documentation) | [Source Code](../../armsrc/Standalone/lf_hidfcbrute.c) | [Development Guide](../../armsrc/Standalone/readme.md#developing-standalone-modes)
---
## What
Brute forces all 256 possible HID facility codes (0–255) using a static card number of 1, and logs results to flash memory. When a reader accepts a facility code, you can mark it with a button press.
## Why
HID 26-bit (H10301) cards encode a facility code (FC, 0–255) and a card number (CN, 0–65535). If you don't have a valid card to clone, but you do have physical access to a reader, you can discover the correct facility code by trying all 256 possibilities. Once you know the FC, you can pair it with brute-forced card numbers.
This is the first step in a blind HID attack when you have no captured credentials.
## How
1. The mode simulates an HID 26-bit tag with FC cycling from 0 to 255 and CN fixed at 1
2. During each simulation, LED C toggles to show progress
3. Press the button to log the current FC to `lf_hid_fcbrute.log` on flash (this is your "the door opened" marker)
4. Hold the button for 1 second to exit
5. After completion, retrieve the log file via the client
## LED Indicators
| LED | Meaning |
|-----|---------|
| **A** (solid) | Brute force active |
| **C** (toggling) | Toggles on each FC attempt — visual progress indicator |
| **D** (solid) | Simulation transmission active |
## Button Controls
| Action | Effect |
|--------|--------|
| **Click / hold 10ms** | Begin brute force |
| **Single click** (during brute) | Log current FC to flash file |
| **Hold ≥ 1 second** | Exit brute force |
| **USB command** | Exit standalone mode |
## State Machine
```mermaid
stateDiagram-v2
[*] --> WaitStart : Startup
WaitStart --> BruteFC0 : Button press
BruteFC0 --> BruteFC1 : Simulate FC=0, advance
BruteFC1 --> BruteFC2 : Simulate FC=1, advance
BruteFC2 --> BruteFC_N : ...
BruteFC_N --> BruteFC255 : Simulate FC=N, advance
BruteFC255 --> Complete : All FCs tested
BruteFC_N --> LogFC : Button click\n(door opened!)
LogFC --> BruteFC_N : Continue brute
BruteFC_N --> [*] : Button hold ≥ 1s
Complete --> [*] : Done
note right of LogFC
Writes current FC
to lf_hid_fcbrute.log
on SPI flash
end note
```
## Flash Storage
- **Log file**: `lf_hid_fcbrute.log` on SPI flash
- Contains facility codes that were manually marked via button press
- Retrieve with the client after the assessment
## Compilation
```
make clean
make STANDALONE=LF_HIDFCBRUTE -j
./pm3-flash-fullimage
```
## Related
- [HID Corporate Brute](lf_hidbrute.md) — Brute force card numbers with known FC
- [SamyRun](lf_samyrun.md) — Read/clone/sim HID26
- [ProxBrute](lf_proxbrute.md) — HID ProxII brute force
- [IceHID Collector](lf_icehid.md) — Passive HID credential collection