-
Suggestion
-
Resolution: Unresolved
-
None
-
None
Issue Summary
We would like to have the updated version of spring-core libraries to 5.3.32.
Currently used spring version - 4.0.9.RELEASE - is known to contain a number of security vulnerabilities.
Steps to Reproduce
N/A
Expected Results
N/A
Actual Results
N/A
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available.
[FE-7533] Update spring-core libraries to 5.3.32 or newer
Status | Original: Gathering Interest [ 11772 ] | New: Future Consideration [ 11775 ] |
Description |
Original:
h3. Issue Summary
We would like to have the updated version of spring-core libraries to 5.3.32. h3. Steps to Reproduce N/A h3. Expected Results N/A h3. Actual Results N/A h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
We would like to have the updated version of spring-core libraries to 5.3.32. Currently used spring version - 4.0.9.RELEASE - is known to contain a number of security vulnerabilities. h3. Steps to Reproduce N/A h3. Expected Results N/A h3. Actual Results N/A h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available. |
Summary | Original: Update spring-core libraries to 5.3.32 | New: Update spring-core libraries to 5.3.32 or newer |
Security | Original: Reporter and Atlassian Staff [ 10751 ] |
Upgrading Spring requires an upgrade of Atlassian Platform from version 3 to version 5 (or newer). Platform V3 and V5 are not binary compatible, so an upgrade will introduce breaking changes for the plugin ecosystem. This requires a platform release of Fisheye/Crucible (i.e. version 5.0.0), like it's done for Jira, Confluence and other products.