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

Do we need to change the contents of AF.json if we are using a different board? #20

Open
GM-repo opened this issue Apr 24, 2023 · 1 comment

Comments

@GM-repo
Copy link

GM-repo commented Apr 24, 2023

I am trying to replicate the BIAS attack using a CYW920719B2Q40EVB-01 board, since the board used in the paper (CYW920819EVB-02 evaluation board) is discontinued and not available in the market anymore.

While executing the 'make bias' command to impersonate the target, I am getting the following error: "patchRom: 'PATCHRAM _TARGET _TABLE ADDRESS' not in fw.py. FEATURE NOT SUPPORTED!" As a result of this error, I am unable to achieve the "Ready to connect to a victim slave" state. Could it be because the attack file AF.json (https://github.com/francozappa/bias/blob/master/bias/AF.json) might not be compatible with the board that we are using? As far as I understood from the paper, the addresses specified in the AF.json file indicate the addresses of the functions that are patched by the bias.py code. Do we need to change the addresses if we are using a different board? If so, how we can derive these addresses? Any suggestions regarding this would be highly appreciated.

@ghost
Copy link

ghost commented May 16, 2023

This is InternalBlue side, the board you are using is not fully reverse engineered, so in fw/fw_0xxxx.py the patchram target table address is not there. You could try reverse engineering the board yourself, or purchase another board. It could also be possible to pattern match your boards memdump with another to see where that address starts at but that may not be possible.

AF.json contains addresses for the board used in the paper, and I believe newer version of the board.

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

1 participant