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

Chameleon mini Rev G (MF Detection/Reader attack) #226

Closed
nico0481 opened this issue Aug 14, 2019 · 16 comments
Closed

Chameleon mini Rev G (MF Detection/Reader attack) #226

nico0481 opened this issue Aug 14, 2019 · 16 comments

Comments

@nico0481
Copy link

Hello,

Is the Chameleon mini Rev G able to do reader attack (MF Detection).
With which firmware?
I can't find a way to do this.

Thank you

Best regards

Nico

@ghost
Copy link

ghost commented Aug 14, 2019

Not with standard firmware.
I had experimented with it a bit, hadn't tested it yet and hadn't finished it.
Need to check my local repos ;)

@ghost
Copy link

ghost commented Aug 24, 2019

I've attempted to bodge this feature into the current Rev G firmware and I'm clueless. I've asked the devs for the RevE Rebooted if they could assist with adding this feature to my fork of the Rev G firmware but they just tell me to go here. Would be nice if they could help out, and if not then we'll have to pray that someone gets this working on the rev g or pray we can afford to purchase a rev e rebooted.

https://github.com/lavanoid/ChameleonMini/commit/0ad00933b5aeca77cb0722e145d630c656dbe768
iceman1001/ChameleonMini-rebooted#139

Currently the RevG just locks up with a red LED and I don't know why.

@ghost
Copy link

ghost commented Aug 25, 2019

hi @lavanoid I tried the same time ago. found my local repo and pushed it now c8249d5 .

There I don't get problems with red LED. But I am not sure if its working.

Have no experience with detection function and are not sure what exactly is needed.
Maybe it is working, but I need some more tests or hints how to test.
Any Ideas?

I checked your code. Looks almost identical what I have done.

What have I done:

  1. Set MF Classic & UID
  2. Set Detection
  3. Hold on reader
  4. Use GUI and mfkey

@ghost
Copy link

ghost commented Aug 25, 2019

I just built the firmware with your commits and it seems to be working, however I have no idea what GUI to use to run mfkey. The latest build of ChameleonMini-rebootedGUI hides the mfkey option when detecting the Rev G.

I thought maybe something would be stored in the Chameleon device logs but I don't seem to have anything in there.

This is the video I watched, to get an idea of how the MF_DETECT function works: https://www.youtube.com/watch?v=1VpXC3-eKhc

@ghost
Copy link

ghost commented Aug 25, 2019 via email

@ghost
Copy link

ghost commented Aug 25, 2019

That seems to work! Requires a few retries and doesn't always find the keys (might just be because I'm using Mifare Classic Tool on Android and not an actual reader) but it does indeed work.

image
image
One bug with the GUI is that it doesn't let me change the UID of the tag, so I have to use another tool to do that.

@ghost
Copy link

ghost commented Aug 25, 2019

UID changes worked.
Enter UID --> Change UID.
(doesn't work in detection mode - need to set for example mf_classic_1k)
If it doesn't work, give a short info, then I fix it.

How you check it with MCT? I never tried this :)

@ghost ghost mentioned this issue Aug 25, 2019
@ghost
Copy link

ghost commented Aug 25, 2019

(doesn't work in detection mode - need to set for example mf_classic_1k) If it doesn't work, give a short info, then I fix it.
I'll give it a try when I'm booted into Windows again (only use Windows for games, so not signed into anything personal).

How you check it with MCT? I never tried this :)
I have a few key files from previous tags I have dumped. In MCT, I do this:

1.) Select "Read Tag"
2.) Select the key file I have, from a previous tag
3.) Select "Start mapping and read tag"

MCT will then attempt to authenticate with the Chameleon with the keys I told it to use, just like what a reader would do :)

@ghost
Copy link

ghost commented Aug 25, 2019

Ok thanks. Need to use MCT more :)
Me too - only Linux user - Win only for games and some GUI stuff

@ghost
Copy link

ghost commented Aug 25, 2019

Greetings, my fellow Linux user 🐱

  • Windows for games & password cracking with hashcat (pain controlling GPU overclocks and fan speeds on any Linux distro)
  • Manjaro Linux for everything else except Netflix (cuz DRM)
  • macOS for Netflix (faster than Windows, 1080p Netflix support on special titles, unix)

@nico0481
Copy link
Author

Hi Gtpy,

Thanks for the job!

I use your GUI Ver.: 1.1.0.4 and firmware update on chameleon is done.
Here are infor from GUI.
"ChameleonMini RevG 190321 using LUFA 151115 compiled with AVR-GCC 8.3.0. Based on the open-source NFC tool ChameleonMini. https://github.com/emsec/ChameleonMini commit 8a2755e"

MF_DETECTION is now in the pick list (new configuration), but I get "202:INVALID PARAMETER" in configuration field as soon as I try to select it.
Any idea of this issue?

Thank you
Best regards

Nico

@ghost
Copy link

ghost commented Sep 12, 2019

Hi Nico,

I think you compiled the firmware from emsec/Chameleon-Mini: Master Branch , right?
Because emsec not merged the detection feature yet, you’ll need to clone from my fork(gtpy:mfDetection) look at PR: #229

@nico0481
Copy link
Author

nico0481 commented Sep 12, 2019 via email

@ghost
Copy link

ghost commented Sep 14, 2019

Check out my repo for MF Detection support on the Rev G. It has had some changes made to it, for readers that check the card capacity.

Here is a pre-compiled version with the latest commits in my repo: https://github.com/lavanoid/ChameleonMini/releases/tag/BETA-RevG

@ceres-c
Copy link
Contributor

ceres-c commented Nov 1, 2019

I think it might be time to close this issue @geo-rg @david-oswald

@fptrs fptrs closed this as completed Nov 4, 2019
@Walter-Bishop
Copy link

I tried to use gtpy's code in #229 but it seems their GUI is not available any more 😢: https://gitlab.com/Gtpy/ChameleonMini-RevG_GUI

@nico0481 do you (or anyone else) still have a copy of it and could upload it here?

I changed the iceman firmware so that it allows to use the mfkey32 attack but it just returns a CRC checksum error. I assume there is some difference in how the data is being transmitted in the Rev. E rebooted firmware and in #229 but I couldn't find any specific difference yet.

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

4 participants