Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Card is not vulnerable to nested attack #53

Open
mirobertod opened this issue Feb 9, 2018 · 9 comments
Open

Card is not vulnerable to nested attack #53

mirobertod opened this issue Feb 9, 2018 · 9 comments

Comments

@mirobertod
Copy link

Hello,
I used the following command to perform a dump of my Mifare Classic 1K card:

mfoc -O my_dump.mdf

Then I used the following command to write the dump into a blank card:

nfc-mfclassic w A my_dump.mdf blank.mdf f
Result:

NFC reader: ACS / ACR122U PICC Interface opened
  Found MIFARE Classic card:
  ISO/IEC 14443A (106 kbps) target:
      ATQA (SENS_RES): 00  04  
         UID (NFCID1): a0  b0  5b  56  
        SAK (SEL_RES): 08  
  Guessing size: seems to be a 1024-byte card
  Writing 64 blocks |...............................................................|
  Done, 63 of 64 blocks written.

After that I tried to read my new card with same command used at the beginning:

mfoc -O my_new_dump.mdf

And the result is:

Found Mifare Classic 1k tag
  ISO/IEC 14443A (106 kbps) target:
      ATQA (SENS_RES): 00  04  
  * UID size: single
  * bit frame anticollision supported
         UID (NFCID1): a0  b0  5b  56  
        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 (4 Byte UID or 4 Byte RID) 2K, Security level 1
  * SmartMX with MIFARE 1K emulation
  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] -> [................]
  [Key: a0a1a2a3a4a5] -> [/...............]
  [Key: d3f7d3f7d3f7] -> [/...............]
  [Key: 000000000000] -> [/...............]
  [Key: b0b1b2b3b4b5] -> [/...............]
  [Key: 4d3a99c351dd] -> [/...............]
  [Key: 1a982c7e459a] -> [/...............]
  [Key: aabbccddeeff] -> [/...............]
  [Key: 714c5c886e97] -> [/...............]
  [Key: 587ee5f9350f] -> [/...............]
  [Key: a0478cc39091] -> [/...............]
  [Key: 533cb6c723f6] -> [/...............]
  [Key: 8fd0a4f256e9] -> [/...............]
  
  Sector 00 - Found   Key A: a0a1a2a3a4a5 Unknown Key B
  Sector 01 - Unknown Key A               Unknown Key B
  Sector 02 - Unknown Key A               Unknown Key B
  Sector 03 - Unknown Key A               Unknown Key B
  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 - Unknown Key A               Unknown Key B
  
  
  Using sector 00 as an exploit sector
  Card is not vulnerable to nested attack

I tried also with the mfcuk command but I cannot read.

Is there someone can help me explaining what happend?
Thanks

@rainyl
Copy link

rainyl commented Oct 28, 2018

same issue...any solutions???

@XAS-712
Copy link

XAS-712 commented Feb 12, 2019

Try hardnested crack.

@5trohm
Copy link

5trohm commented Mar 12, 2019

same issue useing an old Gymcard (SAK08) . got Lucky with another Card (new Gymcard SAK88) and get Keys of Sector 04 -14. even with this one known key added to the mfoc command mfoc -P 500 -O GymCard_mfoc.mfd -k XXXXXXXXXXXX

Try to authenticate to all sectors with default keys...
Symbols: '.' no key found, '/' A key found, '\' B key found, 'x' both keys found
[Key: xxxxxxxxxxxx] -> [....///////////.]
[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]

it wont work. Also tried a herdnested crack with miLazyCracker.
MFOC not possible, detected hardened Mifare Classic
got problems with the libnfc_cryptol_crack.

@scorpiodu23
Copy link

I'm going back to the subject, someone has a solution, please?

@mac3d0
Copy link

mac3d0 commented Feb 23, 2020

Vou voltar ao assunto, alguém tem uma solução, por favor?

I can't find fault with my Mifare Plus 2k tag card he is not vulnerable to nested attack, someone has an idea or solution

@rainyl
Copy link

rainyl commented Mar 14, 2020

so, i finally known that it because the card is not possible to be cracked by nested,

Try hardnested crack.

and his solution is the right way, thanks

@mac3d0
Copy link

mac3d0 commented Mar 17, 2020 via email

@mac3d0
Copy link

mac3d0 commented Mar 17, 2020 via email

@Faelian
Copy link

Faelian commented Jun 14, 2022

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants