Proxmark3 community

Research, development and trades concerning the powerful Proxmark3 device.

Remember; sharing is caring. Bring something back to the community.


"Learn the tools of the trade the hard way." +Fravia

You are not logged in.

Announcement

Time changes and with it the technology
Proxmark3 @ discord

Users of this forum, please be aware that information stored on this site is not private.

#1 2020-03-25 10:34:47

JonnyDvE
Contributor
Registered: 2020-03-24
Posts: 3

Cant Crack Mifare 4k

I´ve been trying to read nad copy a keyfob from Work, but im unable to read the second sector, ive run Autpwn a few times now, but it just stops after collecting ~64k nonces in Hardnested, after that it just crashes

    
[=] Using UART port COM13 
[=] Communicating with PM3 over USB-CDC 

 [ Proxmark3 RFID instrument ] 

 [ CLIENT ] 
  client: RRG/Iceman
  compiled with MinGW-w64 9.2.0 OS:Windows (64b) ARCH:x86_64

 [ PROXMARK3 ] 

 [ ARM ]
  bootrom: RRG/Iceman/master/8ef3f343 2020-03-20 11:20:37
       os: RRG/Iceman/master/8ef3f343 2020-03-20 11:20:49
  compiled with GCC 8.3.1 20190703 (release) [gcc-8-branch revision 273027]

 [ FPGA ]
  LF image built for 2s30vq100 on 2020-02-22 at 12:51:14
  HF image built for 2s30vq100 on 2020-01-12 at 15:31:16

 [ Hardware ] 
  --= uC: AT91SAM7S512 Rev B
  --= Embedded Processor: ARM7TDMI
  --= Nonvolatile Program Memory Size: 512K bytes, Used: 246544 bytes (47%) Free: 277744 bytes (53%)
  --= Second Nonvolatile Program Memory Size: None
  --= Internal SRAM Size: 64K bytes
  --= Architecture Identifier: AT91SAM7Sxx Series
  --= Nonvolatile Program Memory Type: Embedded Flash Memory


[usb] pm3 --> hf search

[+]  UID: FD FF 46 11  
[+] ATQA: 00 02 
[+]  SAK: 18 [2] 
[+] TYPE: NXP MIFARE Classic 4k | Plus 4k SL1 | 4k Ev1 
[=] proprietary non iso14443-4 card found, RATS not supported
[+] Prng detection: hard 

[+] Valid ISO14443-A tag found

[usb] pm3 --> hf mf autopwn * 4
[!] no known key was supplied, key recovery might fail
[+] loaded 23 keys from hardcoded default array
[=] running strategy 1

[+] Chunk: 5.3s | found 55/80 keys (23)

[=] running strategy 2

[+] Chunk: 5.2s | found 55/80 keys (23)

[+] target sector:  0 key type: A -- found valid key [  A0 A1 A2 A3 A4 A5  ] (used for nested / hardnested attack)
[+] target sector:  0 key type: B -- found valid key [  B5 78 F3 8A 5C 61  ]
[+] target sector:  2 key type: A -- found valid key [  A0 A1 A2 A3 A4 A5  ]
[+] target sector:  2 key type: B -- found valid key [  00 00 01 4B 5C 31  ]
[+] target sector:  3 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector:  3 key type: B -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector:  4 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector:  4 key type: B -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector:  5 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector:  5 key type: B -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector:  6 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector:  6 key type: B -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector:  7 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector:  7 key type: B -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector:  8 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector:  8 key type: B -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector:  9 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector:  9 key type: B -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 10 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 10 key type: B -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 11 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 11 key type: B -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 12 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 12 key type: B -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 13 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 13 key type: B -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 14 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 14 key type: B -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 15 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 15 key type: B -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 16 key type: A -- found valid key [  A0 A1 A2 A3 A4 A5  ]
[+] target sector: 16 key type: B -- found valid key [  B5 78 F3 8A 5C 61  ]
[+] target sector: 17 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 18 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 19 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 20 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 21 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 22 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 23 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 24 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 25 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 26 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 27 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 28 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 29 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 30 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 31 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 32 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 33 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 34 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 35 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 36 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 37 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 38 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] target sector: 39 key type: A -- found valid key [  FF FF FF FF FF FF  ]
[+] Using AVX2 SIMD core.
[-] Error - can't find hardnested_bf_bench_data.bin
Couldn't read benchmark data. Assuming brute force rate of 120000000 states per second



 time    | #nonces | Activity                                                | expected to brute force
         |         |                                                         | #states         | time 
