OWASP Dependency-Check Maven Plugin: A Must-Have
Though it's tough, this developer admits he hadn't heard of this plugin until recently. If you're in the same boat, read to get an overview of this great security tool.
Join the DZone community and get the full member experience.Join For Free
I have to admit, with a high degree of shame, that I didn't know about the OWASP dependency check maven plugin. And seems to have been around since 2013. And, apparently, a thousand projects on GitHub are using it already.
In the past, I've gone manually through dependencies to check them against vulnerability databases, or, in many cases, I was just blissfully ignorant about any vulnerabilities that my dependencies had.
The purpose of this post is just that - to recommend the OWASP dependency check maven plugin as a must-have in practically every maven project (there are dependency-check tools for other build systems as well).
When you add the plugin it generates a report. Initially, you can go and manually upgrade the problematic dependencies (I upgraded two of those in my current project), or suppress the false positives (e.g. the Cassandra library is marked as vulnerable, whereas the actual vulnerability is that Cassandra binds an unauthenticated RMI endpoint, which I've addressed via my stack setup, so the library isn't an issue).
Then you can configure a threshold for vulnerabilities and fail the build if new ones appear - either by you adding a vulnerable dependency or in case a vulnerability is discovered in an existing dependency.
All of that is shown on the examples page and is pretty straightforward. I'd suggest adding the plugin immediately, it's a must-have:
<plugin> <groupId>org.owasp</groupId> <artifactId>dependency-check-maven</artifactId> <version>3.0.2</version> <executions> <execution> <goals> <goal>check</goal> </goals> </execution> </executions> </plugin>
It's not all roses, of course. People on Reddit complained that while the plugin caches stuff locally, it can still slow down your build significantly. So it is a good idea to exclude it from your general build and run it nightly in your CI system, and/or in your deployment pipeline.
Now, checking dependencies for vulnerabilities is just one small aspect of having your software secure and it shouldn't give you a false sense of security (a sort-of "I have my dependencies checked, therefore my system is secure" fallacy). But it's an important aspect. And having that check automated is a huge gain.
Published at DZone with permission of Bozhidar Bozhanov, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.