Denial of Service (DoS) Affecting org.springframework.boot:spring-boot-autoconfigure package, versions [,2.5.15)[2.6.0,2.6.15)[2.7.0,2.7.12)[3.0.0,3.0.7)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Denial of Service (DoS) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JAVA-ORGSPRINGFRAMEWORKBOOT-5564390
- published19 May 2023
- disclosed19 May 2023
- creditMartin van Kervel Smedshammer
Introduced: 19 May 2023
CVE-2023-20883 (opens in a new tab)How to fix?
Upgrade org.springframework.boot:spring-boot-autoconfigure to version 2.5.15, 2.6.15, 2.7.12, 3.0.7 or higher.
Overview
Affected versions of this package are vulnerable to Denial of Service (DoS) if Spring MVC is used together with a reverse proxy cache.
Specifically, an application is vulnerable if all of the conditions are true:
- The application has Spring MVC auto-configuration enabled. This is the case by default if Spring MVC is on the classpath.
- The application uses Spring Boot's welcome page support, either static or templated.
- The application is deployed behind a proxy which caches 404 responses.
The application is NOT vulnerable if any of the following are true:
- Spring MVC auto-configuration is disabled. This is true if
WebMvcAutoConfigurationis explicitly excluded, if Spring MVC is not on the classpath, or ifspring.main.web-application-typeis set to a value other thanSERVLET. - The application does not use Spring Boot's welcome page support.
- There is no proxy which caches 404 responses.
Workaround
Users who are unable to upgrade should configure the reverse proxy not to cache 404 responses and/or not to cache responses to requests to the root (/) of the application.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
wspackage