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

Add support for JSR305 @Detainted / @Tainted / @Untainted in the taint analysis #735

Open
gehel opened this issue May 3, 2024 · 0 comments

Comments

@gehel
Copy link

gehel commented May 3, 2024

Description

Adding support to JSR305 @Detainted / @tainted / @Untainted in the taint analysis would allow to more easily mark specific classes / methods to ignore some of the violations raised by find-sec-bugs.

For example, in the projects that I work with, we regularly have values coming from configuration files that we implicitly trust. We tend to ignore the warnings generated as false positives (with @SuppressFBWarning), but that will lead to less trust in the tools. We could use custom signatures / configuration to mark some of our own classes as trusted. Having a simple way to mark trusted classes directly in code via annotations seems simpler and helps improve the documentation of the code itself. Since JSR305 already provides annotations that match this use case, it seems like a good idea to use them.

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