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.
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.
Are there any known weaknesses in the ata5577 password protection mode?
or wake with password mode?
or block locking bits?
(Other than snooping the writing of the tag.)
Offline
By the simple one I understood from it, is the block lock bits is wrong then the password block could be read.
Offline
Not sure about that, but I know if the config block is set wrong it (to output 7 blocks) it will transmit all its memory including the block used as a password. But that is why the spec docs tell you not to set that to 7 if you use the password mode.
Offline
yup, thats what I meant.
but how many hasn't gotten that wrong?
How about adding a pwd to a t55x7 tag and see if there are any timings issues, (like an oracle attack) for wrong vs correct password. If we can get that down, it will be easy to bruteforce it. Or what do you think?
Offline
This is a good idea iceman.
Offline
So the idea is it would take a different amount of time to reject the bad password for each correct byte guessed correctly?
Offline
Yes, that would be the assumption we'll be trying to verify. Somewhere the line that a bad password gets rejected faster OR slower than a correct one.
We'll need to time it.. but then t55x7 might not respond to a faulty pwd command but silently discard it.
Offline
The tag may not respond on a bad password but there may be an interruption to the data stream it is always outputting (except wake on password configured cards.)
Offline
However, I have no clue how we could measure the time accurate enough to tell anyway, it would no doubt be very small.
Offline
well, research, or the wild frontier!
Offline