CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2018 · Vmware

CVE-2018-15756
Vmware Spring Framework vulnerability

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.

Affected products

Spring Framework, Agile Plm, Communications Brm - Elastic Charging Engine, Communications Converged Application Server - Service Controller, Communications Diameter Signaling Router, Communications Element Manager, Communications Online Mediation Controller, Communications Session Report Manager, Communications Session Route Manager, Communications Unified Inventory Management and more. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Vmware Spring Framework runs anywhere in your environment, including systems of suppliers.
  • UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
  • Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.

References

More vulnerabilities in Vmware products

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.