fix(deps): update spring.version [security] (major) #81
+1
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=80&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.2.18.RELEASE->5.2.21.RELEASE3.2.18.RELEASE->5.2.20.RELEASE3.2.18.RELEASE->6.0.03.2.18.RELEASE->4.3.17.RELEASE3.2.18.RELEASE->5.2.22.RELEASEGitHub Vulnerability Alerts
CVE-2022-22968
In Spring Framework versions 5.3.0 - 5.3.18, 5.2.0 - 5.2.20, and older unsupported versions, the patterns for disallowedFields on a DataBinder are case sensitive which means a field is not effectively protected unless it is listed with both upper and lower case for the first character of the field, including upper and lower case for the first character of all nested fields within the property path. Versions 5.3.19 and 5.2.21 contain a patch for this issue.
CVE-2022-22965
Spring Framework prior to versions 5.2.20 and 5.3.18 contains a remote code execution vulnerability known as
Spring4Shell.Impact
A Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data binding. The specific exploit requires the application to run on Tomcat as a WAR deployment. If the application is deployed as a Spring Boot executable jar, i.e. the default, it is not vulnerable to the exploit. However, the nature of the vulnerability is more general, and there may be other ways to exploit it.
These are the prerequisites for the exploit:
spring-webmvcorspring-webfluxdependencyPatches
Workarounds
For those who are unable to upgrade, leaked reports recommend setting
disallowedFieldsonWebDataBinderthrough an@ControllerAdvice. This works generally, but as a centrally applied workaround fix, may leave some loopholes, in particular if a controller setsdisallowedFieldslocally through its own@InitBindermethod, which overrides the global setting.To apply the workaround in a more fail-safe way, applications could extend
RequestMappingHandlerAdapterto update theWebDataBinderat the end after all other initialization. In order to do that, a Spring Boot application can declare aWebMvcRegistrationsbean (Spring MVC) or aWebFluxRegistrationsbean (Spring WebFlux).CVE-2016-9878
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.
CVE-2016-1000027
Pivotal Spring Framework before 6.0.0 suffers from a potential remote code execution (RCE) issue if used for Java deserialization of untrusted data. Depending on how the library is implemented within a product, this issue may or not occur, and authentication may be required.
Maintainers recommend investigating alternative components or a potential mitigating control. Version 4.2.6 and 3.2.17 contain enhanced documentation advising users to take precautions against unsafe Java deserialization, version 5.3.0 deprecate the impacted classes and version 6.0.0 removed it entirely.
CVE-2024-22259
Applications that use UriComponentsBuilder in Spring Framework to parse an externally provided URL (e.g. through a query parameter) AND perform validation checks on the host of the parsed URL may be vulnerable to a open redirect https://cwe.mitre.org/data/definitions/601.html attack or to a SSRF attack if the URL is used after passing validation checks.
This is the same as CVE-2024-22243 https://spring.io/security/cve-2024-22243, but with different input.
CVE-2024-38809
Description
Applications that parse ETags from
If-MatchorIf-None-Matchrequest headers are vulnerable to DoS attack.Affected Spring Products and Versions
org.springframework:spring-web in versions
6.1.0 through 6.1.11
6.0.0 through 6.0.22
5.3.0 through 5.3.37
Older, unsupported versions are also affected
Mitigation
Users of affected versions should upgrade to the corresponding fixed version.
6.1.x -> 6.1.12
6.0.x -> 6.0.23
5.3.x -> 5.3.38
No other mitigation steps are necessary.
Users of older, unsupported versions could enforce a size limit on
If-MatchandIf-None-Matchheaders, e.g. through a Filter.CVE-2024-22262
Applications that use UriComponentsBuilder to parse an externally provided URL (e.g. through a query parameter) AND perform validation checks on the host of the parsed URL may be vulnerable to a open redirect https://cwe.mitre.org/data/definitions/601.html attack or to a SSRF attack if the URL is used after passing validation checks.
This is the same as CVE-2024-22259 https://spring.io/security/cve-2024-22259 and CVE-2024-22243 https://spring.io/security/cve-2024-22243 , but with different input.
CVE-2016-5007
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 (as well as other unsupported versions) 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.
CVE-2018-1257
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.
CVE-2018-1272
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.
CVE-2018-1271
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.
CVE-2022-22970
In spring framework versions prior to 5.3.20+ , 5.2.22+ and old unsupported versions, applications that handle file uploads are vulnerable to DoS attack if they rely on data binding to set a MultipartFile or javax.servlet.Part to a field in a model object.
Release Notes
spring-projects/spring-framework (org.springframework:spring-context)
v5.2.21.RELEASECompare Source
⭐ New Features
🐞 Bug Fixes
v5.2.20.RELEASECompare Source
⭐ New Features
v5.2.19.RELEASECompare Source
⭐ New Features
🐞 Bug Fixes
📔 Documentation
🔨 Dependency Upgrades
v5.2.18.RELEASECompare Source
⭐ New Features
🐞 Bug Fixes
🔨 Dependency Upgrades
v5.2.17.RELEASECompare Source
⭐ New Features
🐞 Bug Fixes
📔 Documentation
prepareTestInstance()is invoked when using theSpringMethodRule#27312🔨 Dependency Upgrades
v5.2.16.RELEASECompare Source
⭐ New Features
🪲 Bug Fixes
📔 Documentation
@Transactionalexamples regarding method visibility #27005@Transactionaldocs regarding method visibility #27004@TransactionalEventListenerafter completion methods #26979🔨 Dependency Upgrades
v5.2.15.RELEASECompare Source
⭐ New Features
🪲 Bug Fixes
@ModelAttribute(binding=false)is not honored with WebFlux #26888📔 Documentation
🔨 Dependency Upgrades
v5.2.14.RELEASECompare Source
⭐ New Features
🪲 Bug Fixes
@DirtiesContextnot applied when class-level@EnabledIfevaluates to false #26697@CrossOriginmaxAge value should override global value #26620@Component#26584🔨 Dependency Upgrades
v5.2.13.RELEASECompare Source
⭐ New Features
🪲 Bug Fixes
@Nullablevalue but throws NullPointerException #26277📔 Documentation
🔨 Dependency Upgrades
v5.2.12.RELEASECompare Source
⭐ New Features
🪲 Bug Fixes
📔 Documentation
@Transactionaldoes not propagate to new threads #26102🔨 Dependency Upgrades
v5.2.11.RELEASECompare Source
⭐ New Features
🪲 Bug Fixes
📔 Documentation
v5.2.10.RELEASECompare Source
⭐ New Features
@RequestPartmultipart controllers with Servlet MockPart #25829🪲 Bug Fixes
@ActiveProfileswith same profiles but different order results in duplicate ApplicationContext #25973📔 Documentation
🔨 Dependency Upgrades
v5.2.9.RELEASECompare Source
⭐ New Features
@FunctionalInterface#25571🪲 Bug Fixes
@RestControllerAdviceannotation attributes #25520@Beanmethod with name mismatch causes bean to be created twice (in case of ASM processing) #25263📔 Documentation
@RestControllerand Webflux #25596@Beanjavadoc and ConfigurationClassEnhancer #25590@RequestMapping#params #25482🔨 Dependency Upgrades
❤️ Contributors
We'd like to thank all the contributors who worked on this release!
v5.2.8.RELEASECompare Source
⭐ New Features
🪲 Bug fixes
📔 Documentation
🔨 Dependency upgrades
❤️ Contributors
We’d like to thank all the contributors who worked on our current release!
v5.2.7.RELEASECompare Source
⭐ New Features
@Aspect#25186🪲 Bug Fixes
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.