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

How can I use dr_checker to do common static analysis? #14

Open
tomgu1991 opened this issue Sep 26, 2017 · 2 comments
Open

How can I use dr_checker to do common static analysis? #14

tomgu1991 opened this issue Sep 26, 2017 · 2 comments

Comments

@tomgu1991
Copy link

Hi,

Well, it is interesting to use this tool to analyze vulnerabilities in drivers. But can I use it for common static analysis?

Basically, I have a single file with a makefile file. Can I use dr_checker to detect vulnerabilities? Furthermore, I have a buildable project with a makefile.

Can anyone show me the detail steps?

Thanks!

@Machiry
Copy link
Contributor

Machiry commented Sep 27, 2017

As of now, DR.CHECKER is customized to analyzing the kernel code. We may in near future ( ~ 1 month) release a general purpose taint based vulnerability finding tool based on the DR.CHECKER principles.

However, you can give it a try. Following are the two places you can start with:

  1. Look into KernelCustomizations for the specific changes we made to analyze kernel drivers.
  2. Look into SoundyAliasAnalysis.cpp to know, How we start the tainting process for each entry point.

@ch1dyc4t
Copy link

ch1dyc4t commented Mar 8, 2018

Hey,@Machiry

When will the general vulnerabilities detection version be released?

I also want to use dr_checker to detect vulnerabilities in my project which is written by C with makefile.

Thank you.

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

3 participants