Spring Cloud Config Server May Not Use Vault Token Sent By Clients

Summary

Spring Cloud Config Server may not use Vault token sent by clients using a X-CONFIG-TOKEN header when making requests to Vault. Your application may be affected by this if the following are true: • You have Spring Vault on the classpath of your Spring Cloud Config Server and • You are using the X-CONFIG-TOKEN header to send a Vault token to the Spring Cloud Config Server for the Config Server to use when making requests to Vault and • You are using the default Spring Vault SessionManager implementation LifecycleAwareSessionManager or a SessionManager implementation that persists the Vault token such as SimpleSessionManager. In this case the SessionManager persists the first token it retrieves and will continue to use that token even if client requests to the Spring Cloud Config Server include a X-CONFIG-TOKEN header with a different value. Affected Spring Products and Versions Spring Cloud Config: • 2.2.1.RELEASE - 4.2.1 Mitigation Users of affected versions should upgrade to the corresponding fixed version. Affected version(s)Fix versionAvailability4.2.x4.2.2OSS4.1.x4.1.6OSS4.0.x4.0.10Commercial3.1.x3.1.10Commercial3.0.x4.1.6OSS2.2.x4.1.6OSS NOTE: Spring Cloud Config 3.0.x and 2.2.x are no longer under open source or commercial support. Users of these versions are encouraged to upgrade to a supported version. No other mitigation steps are necessary.

Timeline

1. Apr 10, 2025, 5:26 PM UTCCVE published
2. Apr 10, 2025, 6:08 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: yes · Technical impact: partial

3. Apr 10, 2025, 6:08 PM UTCRecord last updated

Affected versions

• Spring Spring Cloud Config

  From 4.2.x · fixed in 4.2.2; From 4.1.x · fixed in 4.1.6; From 4.0.x · fixed in 4.0.10; From 3.1.x · fixed in 3.1.10; From 3.0.x · fixed in 4.1.6; From 2.2.x · fixed in 4.1.6

References 1