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

NFC 0.69.1 Can not parse file #1904

Closed
Antiarchitect opened this issue Oct 21, 2022 · 7 comments
Closed

NFC 0.69.1 Can not parse file #1904

Antiarchitect opened this issue Oct 21, 2022 · 7 comments
Assignees
Labels
Bug NFC NFC-related

Comments

@Antiarchitect
Copy link

Describe the bug.

I have two phones with NFC chips. Reading one (One Plus 7) goes normally and I can Emulate UID normally. But have issues with another one which is Honor 50: I can read NFC and save it but selecting saved file tells Can not parse file and thus I have no actions menu (UX bug) so I cannot even delete it.
image
image

Reproduction

  1. Go to NFC
  2. Select Read
  3. Read Honor 50 with NFC turned on
  4. Save and name
  5. Try to select the file in Saved section

Target

No response

Logs

No response

Anything else?

No response

@gornekich
Copy link
Member

Hello @Antiarchitect !
Could you please share the content of the saved file? Nfc type and UID fields in particular

@gornekich
Copy link
Member

Not UID, but it's length

@Antiarchitect
Copy link
Author

Will try to extract the file a bit later :)

@Antiarchitect
Copy link
Author

Filetype: Flipper NFC device
Version: 2
Device type: UID
UID: 00 00 00 00 00 00 00 00 00 00
ATQA: 00 00
SAK: 00

@skotopes skotopes added the NFC NFC-related label Oct 22, 2022
@LowSkillDeveloper
Copy link

I have the same problem with my bus pass.

Filetype: Flipper NFC device
Version: 2
# Nfc device type can be UID, Mifare Ultralight, Mifare Classic, Bank card
Device type: Mifare DESFire
# UID, ATQA and SAK are common for all formats
UID: 04 73 43 85 97 7D 80
ATQA: 44 03
SAK: 20
# Mifare DESFire specific data
PICC Version: 04 01 01 01 00 1A 05 04 01 01 01 04 1A 05 04 73 43 85 97 7D 80 B9 0C 22 41 50 05 22
PICC Free Memory: 1312
PICC Change Key ID: 00
PICC Config Changeable: true
PICC Free Create Delete: false
PICC Free Directory List: true
PICC Key Changeable: true
PICC Max Keys: 01
PICC Key 0 Version: 00
Application Count: 10
Application IDs: D0 02 F4 70 02 F0 60 34 F5 10 20 F1 50 89 F8 20 20 F1 80 10 F1 A0 11 F1 0B 10 00 FF FF FF

Screenshot_20221028-182105_Flipper

@mh-
Copy link
Contributor

mh- commented Nov 22, 2022

I have the same problem with my bus pass.

Ok, yes that's the same problem as in #2040 - the DESFire import

bool nfc_device_load_mifare_df_app(FlipperFormat* file, MifareDesfireApplication* app) {

expects details about the key for each application.

If you modify the file like this

Filetype: Flipper NFC device
Version: 2
# Nfc device type can be UID, Mifare Ultralight, Mifare Classic, Bank card
Device type: Mifare DESFire
# UID, ATQA and SAK are common for all formats
UID: 04 73 43 85 97 7D 80
ATQA: 44 03
SAK: 20
# Mifare DESFire specific data
PICC Version: 04 01 01 01 00 1A 05 04 01 01 01 04 1A 05 04 73 43 85 97 7D 80 B9 0C 22 41 50 05 22
PICC Free Memory: 1312
PICC Change Key ID: 00
PICC Config Changeable: true
PICC Free Create Delete: false
PICC Free Directory List: true
PICC Key Changeable: true
PICC Max Keys: 01
PICC Key 0 Version: 00
Application Count: 0

i.e. set Application Count to 0, Flipper can read the file and emulate the UID.

But: I would advise against trying that UID in an actual bus, assuming that you are not the owner of the bus company or authorized to do penetration testing by them. And also, it is unlikely that such a system will accept the clone just based on the UID.

@skotopes
Copy link
Member

Fixed in #2041 thanks to @mh-

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

No branches or pull requests

5 participants