Execution of the Maven plugin Dependency-Check, as well as evaluation and correction of the vulnerabilities found.
The previous Dependency-Check version was outdated and has been updated. A change is required to run the new version.
Code migration
Since some versions the Dependency-Check plugin of OWASP uses the NVD API to perform updates before the check. This basically works just like that, but usually takes a lot of time (in a personal test ~7-10 minutes for 25%).
If you store an NVD API key, this step is much quicker (in my personal test just under 3 minutes in total). However, as this key should not be public for security reasons, it must be stored manually locally on the computer.
To do this, the settings.xml file must be opened in the local .m2 folder (Maven Repository Location). The following code must now be inserted in the <servers>...</servers> section:
<!-- For NVD API --> <server> <id>nvd-api-key</id> <password>***</password> </server>
The asterisks in the password section <password>***</password> must be replaced by the key.
Test
Run the Mavengoal mvn dependency-check:aggregate on tl-parent-all in the terminal or Jenkins.