------------------------------------------------------------------------------------------------------
       0 |       0 | Start using 24 threads and AVX2 SIMD core               |                 |
       0 |       0 | Brute force benchmark: 120 million (2^26.8) keys/s      | 140737488355328 |   14d
       0 |       0 | Using 0 precalculated bitflip state tables              | 140737488355328 |   14d
       3 |     112 | Apply bit flip properties                               | 140737488355328 |   14d
       3 |     224 | Apply bit flip properties                               | 140737488355328 |   14d
       4 |     333 | Apply bit flip properties                               | 140737488355328 |   14d
       5 |     444 | Apply bit flip properties                               | 140737488355328 |   14d
       6 |     555 | Apply bit flip properties                               | 140737488355328 |   14d
       7 |     667 | Apply bit flip properties                               | 140737488355328 |   14d
       8 |     775 | Apply bit flip properties                               | 140737488355328 |   14d
       8 |     887 | Apply bit flip properties                               | 140737488355328 |   14d
       9 |     997 | Apply bit flip properties                               | 140737488355328 |   14d
      10 |    1108 | Apply bit flip properties                               | 140737488355328 |   14d
      11 |    1216 | Apply bit flip properties                               | 140737488355328 |   14d
      12 |    1327 | Apply bit flip properties                               | 140737488355328 |   14d
      13 |    1439 | Apply bit flip properties                               | 140737488355328 |   14d
      14 |    1550 | Apply bit flip properties                               | 140737488355328 |   14d
      14 |    1660 | Apply bit flip properties                               | 140737488355328 |   14d
      15 |    1770 | Apply bit flip properties                               | 140737488355328 |   14d
      16 |    1876 | Apply bit flip properties                               | 140737488355328 |   14d
      17 |    1985 | Apply Sum property. Sum(a0) = 128                       |             nan |  nand
      18 |    2096 | Apply bit flip properties                               |             nan |  nand
      49 |    2204 | Apply bit flip properties                               |             nan |  nand
      50 |    2314 | Apply bit flip properties                               |             nan |  nand
      51 |    2424 | Apply bit flip properties                               |             nan |  nand
      52 |    2531 | Apply bit flip properties                               |             nan |  nand
      53 |    2638 | Apply bit flip properties                               |             nan |  nand
      54 |    2744 | Apply bit flip properties                               |             nan |  nand
      54 |    2852 | Apply bit flip properties                               |             nan |  nand
      55 |    2961 | Apply bit flip properties                               |             nan |  nand
    [...]
    5062 |   65532 | Apply bit flip properties                               |             nan |  nand
    5063 |   65532 | Apply bit flip properties                               |             nan |  nand
    5064 |   65532 | Apply bit flip properties                               |             nan |  nand
    5065 |   65532 | Apply bit flip properties                               |             nan |  nand
    5066 |   65532 | Apply bit flip properties                               |             nan |  nand
    5067 |   65532 | Apply bit flip properties                               |             nan |  nand
    5067 |   65532 | Apply bit flip properties                               |             nan |  nand
    5068 |   65532 | Apply bit flip properties                               |             nan |  nand
    5069 |   65532 | Apply bit flip properties                               |             nan |  nand

[!!] Error: No response from Proxmark3.

[!] Communicating with Proxmark3 device failed 
[=] Running in OFFLINE mode. Use "hw connect" to reconnect

Anything else I can try?

Offline

#2 2020-03-25 11:49:53

zorks56
Contributor
Registered: 2020-02-02
Posts: 14

Re: Cant Crack Mifare 4k

Hi.the problem is the firmware version. Me too the dame problem

Offline

#3 2020-03-25 16:11:32

iceman
Administrator
Registered: 2013-04-25
Posts: 9,497
Website

Re: Cant Crack Mifare 4k

I don't think its any problem with the firmware version.  I would think you two don't have a RDV4 but insists on using a fw compiled for it instead of using a fw compiled for other proxmark3 devices.

Offline

#4 2020-03-25 19:18:53

JonnyDvE
Contributor
Registered: 2020-03-24
Posts: 3

Re: Cant Crack Mifare 4k

Indeed I am not using an rdv4, i did Try it for the sake of autopwn. ( I used the precompiled version Generic)
As I have troubles compiling myself and always got the wrong Keys using the other precompiled versions I gave it a shot.
Is it even possible to read the sector if you dont have either key A or B of that sector? Maybe someone has a bigger Keylist to try?

Offline

#5 2020-07-26 01:08:52

Kosmic
Contributor
Registered: 2020-05-27
Posts: 5

Re: Cant Crack Mifare 4k

I had the same problem one time. And solved it by updating to the latest firmware/software. Update your Proxmark and try it again.

Offline

Board footer

Powered by FluxBB