You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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:
Look into KernelCustomizations for the specific changes we made to analyze kernel drivers.
Look into SoundyAliasAnalysis.cpp to know, How we start the tainting process for each entry point.
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!
The text was updated successfully, but these errors were encountered: