Endless mfcuk_key_recovery_block() error (code 0x09)

[adamasstokhorst]

I used two versions of MFCUK, one is the latest and another is a r55 binary that is precompiled and came with libnfc.dll (I had to provide libusb0.dll for this). I'm not sure what version of libnfc I have on both (probably different versions).

When compiling MFCUK, I did "autoreconf -is", "./configure", and "make". However, there was this message while executing the configure script (it still compiled though): EDIT: link because GitHub removed lots of spaces: http://pastebin.com/kAhZwyeM

In both cases, I left MFCUK to recover a key (because MFOC couldn't do it and spent hours probing to no success), and when I came back to it, I returned to a screenful of "ERROR: mfcuk_key_recovery_block() (error code=0x09)"

I couldn't find anything about error code 0x09 anywhere, any help would be appreciated.

[revok7512]

hi,

did you had any clue on that bug

i'm having the same problem it's when i try too dump a classik mini (5sectors) tag

is Mfuck working with mini tags? i'm not sure

regards

[mattionline]

Same error here: MacOS 10.13.3 mfcuk - 0.3.8 ACR122U Mifare Classic 1k Execution time: 12 hours

How can i solve the error?

MBP:mfcuk mathias$ mfcuk -C -R 0:A -s 250 -S 250 -v 5
mfcuk - 0.3.8
Mifare Classic DarkSide Key Recovery Tool - 0.3
by Andrei Costin, [email protected], http://andreicostin.com

WARN: cannot open template file './data/tmpls_fingerprints/mfcuk_tmpl_skgt.mfd'
WARN: cannot open template file './data/tmpls_fingerprints/mfcuk_tmpl_ratb.mfd'
WARN: cannot open template file './data/tmpls_fingerprints/mfcuk_tmpl_oyster.mfd'

INFO: Connected to NFC reader: ACS ACR122U / ACR122U214



INITIAL ACTIONS MATRIX - UID 04 e8 f9 c2 - TYPE 0x08 (MC1K)
---------------------------------------------------------------------
Sector	|    Key A	|ACTS | RESL	|    Key B	|ACTS | RESL
---------------------------------------------------------------------
0	|  000000000000	| . R | . .	|  000000000000	| . . | . .
1	|  000000000000	| . . | . .	|  000000000000	| . . | . .
2	|  000000000000	| . . | . .	|  000000000000	| . . | . .
3	|  000000000000	| . . | . .	|  000000000000	| . . | . .
4	|  000000000000	| . . | . .	|  000000000000	| . . | . .
5	|  000000000000	| . . | . .	|  000000000000	| . . | . .
6	|  000000000000	| . . | . .	|  000000000000	| . . | . .
7	|  000000000000	| . . | . .	|  000000000000	| . . | . .
8	|  000000000000	| . . | . .	|  000000000000	| . . | . .
9	|  000000000000	| . . | . .	|  000000000000	| . . | . .
10	|  000000000000	| . . | . .	|  000000000000	| . . | . .
11	|  000000000000	| . . | . .	|  000000000000	| . . | . .
12	|  000000000000	| . . | . .	|  000000000000	| . . | . .
13	|  000000000000	| . . | . .	|  000000000000	| . . | . .
14	|  000000000000	| . . | . .	|  000000000000	| . . | . .
15	|  000000000000	| . . | . .	|  000000000000	| . . | . .


VERIFY:
	Key A sectors: 0 1 2 3 4 5 6 7 8 9 a b c d e f
	Key B sectors: 0 1 2 3 4 5 6 7 8 9 a b c d e f


ACTION RESULTS MATRIX AFTER VERIFY - UID 04 e8 f9 c2 - TYPE 0x08 (MC1K)
---------------------------------------------------------------------
Sector	|    Key A	|ACTS | RESL	|    Key B	|ACTS | RESL
---------------------------------------------------------------------
0	|  000000000000	| . R | . .	|  000000000000	| . . | . .
1	|  000000000000	| . . | . .	|  000000000000	| . . | . .
2	|  000000000000	| . . | . .	|  000000000000	| . . | . .
3	|  000000000000	| . . | . .	|  000000000000	| . . | . .
4	|  000000000000	| . . | . .	|  000000000000	| . . | . .
5	|  000000000000	| . . | . .	|  000000000000	| . . | . .
6	|  000000000000	| . . | . .	|  000000000000	| . . | . .
7	|  000000000000	| . . | . .	|  000000000000	| . . | . .
8	|  000000000000	| . . | . .	|  000000000000	| . . | . .
9	|  000000000000	| . . | . .	|  000000000000	| . . | . .
10	|  000000000000	| . . | . .	|  000000000000	| . . | . .
11	|  000000000000	| . . | . .	|  000000000000	| . . | . .
12	|  000000000000	| . . | . .	|  000000000000	| . . | . .
13	|  000000000000	| . . | . .	|  000000000000	| . . | . .
14	|  000000000000	| . . | . .	|  000000000000	| . . | . .
15	|  000000000000	| . . | . .	|  000000000000	| . . | . .


RECOVER:  0
-----------------------------------------------------
Let me entertain you!
    uid: 04e8f9c2
   type: 08
    key: 000000000000
  block: 03
diff Nt: 0
  auths: 0
-----------------------------------------------------

-----------------------------------------------------
Let me entertain you!
    uid: 04e8f9c2
   type: 08
    key: 000000000000
  block: 03
diff Nt: 1
  auths: 1
-----------------------------------------------------

Hours later....


-----------------------------------------------------
Let me entertain you!
    uid: 04e8f9c2
   type: 08
    key: 000000000000
  block: 03
diff Nt: 65535
  auths: 65536
-----------------------------------------------------

-----------------------------------------------------
Let me entertain you!
    uid: 04e8f9c2
   type: 08
    key: 000000000000
  block: 03
diff Nt: 65536
  auths: 65537
-----------------------------------------------------
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x09)

