Java: Convert security queries to path-problem. #480
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aschackmull
added
depends on internal PR
aschackmull
force-pushed
the
java/path-problem-conversion
branch
from
e9e9cd1 to
918fc90
Compare
yh-semmle
approved these changes
Nov 19, 2018
cklin
pushed a commit
that referenced
this pull request
May 23, 2022
Add preliminary support for go 1.16
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This add path explanations to most of the security queries. A few queries were left out since they didn't follow the general pattern:
CWE-209/StackTraceExposure.qlreports results based on a disjunction of 3 configurations, and theCWE-312/ClearTextStorage*.qljoins several flow configurations.This depends on an internal PR for updating of internal tests.