Description

Spring Cloud Netflix, versions 2.2.x prior to 2.2.4, versions 2.1.x prior to 2.1.6, and older unsupported versions allow applications to use the Hystrix Dashboard proxy.stream endpoint to make requests to any server reachable by the server hosting…

Description

Spring Integration framework provides Kryo Codec implementations as an alternative for Java (de)serialization. When Kryo is configured with default options, all unregistered classes are resolved on demand. This leads to the "deserialization gadgets…

Description

When configured to enable default typing, Jackson contained a deserialization vulnerability that could lead to arbitrary code execution. Jackson fixed this vulnerability by blacklisting known "deserialization gadgets".

Spring Batch configures Jackson with global default typing enabled which means that through the previous exploit, arbitrary code could be executed if all of the following is true:

• Spring Batch’s Jackson support is being leveraged to serialize a job’s ExecutionContext.
• A malicious user gains write access to the data store used by the JobRepository (where the data to be deserialized is stored).

In order to protect against this type of attack, Jackson prevents a set of untrusted gadget classes from being deserialized. Spring Batch should be proactive against blocking unknown “deserialization gadgets” when enabling default typing.

Affected Spring Products and Versions

• Spring Batch
  • 4.0.0 to 4.0.4
  • 4.1.0 to 4.1.4
  • 4.2.0 to 4.2.2

Mitigation

Users of an affected version should upgrade to 4.2.3 or later.  Releases that have fixed this issue include:

• Spring Batch
  • 4.2.3

Credit

This issue was identified and responsibly reported by Srikanth…

Description

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

Description

Spring Security versions 5.2.x prior to 5.2.4 and 5.3.x prior to 5.3.2 contain a signature wrapping vulnerability during SAML response validation. When using the spring-security-saml2-service-provider component, a malicious user can carefully…

Description

Spring Security versions 5.3.x prior to 5.3.2,  5.2.x prior to 5.2.4,  5.1.x prior to 5.1.10, 5.0.x prior to 5.0.16 and 4.2.x prior to 4.2.16 use a fixed null initialization vector with CBC Mode in the implementation of the queryable text encryptor…

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…

Description

Reactor Netty HttpClient, versions 0.9.x prior to 0.9.5, and versions 0.8.x prior to 0.8.16, may be used incorrectly, leading to a credentials leak during a redirect to a different domain. In order for this to happen, the HttpClient must have been…

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…

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

• https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/reflected-file-download-a-new-web-attack-vector/
• https://github.com/spring-projects/spring-framework/issues/24220
…