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

Change SDK exclusion method #10

Open
zerjioang opened this issue Sep 20, 2016 · 0 comments
Open

Change SDK exclusion method #10

zerjioang opened this issue Sep 20, 2016 · 0 comments

Comments

@zerjioang
Copy link
Member

Current algorithm that detects whether a given class belongs to a java sdk is based on full classname matching (package+classname). This has to be change since bad guys can use package name spoofing to invalidate their class analysis and bypass the scan.

For this reason, the next iteration on this algorithm has to be based on class method enumaration, matching and opcode sequence matching. If the analyzed class has the same number of methods, the same method declarations and the code of the methods is very very very close, then the class belongs to android SDK and will not be analyzed.

@zerjioang zerjioang modified the milestone: Droidefense 0.2.0 Oct 14, 2016
@zerjioang zerjioang removed this from the Droidefense CLI milestone May 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

1 participant