Denial of Service in Spring Framework
High severity
GitHub Reviewed
Published
Jun 15, 2020
to the GitHub Advisory Database
•
Updated Jun 5, 2024
Package
Affected versions
>= 5.1.0.RELEASE, < 5.1.1.RELEASE
>= 5.0.0.RELEASE, < 5.0.10.RELEASE
>= 4.2.0.RELEASE, < 4.3.20.RELEASE
Patched versions
5.1.1.RELEASE
5.0.10.RELEASE
4.3.20.RELEASE
Description
Published by the National Vulnerability Database
Oct 18, 2018
Reviewed
Jun 11, 2020
Published to the GitHub Advisory Database
Jun 15, 2020
Last updated
Jun 5, 2024
Credits
-
SunBK201 Analyst
Spring Framework, version 5.1, versions 5.0.x prior to 5.0.10, versions 4.3.x prior to 4.3.20, and older unsupported versions on the 4.2.x branch provide support for range requests when serving static resources through the ResourceHttpRequestHandler, or starting in 5.0 when an annotated controller returns an org.springframework.core.io.Resource. A malicious user (or attacker) can add a range header with a high number of ranges, or with wide ranges that overlap, or both, for a denial of service attack. This vulnerability affects applications that depend on either spring-webmvc or spring-webflux. Such applications must also have a registration for serving static resources (e.g. JS, CSS, images, and others), or have an annotated controller that returns an org.springframework.core.io.Resource. Spring Boot applications that depend on spring-boot-starter-web or spring-boot-starter-webflux are ready to serve static resources out of the box and are therefore vulnerable.
References