← Search results
CVE-LINKED INVENTORY10 SECURITY RECORDS
Publisher not identified
Spring Security
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2024-22257 | 18 Mar 2024 | 6.2.0 to 6.2.2, 6.1.0 to 6.1.7, 6.0.0 to 6.0.9, 5.8.0 to 5.8.10, 5.7.0 to 5.7.11 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2023-34042 | 5 Feb 2024 | Spring Security 6.1.x prior to 6.1.4, Spring Security 6.0.x prior to 6.0.7, Spring Security 5.8.x prior to 5.8.7, Spring Security 5.7.x prior to 5.7.11 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-34034 | 19 Jul 2023 | Spring Security 6.1.0 ≤ 6.1.1; Spring Security 6.0.0 ≤ 6.0.4; Spring Security 5.8.0 ≤ 5.8.4; Spring Security 5.7.0 ≤ 5.7.9 ; Spring Security 5.6.0 ≤ 5.6.11 | Before applying the update, back up your existing installation, including all applications, configuration files, databases and database settings, and so on. The References section of this erratum contains a download link (you must log in to download the update). | Update reference ↗ |
| CVE-2023-34035 | 18 Jul 2023 | Spring Security 5.8.0 to 5.8.4, Spring Security 6.0.0 to 6.0.4, Spring Security 6.1.0 to 6.1.1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-20862 | 19 Apr 2023 | Spring Security, versions 5.7.x prior to 5.7.8, versions 5.8.x prior to 5.8.3, and versions 6.0.x prior to 6.0.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-31690 | 31 Oct 2022 | Spring Security (5.7 to 5.7.4 and 5.6 to 5.6.8 as well as older, unsupported versions) | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2022-22976 | 19 May 2022 | Spring Security versions 5.5.x prior to 5.5.7, 5.6.x prior to 5.6.4, and earlier unsupported versions | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2022-22978 | 19 May 2022 | Spring security versions 5.4.x prior to 5.4.11+,5.5.x prior to 5.5.7+,5.6.x prior to 5.6.4+ and all earlier unsupported versions | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2021-22119 | 29 Jun 2021 | Spring Security versions 5.5.x prior to 5.5.1, 5.4.x prior to 5.4.7, 5.3.x prior to 5.3.10 and 5.2.x prior to 5.2.11 | Before applying the update, back up your existing installation, including all applications, configuration files, databases and database settings, and so on. Installation instructions are available from the Fuse 7.11.0 product documentation page: https://access.redhat.com/documentation/en-us/red_hat_fuse/7.11/ | Update reference ↗ |
| CVE-2021-22112 | 23 Feb 2021 | 5.4.x prior to 5.4.4, 5.3.x prior to 5.3.8.RELEASE, 5.2.x prior to 5.2.9.RELEASE | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.