Spring Framework up to 4.2.x/4.3.19/5.0.9/5.1.0 Range resource management

Summaryinfo

A vulnerability marked as problematic has been reported in Spring Framework up to 4.2.x/4.3.19/5.0.9/5.1.0. Affected is an unknown function of the component Range Handler. This manipulation causes resource management. This vulnerability appears as CVE-2018-15756. The attack may be initiated remotely. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Spring Framework up to 4.2.x/4.3.19/5.0.9/5.1.0. It has been declared as problematic. Affected by this vulnerability is an unknown code of the component Range Handler. The manipulation with an unknown input leads to a resource management vulnerability. The CWE definition for the vulnerability is CWE-399. As an impact it is known to affect availability. The summary by CVE is:

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.

The bug was discovered 10/16/2018. The weakness was presented 10/18/2018 (Website). The advisory is shared at pivotal.io. This vulnerability is known as CVE-2018-15756 since 08/23/2018. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.

The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $0-$5k.

Upgrading to version 4.3.20 or 5.0.10 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 105703†). See VDB-133726, VDB-133727, VDB-137948 and VDB-137949 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Spring Framework

Version

• 4.0
• 4.1
• 4.2
• 4.3.0
• 4.3.1
• 4.3.2
• 4.3.3
• 4.3.4
• 4.3.5
• 4.3.6
• 4.3.7
• 4.3.8
• 4.3.9
• 4.3.10
• 4.3.11
• 4.3.12
• 4.3.13
• 4.3.14
• 4.3.15
• 4.3.16
• 4.3.17
• 4.3.18
• 4.3.19
• 5.0
• 5.0.0
• 5.0.1
• 5.0.2
• 5.0.3
• 5.0.4
• 5.0.5
• 5.0.6
• 5.0.7
• 5.0.8
• 5.0.9
• 5.1.0

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion