-
-
Notifications
You must be signed in to change notification settings - Fork 584
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
False positive on token_fail_reason #843
Labels
bug
Something isn't working
Comments
3 tasks
Looks like a false positive as a result of #766 which now examines function calls with attributes that have the word "token" within them. The hardcoded password/token/etc check tends to have a lower confidence to detect guaranteed cases of a hardcoded secret. You can always add |
Segelzwerg
added a commit
to Whist-Team/Whist-Server
that referenced
this issue
Mar 5, 2022
jshcodes
added a commit
to CrowdStrike/falconpy
that referenced
this issue
Mar 9, 2022
Relates to PyCQA/bandit#843
jshcodes
added a commit
to CrowdStrike/falconpy
that referenced
this issue
Mar 9, 2022
Relates to PyCQA/bandit#843
2 tasks
jshcodes
added a commit
to CrowdStrike/falconpy
that referenced
this issue
Mar 10, 2022
Relates to PyCQA/bandit#843
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Up until this latest release, our bandit workflows have delivered passing results without issue. With our latest commit, 1.7.3 was installed and our unit testing failed with the following:
Impacted code block
Reproduction steps
Expected behavior
I don't believe there is a problem with the code above.
Bandit version
1.7.3 (Default)
Python version
3.10 (Default)
Additional context
Appears to be similar to issue #842.
The text was updated successfully, but these errors were encountered: