[#887] Add OWASP dependency check plugin #890
Open
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
…urrently replacing dependencies listed in the build.gradle file with the ones referenced in the toml file
…ndencies versions and the ci/cd pipeline in git. will update each depedency slowly to ensure that upgrades are down correctly.
…github's ci/cd is happy still with these set of changes.
…github's ci/cd is happy still with these set of changes (again)
…github's ci/cd is happy still with these set of changes (again) partIII
…is happy still with these set of changes (again)
…s happy still with these set of changes (again)
…ansition to newer spring.
…an unused dependency.
…tical vulnerable dependendcies
…guring what to do with the remaining vulnerabilities.
…, now figuring what to do with the remaining vulnerabilities.
…ability issues will be addressed in another PR. I've cut down vulnerabilities by quite a lot and I want to test the new OWASP plugin against the remaining vulnerabilities.
…es and removed unused one.
…leproperties-file' into v3_issue_887-add-owasp-dependency-check
…quent runs took about 2-4 minutes. Plugin downloads the NVD (National Vulnerability Database) the very first time the user runs the analyzeDependency command (assuming said user does not already have it cached somewhereon their system. Once downloaded, the plugin checks the subprojects dependenies against that of the NVD's and creates an HTML report per subproject on all the critical dependencies subproject has.
… with spring junit.
…leproperties-file' into v3_issue_887-add-owasp-dependency-check
…ept for HIRS_CA and HIRS_CAportal modules.
…is are found in just the CA Portal dependency. While the appliation builds and runs well as a service, currently running into issues with fixing these dependencies.
…tain vulnerabilites can't be fixed due to the fact that they have to be fixed by outside entities.
ThatSilentCoder
changed the title
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.
Description
Add a new Gradle plugin that can detect critical dependencies.
Notes
When I added this plugin for the first time to the application and ran the dependencyCheck tasks that this plugin provides, the task took about 40 minutes to run. The reason why it took so long on the very first attempt is because this plugin downloads the NVD (National Vulnerability Database) and caches it somewhere in your system so that in future gradle runs, the plugin can check against the cached database. After the first run, it takes on average between 2-3 minutes per run and if you ever feel the need to upgrade your cached vulnerability database, you can run the
./gradlew dependencyCheckUpdatecommand.To see all the tasks that this plugin provides, run ./gradle tasks and go to the dependency-check tasks section.
Test Instructions
Warning: Cannot be merged until the last PR I created has been merged into main.