A few hours later the error appeared the first time


-----------------------------------------------------
Let me entertain you!
    uid: 04e8f9c2
   type: 08
    key: 000000000000
  block: 03
diff Nt: 65536
  auths: 81893
-----------------------------------------------------
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x09)

MBP:~ mathias$ mfoc -O cardtocopy.dmp
Found Mifare Classic 1k tag
ISO/IEC 14443A (106 kbps) target:
ATQA (SENS_RES): 00 44
* UID size: double
* bit frame anticollision supported
UID (NFCID1): 04 e8 f9 c2 a5 59 80
SAK (SEL_RES): 08
* Not compliant with ISO/IEC 14443-4
* Not compliant with ISO/IEC 18092

Fingerprinting based on MIFARE type Identification Procedure:
* MIFARE Classic 1K
* MIFARE Plus (7 Byte UID) 2K, Security level 1
Other possible matches based on ATQA & SAK values:

Try to authenticate to all sectors with default keys…
Symbols: ‚.‘ no key found, ‚/‘ A key found, ‚\‘ B key found, ‚x‘ both keys found
[Key: ffffffffffff] -> [xxxx………..x]
[Key: a0a1a2a3a4a5] -> [xxxx………..x]
[Key: d3f7d3f7d3f7] -> [xxxx………..x]
[Key: 000000000000] -> [xxxx………..x]
[Key: b0b1b2b3b4b5] -> [xxxx………..x]
[Key: 4d3a99c351dd] -> [xxxx………..x]
[Key: 1a982c7e459a] -> [xxxx………..x]
[Key: aabbccddeeff] -> [xxxx………..x]
[Key: 714c5c886e97] -> [xxxx………..x]
[Key: 587ee5f9350f] -> [xxxx………..x]
[Key: a0478cc39091] -> [xxxx………..x]
[Key: 533cb6c723f6] -> [xxxx………..x]
[Key: 8fd0a4f256e9] -> [xxxx………..x]

Sector 00 – Found Key A: ffffffffffff Found Key B: ffffffffffff
Sector 01 – Found Key A: ffffffffffff Found Key B: ffffffffffff
Sector 02 – Found Key A: ffffffffffff Found Key B: ffffffffffff
Sector 03 – Found Key A: ffffffffffff Found Key B: ffffffffffff
Sector 04 – Unknown Key A Unknown Key B
Sector 05 – Unknown Key A Unknown Key B
Sector 06 – Unknown Key A Unknown Key B
Sector 07 – Unknown Key A Unknown Key B
Sector 08 – Unknown Key A Unknown Key B
Sector 09 – Unknown Key A Unknown Key B
Sector 10 – Unknown Key A Unknown Key B
Sector 11 – Unknown Key A Unknown Key B
Sector 12 – Unknown Key A Unknown Key B
Sector 13 – Unknown Key A Unknown Key B
Sector 14 – Unknown Key A Unknown Key B
Sector 15 – Found Key A: ffffffffffff Found Key B: ffffffffffff

Using sector 00 as an exploit sector
Card is not vulnerable to nested attack

[postex0dus]

Same problem here.. after about 10 hours of mfcuk I find my screen full of 0x09 errors ...

[Rafac13]

What's the solution for it?

[jerkha]

@mattionline "Card is not vulnerable to nested attack" you should try hardnested attack

[jerkha]

Anyone has found a solution ?

[Marcussso]

Same issue No solution yet?

[sferia82]

any solution? i am at same problem.

[r0one]

same here

[thevaquer]

The last versions are probably faulty... What versions of libnfc and mfcuk are you using? I'm going to try with older versions. A shame that mfcuk dont have the older versions available...

[joeyboon]

Just wanted to say I'm experiencing the same issue,

[VergeDX]

+1