{"uuid": "ce0e8e5f-3011-4c2f-821a-5de76df07a96", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22232", "type": "seen", "source": "https://t.me/cvedetector/22676", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-22232 - Spring Cloud Config Server Vault Token Token Persistence Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-22232 \nPublished : April 10, 2025, 6:15 p.m. | 1\u00a0hour, 7\u00a0minutes ago \nDescription : Spring Cloud Config Server may not use Vault token sent by clients using a X-CONFIG-TOKEN\u00a0header 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\u00a0header 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\u00a0implementation LifecycleAwareSessionManager\u00a0or a SessionManager\u00a0implementation that persists the Vault token such as SimpleSessionManager.  \n  \nIn this case the SessionManager\u00a0persists 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\u00a0header 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. \nSeverity: 5.3 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"10 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-10T22:02:58.000000Z"}