Change API of vulnerability.csv
#117
Merged
Conversation
This file contains 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
…into vuln_api_change
…into vuln_api_change
…into vuln_api_change
…into vuln_api_change
…into vuln_api_change
…ns. Add functionList to vulnerability.csv
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 pr adds more debug information into
vulnerability.csv.Two lists are also output, which can be used to produce a callstack to better track a vulnerability:
original_statement_listcontaining a list of n statements corresponding to private function calls that can be used to get to the vulnerable statemet, and ending with the statement the vulnerability was located infunction_listcontaining a list of n functions called to get to the vulnerable statementWe currently chose to only output a single callstack for each vulnerability instance.
We also now output both a csv and json file for vulnerabilities.