CVE-2020-5403: DoS Via Malformed URL with Reactor Netty HTTP Server

MEDIUM | FEBRUARY 27, 2020 | CVE-2020-5403

Description

Reactor Netty HttpServer, versions 0.9.3 and 0.9.4, is exposed to a URISyntaxException that causes the connection to be closed prematurely instead of producing a 400 response.

Affected Spring Products and Versions

  • Reactor Netty
    • 0.9.3
    • 0.9.4

Mitigation

Users of affected versions should upgrade to 0.9.5 (reactor-bom Dysprosium SR-5). No other steps are necessary.

  • Reactor Netty
    • 0.9.5

Credit

This issue was…

CVE-2020-5405: Directory Traversal with spring-cloud-config-server

HIGH | FEBRUARY 26, 2020 | CVE-2020-5405

Description

Spring Cloud Config, versions 2.2.x prior to 2.2.2, versions 2.1.x prior to 2.1.7, and older unsupported versions allow applications to serve arbitrary configuration files through the spring-cloud-config-server module. A malicious user, or attacker…

CVE-2020-5398: RFD Attack via “Content-Disposition” Header Sourced from Request Input by Spring MVC or Spring WebFlux Application

HIGH | JANUARY 16, 2020 | CVE-2020-5398

Description

In Spring Framework, versions 5.2.x prior to 5.2.3, versions 5.1.x prior to 5.1.13, and versions 5.0.x prior to 5.0.16, an application is vulnerable to a reflected file download (RFD) attack when it sets a “Content-Disposition” header in the response where the filename attribute is derived from user supplied input.

Specifically, an application is vulnerable when all of the following are true:

  • The header is prepared with org.springframework.http.ContentDisposition.
  • The filename is set via one of:
    • ContentDisposition.Builder#filename(String), or
    • ContentDisposition.Builder#filename(String, US_ASCII)
  • The value for the filename is derived from user supplied input.
  • The user supplied input is not sanitized by the application.
  • The downloaded content of the response is injected with malicious commands by the attacker (see RFD paper reference for details).

An application is not vulnerable if any of the following is true:

  • The application does not set a “Content-Disposition” response header.
  • The header is not prepared with org.springframework.http.ContentDisposition.
  • The filename is set via one of:
    • ContentDisposition.Builder#filename(String, UTF_8), or
    • ContentDisposition.Builder#filename(String, ISO_8859_1)
  • The filename is not derived from user supplied input.
  • The filename is derived from user supplied input but sanitized by the application.

Affected Spring Products and Versions

  • Spring Framework
    • 5.2.0 to 5.2.2
    • 5.1.0 to 5.1.12
    • 5.0.0 to 5.0.15

Mitigation

Users of affected versions should apply the following mitigation. 5.2.x users should upgrade to 5.2.3. 5.1.x users should upgrade to 5.1.13. 5.0.x users should upgrade to 5.0.16. No other steps are necessary.  Releases that have fixed this issue include:

  • Spring Framework
    • 5.2.3
    • 5.1.13
    • 5.0.16

Credit

This issue was identified and responsibly reported by Roman Shalymov from EPAM.

References

Get ahead

VMware offers training and certification to turbo-charge your progress.

Learn more

Get support

Tanzu Spring offers support and binaries for OpenJDK™, Spring, and Apache Tomcat® in one simple subscription.

Learn more

Upcoming events

Check out all the upcoming events in the Spring community.

View all