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 is the result of running the OWASP dependency-check tool and addressing the vulnerabilities spotted in the report.
This is the OWASP Dependency-Check report after updating the references: dependency-check-report.html.zip
For those interested, the tool can be run locally by typing in the following command (provided you're at the project's root directory):
dependency-check --project "jPOS-EE" --scan="**/modules/**/build/install/**/**.jar" --format=HTML
(instructions on how to install it can be found here)
Back to the report, as you can see, it still shows 4 vulns. However:
a) one of them is a false-positive. The tool is confusing
jposee-db-mysql-2.2.8.jar
withmysql:mysql:2.2.8
, thus the confidence rate of 'Low' for this item in the report. This vulnerability can be safely dismissed.b) the other three are jPOS dependecies, so they can't be addressed in this project.
Apart from running the test suite locally, I went ahead and manually tried a local
qi-core
build in a couple of projects that use it. They both worked well.