[Security] Bump spring-core from 3.2.1.RELEASE to 4.3.21.RELEASE

[dependabot-preview]

Bumps spring-core from 3.2.1.RELEASE to 4.3.21.RELEASE. This update includes security fixes.

Vulnerabilities fixed

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects org.springframework:spring-core and org.springframework.security:spring-security-core Both Spring Security 3.2.x, 4.0.x, 4.1.0 and the Spring Framework 3.2.x, 4.0.x, 4.1.x, 4.2.x rely on URL pattern mappings for authorization and for mapping requests to controllers respectively. Differences in the strictness of the pattern matching mechanisms, for example with regards to space trimming in path segments, can lead Spring Security to not recognize certain paths as not protected that are in fact mapped to Spring MVC controllers that should be protected. The problem is compounded by the fact that the Spring Framework provides richer features with regards to pattern matching as well as by the fact that pattern matching in each Spring Security and the Spring Framework can easily be customized creating additional differences.

Affected versions: < 4.3.1

Sourced from The GitHub Security Advisory Database.

High severity vulnerability that affects org.springframework:spring-core Under some situations, the Spring Framework 4.2.0 to 4.2.1, 4.0.0 to 4.1.7, 3.2.0 to 3.2.14 and older unsupported versions is vulnerable to a Reflected File Download (RFD) attack. The attack involves a malicious user crafting a URL with a batch script extension that results in the response being downloaded rather than rendered and also includes some input reflected in the response.

Affected versions: > 3.2.0, < 3.2.15

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects org.springframework:spring-core Pivotal Spring Framework before 3.2.14 and 4.x before 4.1.7 do not properly process inline DTD declarations when DTD is not entirely disabled, which allows remote attackers to cause a denial of service (memory consumption and out-of-memory errors) via a crafted XML file.

Affected versions: < 3.2.14

Sourced from The GitHub Security Advisory Database.

High severity vulnerability that affects org.springframework:spring-core Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.16 and older unsupported versions, allow applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through the spring-messaging module. A malicious user (or attacker) can craft a message to the broker that can lead to a remote code execution attack. This CVE addresses the partial fix for CVE-2018-1270 in the 4.3.x branch of the Spring Framework.

Affected versions: < 4.3.16

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects org.springframework:spring-core Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.15 and older unsupported versions, provide client-side support for multipart requests. When Spring MVC or Spring WebFlux server application (server A) receives input from a remote client, and then uses that input to make a multipart request to another server (server B), it can be exposed to an attack, where an extra multipart is inserted in the content of the request from server A, causing server B to use the wrong value for a part it expects. This could to lead privilege escalation, for example, if the part content represents a username or user roles.

Affected versions: < 4.3.15

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects org.springframework:spring-core Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.15 and older unsupported versions, allow applications to configure Spring MVC to serve static resources (e.g. CSS, JS, images). When static resources are served from a file system on Windows (as opposed to the classpath, or the ServletContext), a malicious user can send a request using a specially crafted URL that can lead a directory traversal attack.

Affected versions: < 4.3.15

Sourced from The GitHub Security Advisory Database.

High severity vulnerability that affects org.springframework:spring-core Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.15 and older unsupported versions, allow applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through the spring-messaging module. A malicious user (or attacker) can craft a message to the broker that can lead to a remote code execution attack.

Affected versions: < 4.3.16

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects org.springframework:spring-core Spring Framework, versions 5.0.x prior to 5.0.6, versions 4.3.x prior to 4.3.17, and older unsupported versions allows applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through the spring-messaging module. A malicious user (or attacker) can craft a message to the broker that can lead to a regular expression, denial of service attack.

Affected versions: < 4.3.17

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects org.springframework:spring-core An issue was discovered in Pivotal Spring Framework before 3.2.18, 4.2.x before 4.2.9, and 4.3.x before 4.3.5. Paths provided to the ResourceServlet were not properly sanitized and as a result exposed to directory traversal attacks.

Affected versions: < 3.2.18

Sourced from The GitHub Security Advisory Database.

Denial of Service in Spring Framework 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 versions: < 4.3.2

Sourced from The GitHub Security Advisory Database.

Denial of Service in Spring Framework 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 versions: < 4.3.20

Release notes

Sourced from spring-core's releases.

3.2.9 Release

⭐ New Features

