Spring Boot Welcome Page Denial of Service
Published 26 May 2023 · Updated 21 Feb 2024
Is your project on an affected org.springframework.boot:spring-boot-autoconfigure?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=3.0.0 <3.0.7
- Fixed in
- 3.0.7
mvn versions:use-dep-version -Dincludes=org.springframework.boot:spring-boot-autoconfigure -DdepVersion=3.0.7 -DforceVersion=true- Affected
- >=2.7.0 <2.7.12
- Fixed in
- 2.7.12
mvn versions:use-dep-version -Dincludes=org.springframework.boot:spring-boot-autoconfigure -DdepVersion=2.7.12 -DforceVersion=true- Affected
- >=2.6.0 <2.6.15
- Fixed in
- 2.6.15
mvn versions:use-dep-version -Dincludes=org.springframework.boot:spring-boot-autoconfigure -DdepVersion=2.6.15 -DforceVersion=true- Affected
- <2.5.15
- Fixed in
- 2.5.15
mvn versions:use-dep-version -Dincludes=org.springframework.boot:spring-boot-autoconfigure -DdepVersion=2.5.15 -DforceVersion=trueDetails
In Spring Boot versions 3.0.0 - 3.0.6, 2.7.0 - 2.7.11, 2.6.0 - 2.6.14, 2.5.0 - 2.5.14 and older unsupported versions, there is potential for a denial-of-service (DoS) attack 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 makes use of Spring Boot's welcome page support, either static or templated.
- Your application is deployed behind a proxy which caches 404 responses.
Your application is NOT vulnerable if any of the following are true:
- Spring MVC auto-configuration is disabled. This is true if WebMvcAutoConfiguration is explicitly excluded, if Spring MVC is not on the classpath, or if spring.main.web-application-type is set to a value other than SERVLET.
- The application does not use Spring Boot's welcome page support.
- You do not have a proxy which caches 404 responses.
Affected Spring Products and Versions
Spring Boot
3.0.0 to 3.0.6 2.7.0 to 2.7.11 2.6.0 to 2.6.14 2.5.0 to 2.5.14
Older, unsupported versions are also affected Mitigation
Users of affected versions should apply the following mitigations:
- 3.0.x users should upgrade to 3.0.7+
- 2.7.x users should upgrade to 2.7.12+
- 2.6.x users should upgrade to 2.6.15+
- 2.5.x users should upgrade to 2.5.15+
Users of older, unsupported versions should upgrade to 3.0.7+ or 2.7.12+.
Workarounds: configure the reverse proxy not to cache 404 responses and/or not to cache responses to requests to the root (/) of the application.
Is GHSA-xf96-w227-r7c4 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.springframework.boot:spring-boot-autoconfigure, and gives you the command that fixes it.
More advisories for org.springframework.boot:spring-boot-autoconfigure
- MediumCVE-2026-41001Spring Boot: Predictable Temp Directory in Artemis Auto-configuration · 11 Jun 2026
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2023-20883
- Linkgithub.com/spring-projects/spring-boot/issues/35552
- Linkgithub.com/spring-projects/spring-boot/commit/418dd1ba5bdad79b55a043000164bfcbda2acd78
- Packagegithub.com/spring-projects/spring-boot
- Linkgithub.com/spring-projects/spring-boot/releases/tag/v2.5.15
- Linkgithub.com/spring-projects/spring-boot/releases/tag/v2.6.15
- Linkgithub.com/spring-projects/spring-boot/releases/tag/v2.7.12
- Linksecurity.netapp.com/advisory/ntap-20230703-0008
- Linkspring.io/security/cve-2023-20883
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.