In the world of software development, managing dependencies is a core part of creating strong and secure applications. Spring Boot, a favorite among Java developers, makes building applications easier, but there's more to it than meets the eye. Keeping your dependencies in check is crucial to ensure that your Spring Boot projects run smoothly and remain resilient in the face of ever-evolving threats.
One critical aspect of Spring Boot dependency management is security. Software vulnerabilities are discovered frequently, and by keeping your project's dependencies up to date, you're essentially putting on your digital security armor. Outdated dependencies can be like unlocked doors, inviting trouble from potential threats, and that's something we'd like to avoid.
Software composition analysis (SCA) tools are a very useful tool for developers. They cover an easy solution to managing dependencies, handling security vulnerabilities, navigating licensing issues, and ensuring compliance in your software projects. By using Snyk Open Source as your SCA, you can easily find out if your Spring Boot packages contain vulnerabilities.
In the case of my example project, I found multiple vulnerabilities. The first is a high-severity security issue in
netty-codec-http2. This is a transitive dependency brought in by my
spring-boot-start-webflux, as you can see below.
The second vulnerability I would like to discuss is a medium severity arbitrary code execution issue brought in via the
snakeyaml package. This is also a transitive dependency, this time brought in by
I won’t go into the actual problem of individual vulnerabilities today, but you can check out the dedicated blog post for more information on the
snakeyaml problem. Let’s focus on solving the problem and implementing the best solution.
For the first vulnerability, there is a clear fix described. My application is based on Spring Boot 2.7.16, and therefore, the
spring-boot-starter-webflux is also on version 2.7.16.
Updating the Webflux starter to 2.7.17 should fix the problem. There are multiple way
s of doing this, but not all are recommended.
Typically, your spring boot manifest looks something like the following code:
id 'org.springframework.boot' version '2.7.16'
id 'io.spring.dependency-management' version '1.1.3'
The version number of the individual
spring-boot-starters are derived from the
spring-boot-starter-parent (Maven) or the
org.springframework.boot plugin in Gradle.
The main reason for this is that all these starter packages belong to the same release of Spring and are tested as such.
When looking at the first vulnerability found in my project, the fix suggestion is to update
spring-boot-starter-webflux to version 2.7.17 to solve the high-severity security vulnerability. This suggests that I only have to fix the Webflux package, which I can do by specifying a specific version like the one below.
But stop right here! This is not the recommended way of solving the problem. The specific version, 2.7.17, is used over the parent version. While this might work since this is a patch version release, it isn’t the best or most secure solution. Since semver does not guarantee that API’s stay intact, we can’t be sure this will work. But the most important argument is that there probably is a full new release of Spring Boot.
Remember that I told you earlier that these starters belong together? Therefore the best thing you can do is update your complete Spring Boot distribution to 2.7.17. This is even more important when talking about minor or major releases of a package — which can break API and not run smoothly together. So, in this example, do the following. Update the parent (Maven) or the plugin (Gradle) instead of the individual starters.
id 'org.springframework.boot' version '2.7.17'
I would advise everyone to go the extra mile and update their entire spring boot version to the latest appropriate version. To find out what that is, simply go to https://start.spring.io.
For the second issue, Snyk discovered that there is no clear remediation advice in my appliation. Currently, there is also no available version of a
spring-boot-starter that does not have this insecure transitive dependency. What we do know is that there is an updated version of the transitive dependency available. Updating to
snakeyaml 2.0 will solve the problem.
Once again, I want to emphasize that this is just an example. There might already be an updated version of a
spring-boot-starter available by the time you read this, so be sure to double-check. To learn about the SnakeYaml vulnerability, please check our dedicated blog post on this topic.
The first thing you should do is check of the version of the package you want to update is a property in Spring Boot. The Spring Boot docs contain an appendix with the dependency versions for the specific release. You can also find the version properties in there. These properties can be overridden in both Maven and Gradle, so it uses a newer version of the transitive dependency.
For maven, you can add a property in the properties section.
For Gradle, we can edit this property in a
This is the preferred way over dependency management since
snakeyaml is just a single library. However, in many cases, it is more than one library. The version can refer to a BOM (bill of materials), not to be confused with an SBOM, representing a set of groups of packages that need to be used together and essentially have the same version — such as an API and an implementation package. Both need to be on the same version to perform as expected.
An alternative option is to use the mechanisms in your build tool to update transitive dependencies. This should only be used if you cannot update the version property as shown in the previous section
For Maven, it’s most commonly added to the
dependencyManagement block. This block will ensure that the updated version mentioned in the
dependencyManagement block is used every time the library is called as a transitive dependency.
Since we use the dependency-management plugin for Spring in our Gradle file, we have pretty similar capabilities for Gradle available. Note that this plugin was inserted by the Spring Boot initializer when scaffolding my project.
If you don't use the
io.spring.dependency-management plugin, you can also add constraints to transitive dependencies in Gradle to update a transitive dependency like the one below. Remember that these constraints do not play well with the Spring
dependency-management plugin. So it is either one or the other.
because 'previous versions have a security issue'
Scanning your Spring Boot application with Snyk is essential for ensuring the security and stability of your software. Snyk helps identify in your application's dependencies, which can be exploited by malicious actors if left unaddressed. After reading this article, you also know what the best way is to implement the remediation advice provide by Snyk.
Regularly scanning your codebase proactively addresses security issues and reduces the risk of data breaches and other security incidents. So make sure that scanning is part of your regular flow and that you are well aware of how to respond when a vulnerability occurs.
Below, I scanned my application with the Snyk CLI both before and after remediation. The remediation path I chose was updating the general Spring Boot version and updating the specific version property for
- Update your general Spring Boot version over updating a specific starter.
- Updating the version properties of the Spring Boot dependencies when updating the Spring Boot version is insufficient.
- Use dependency management in Maven or Gradle to update specific transitive dependencies.