• Overriding bean definition message does not take parent definition into account [SPR-9671] #14305
• CollectionToCollectionConverter.convert() improvement for untyped collections [SPR-11479] #16104
• Treat empty log config refresh interval as infinite interval in Log4jWebConfigurer [SPR-11507] #16132
• Improve exception message for failed property access in SpEL [SPR-11535] #16160
• ResizableByteArrayOutputStream and ByteArrayOutputStream capacities [SPR-11594] #16218
• MarshallingView should avoid temporary byte array when copying to response [SPR-11646] #16269
• Fix/optimize handling of @Bean method override regression with return type narrowing on JDK 8 [SPR-11718] #16340
• Metadata reading should never use ASM for java.* and javax.* types (in particular on JDK 8) [SPR-11719] #16341
• AbstractAdvisingBeanPostProcessor.isEligible(…) does not consider proxy interfaces [SPR-11725] #16347
• StandardServletMultipartResolver should support lazy resolution along the lines of CommonsMultipartResolver [SPR-11730] #16352
• AbstractMarshaller should avoid SAXSource workaround when processExternalEntities=true [SPR-11737] #16359
• Improve prefix detection in StringUtils.cleanPath [SPR-11793] #16414
• ConfigurationClassParser.invokeAwareMethods(…) does not consider EnvironmentAware [SPR-11744] #16366
• Basic Java 8 bytecode compatibility for Spring 3.2.x through ASM 5.0.2 [SPR-11656] #16279

🪲 Bug Fixes

• Java config FactoryBean proxy causes class loader leak [SPR-9274] #13912
• Unsafe fallback pointcut construction in AspectJExpressionPointcut [SPR-9335] #13973
• Servlet 3 multipart parameter binding does not work on Weblogic12c (12.1.2.0) [SPR-11074] #15700
• double evaluation of method arguments in SpEL [SPR-11445] #16071
• XmlValidationModeDetector: length of a string is always greater than index of any of its characters [SPR-11477] #16102
• SpringBeanELResolver - setValue throws PropertyNotWritableException [SPR-11502] #16127
• Unable to retrieve FlashMap when target parameters are encoded [SPR-11504] #16129
• Default KeyGenerator doesn't work for methods with arguments of array types [SPR-11505] #16130
• Spring MVC Test can fail to obtain async result due to timing issue [SPR-11516] #16141
• ConstructorResolver will generate NPE in case of no factory method found when there are explicit args [SPR-11517] #16142
• Memory leak when using annotation based auto-wiring in child context [SPR-11520] #16145
• Providing unique names to prototype inner beans causes excessive memory and CPU use [SPR-11545] #16170
• BufferedImageHttpMessageConverter fails if JAI is installed [SPR-11581] #16205
• Log Forging in DispatcherServlet via requestURI [SPR-11591] #16215
• AbstractApplicationEventMulticaster can leak classes [SPR-11606] #16229
• Referencing static field of class that extends Map in expression language causes class cast exception [SPR-11609] #16232
• Servlet mocks are not reinjected into test instance between TestNG test methods [SPR-11626] #16249
• ResourceHttpRequestHandler not closing Resource's input stream [SPR-11644] #16267
• UrlResource.exists() does not properly detect JBoss vfszip resources [SPR-11676] #16299
• ConcurrentReferenceHashMap doesn't limit upper concurrency level [SPR-11720] #16342
• SpringProperties: the ClassLoader might be null, if class is loaded by the bootstrap class loader [SPR-11721] #16343
• If-Modified-Since header is parsed as HTTP-date; but IE 10 sends length [SPR-11727] #16349
• JRubyScriptUtils fails against JRuby 1.7.12 with NullPointerException in findClassNode [SPR-11747] #16369
• IdToEntityConverter throws Access Denied exception within Spring MVC application on WebSphere 8.x [SPR-11758] #16380
• Protect against security exploits via system identifier in DTD declaration [SPR-11768] #16390
• JDBC findColumn gives wrong result in case of duplicate column labels [SPR-11786] #16408
• SPR-10829: Spring JMS problem with Oracle AQ still exists if underlying DataSource is decorated [SPR-11791] #16412
• getTestExecutionListeners() doesn't detect NoClassDefFoundError within BeanInstantiationException [SPR-11804] #16424
• StringUtils.parseLocaleString: locale variant cannot contain country code [SPR-11806] #16426

... (truncated)

Commits

• ca50a47 Release version 4.3.21.RELEASE
• 9600e01 Revised alias definition example in reference documentation
• e9f7c35 ResolvableType-based matching consistently respects generic factory method re...
• cf8479c Upgrade to Tomcat 8.5.35, Netty 4.1.31, Gson 2.8.5, Jackson 2.8.11.3
• 1c1b942 DefaultResponseErrorHandler detects non-standard error code as well
• 85b5c5a Polishing
• ed9afa3 FastByteArrayOutputStream.read byte-to-int conversion
• 22f4b1c SerializedBeanFactoryReference falls back to dummy with specific id
• abacc6d BEST_MATCHING_HANDLER_ATTRIBUTE for spring-webmvc
• 8d668ac Up-to-date version and link in ASM/CGLIB/Objenesis package javadoc
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)