Skip to content

All CVE scan for nodejsscan, eslint, and codeql. #70

Answered by esbena
tprokopcda asked this question in Q&A
Discussion options

You must be logged in to vote

Hi

Your observations match mine. But lets take a dive into some of the
results, to sanity check the nodejsscan behaviour. In conclusion, I
think everything is as it should be, and perhaps nodejsscan just
needs a minor tweak to support a few more CVEs.


From your screenshot, nodejsscan do produce a few good results for
the CWE-23 group. So lets investigate that.

$ bin/cli run --tool eslint-default --tool nodejsscan-default --tool codeql-default CWE-23
...
$ bin/cli report --kind server --tool eslint-default --tool nodejsscan-default --tool codeql-default CWE-23

From the overview, CVE-2017-16107 and CVE-2018-11798 appears
interesting to look at: in 5 of 6 cases, the vulnerability is
detec…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@tprokopcda
Comment options

Answer selected by tprokopcda
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants