{ "dataType": "CVE_RECORD", "dataVersion": "5.1", "cveMetadata": { "cveId": "CVE-2025-22232", "assignerOrgId": "dcf2e128-44bd-42ed-91e8-88f912c1401d", "state": "PUBLISHED", "assignerShortName": "vmware", "dateReserved": "2025-01-02T04:29:59.191Z", "datePublished": "2025-04-10T17:26:56.755Z", "dateUpdated": "2025-04-10T18:08:28.560Z" }, "containers": { "cna": { "affected": [ { "defaultStatus": "unaffected", "product": "Spring Cloud Config", "vendor": "Spring", "versions": [ { "lessThan": "4.2.2", "status": "affected", "version": "4.2.x", "versionType": "custom" }, { "lessThan": "4.1.6", "status": "affected", "version": "4.1.x", "versionType": "custom" }, { "lessThan": "4.0.10", "status": "affected", "version": "4.0.x", "versionType": "custom" }, { "lessThan": "3.1.10", "status": "affected", "version": "3.1.x", "versionType": "custom" }, { "lessThan": "4.1.6", "status": "affected", "version": "3.0.x", "versionType": "custom" }, { "lessThan": "4.1.6", "status": "affected", "version": "2.2.x", "versionType": "custom" } ] } ], "datePublic": "2025-04-07T16:40:00.000Z", "descriptions": [ { "lang": "en", "supportingMedia": [ { "base64": false, "type": "text/html", "value": "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:
  1. You have Spring Vault on the classpath of your Spring Cloud Config Server and
  2. 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
  3. 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:
Mitigation
Users of affected versions should upgrade to the corresponding fixed version.

Affected version(s)Fix versionAvailability
4.2.x4.2.2OSS
4.1.x4.1.6OSS
4.0.x4.0.10Commercial
3.1.x3.1.10Commercial
3.0.x4.1.6OSS
2.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.
" } ], "value": "Spring Cloud Config Server may not use Vault token sent by clients using a X-CONFIG-TOKEN header when making requests to Vault.\nYour application may be affected by this if the following are true:\n * You have Spring Vault on the classpath of your Spring Cloud Config Server and\n * 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\n * You are using the default Spring Vault SessionManager implementation LifecycleAwareSessionManager or a SessionManager implementation that persists the Vault token such as SimpleSessionManager.\n\nIn 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.\nAffected Spring Products and Versions\nSpring Cloud Config:\n * 2.2.1.RELEASE - 4.2.1\n\n\nMitigation\nUsers of affected versions should upgrade to the corresponding fixed version.\n\nAffected 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\nNOTE: 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.\n\nNo other mitigation steps are necessary." } ], "metrics": [ { "cvssV3_1": { "attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 5.3, "baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "version": "3.1" }, "format": "CVSS", "scenarios": [ { "lang": "en", "value": "GENERAL" } ] } ], "problemTypes": [ { "descriptions": [ { "cweId": "CWE-287", "description": "CWE-287 Improper Authentication", "lang": "en", "type": "CWE" } ] } ], "providerMetadata": { "orgId": "dcf2e128-44bd-42ed-91e8-88f912c1401d", "shortName": "vmware", "dateUpdated": "2025-04-10T17:26:56.755Z" }, "references": [ { "url": "https://spring.io/security/cve-2025-22232" } ], "source": { "discovery": "UNKNOWN" }, "title": "Spring Cloud Config Server May Not Use Vault Token Sent By Clients", "workarounds": [ { "lang": "en", "supportingMedia": [ { "base64": false, "type": "text/html", "value": "

If you cannot upgrade, then you can either:

  1. Remove Spring Vault from the classpath if it is not needed or
  2. Implement your own SessionManager that does not persist the Vault token and provide a bean using that implementation in a @Configuration class. For example:


public class StatelessSessionManager implements SessionManager {

  private final ClientAuthentication clientAuthentication;

  private final ReentrantLock lock = new ReentrantLock();

  public StatelessSessionManager(ClientAuthentication clientAuthentication) {
    Assert.notNull(clientAuthentication, \"ClientAuthentication must not be null\");
    this.clientAuthentication = clientAuthentication;
  }

  public VaultToken getSessionToken() {
    this.lock.lock();
    try {
      return this.clientAuthentication.login();
    }
    finally {
      this.lock.unlock();
    }
  }

}

@Configuration
public class MySessionManagerConfiguration extends SpringVaultClientConfiguration {

  private final VaultEnvironmentProperties vaultProperties;

  public MySessionManagerConfiguration(VaultEnvironmentProperties vaultProperties, ConfigTokenProvider configTokenProvider, List<springvaultclientauthenticationprovider> authProviders) {
    super(vaultProperties, configTokenProvider, authProviders);
    this.vaultProperties = vaultProperties;
  }

  @Bean
  @Primary
  public SessionManager sessionManager() {
    if (vaultProperties.getAuthentication() == null && !StringUtils.hasText(vaultProperties.getToken())) {
      return new StatelessSessionManager(clientAuthentication());
    }
    return super.sessionManager();
  }
}
</springvaultclientauthenticationprovider>

" } ], "value": "If you cannot upgrade, then you can either:\n\n * Remove Spring Vault from the classpath if it is not needed or\n * Implement your own SessionManager that does not persist the Vault token and provide a bean using that implementation in a @Configuration class. For example:\n\n\npublic class StatelessSessionManager implements SessionManager {\n\n  private final ClientAuthentication clientAuthentication;\n\n  private final ReentrantLock lock = new ReentrantLock();\n\n  public StatelessSessionManager(ClientAuthentication clientAuthentication) {\n    Assert.notNull(clientAuthentication, \"ClientAuthentication must not be null\");\n    this.clientAuthentication = clientAuthentication;\n  }\n\n  public VaultToken getSessionToken() {\n    this.lock.lock();\n    try {\n      return this.clientAuthentication.login();\n    }\n    finally {\n      this.lock.unlock();\n    }\n  }\n\n}\n\n@Configuration\npublic class MySessionManagerConfiguration extends SpringVaultClientConfiguration {\n\n  private final VaultEnvironmentProperties vaultProperties;\n\n  public MySessionManagerConfiguration(VaultEnvironmentProperties vaultProperties, ConfigTokenProvider configTokenProvider, List authProviders) {\n    super(vaultProperties, configTokenProvider, authProviders);\n    this.vaultProperties = vaultProperties;\n  }\n\n  @Bean\n  @Primary\n  public SessionManager sessionManager() {\n    if (vaultProperties.getAuthentication() == null && !StringUtils.hasText(vaultProperties.getToken())) {\n      return new StatelessSessionManager(clientAuthentication());\n    }\n    return super.sessionManager();\n  }\n}\n" } ], "x_generator": { "engine": "Vulnogram 0.2.0" } }, "adp": [ { "metrics": [ { "other": { "type": "ssvc", "content": { "timestamp": "2025-04-10T18:08:12.310467Z", "id": "CVE-2025-22232", "options": [ { "Exploitation": "none" }, { "Automatable": "yes" }, { "Technical Impact": "partial" } ], "role": "CISA Coordinator", "version": "2.0.3" } } } ], "title": "CISA ADP Vulnrichment", "providerMetadata": { "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2025-04-10T18:08:28.560Z" } } ] } }