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

Printing taint tracked instructions #18

Open
r00tus3r opened this issue Jun 30, 2022 · 3 comments
Open

Printing taint tracked instructions #18

r00tus3r opened this issue Jun 30, 2022 · 3 comments

Comments

@r00tus3r
Copy link

Hi,

I tried to print the instructions using taint tracked data by uncommenting the following code: https://github.com/AngoraFuzzer/libdft64/blob/master/src/libdft_api.cpp#L302

But it seems to print all the instructions which are executed after tainted = true set in here: https://github.com/AngoraFuzzer/libdft64/blob/master/src/syscall_hook.cpp#L19

Is there another way to print the taint tracked instructions?

@spinpx
Copy link
Member

spinpx commented Jul 1, 2022

It looks like there is no existed way to find tainted instructions. You may need to mark them respectively by yourself.

@r00tus3r
Copy link
Author

r00tus3r commented Jul 1, 2022

Alright, do you have any suggestions on what might be a good way to do that?

@spinpx
Copy link
Member

spinpx commented Jul 2, 2022

Sorry that I am not able to offer any good advice since the rules for taint propagation is too trivial.
e.g for binary ops, you may add hook for tag_combine to detect if it is tainted or not, but it does not works on mov instructions.

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

2 participants