Closed stefanscheidt closed 1 year ago
Thanks for reporting the issue, @stefanscheidt. That's right. In fact, we should not be managing the version of this dependency at all. I'm going to remove this from the SC OpenFeign dependencies pom, so that it's pulled directly from Boot.
With version 3.1.5 of spring-cloud-openfeign that ships with Spring Cloud 2021.0.5, the spring-cloud-openfeign-dependencies POM pins the version of spring-security-oauth2-client to 5.7.3.
This causes the following issues:
spring-security.version
with5.7.5
in the application Maven POM itself - an thus will also introduce CVE-2022-31690.As a work around, the second problem can be fixed by not only overwriting the Maven property
spring-security.version
, but also declaring a dependency management for spring-security-oauth2-client using this version in the application Maven POM itself.We don't know what to do in the first situation:
spring-security.version
with5.6.9
in the application Maven POM itself and also declaring a dependency management for spring-security-oauth2-client using this version? Would this be compatible with spring-cloud-openfeign 3.1.5, which says it wants to use spring-security-oauth2-client 5.7.3?spring-security.version
with5.6.9
in the application Maven POM itself and declaring a dependency management for spring-security-oauth2-client using5.7.5
? Would this be OK or cause problems in the 5.6.9 Spring Security stack?