Issues
Upgrade Spring Security
Fixed
Description
Acceptance / Success Criteria
None
Linked issue cannot finish until this issue finishes.
Details
Assignee
Benjamin ReedBenjamin ReedReporter
Benjamin ReedBenjamin ReedLabels
Sprint
NoneFix versions
Priority
Major
Details
Details
Assignee
Benjamin Reed
Benjamin ReedReporter
Benjamin Reed
Benjamin ReedLabels
Sprint
None
Fix versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created March 14, 2023 at 2:17 PM
Updated March 6, 2024 at 9:15 PM
Resolved May 12, 2023 at 2:06 PM
Activity
Show:
chiuen (Qun)June 22, 2023 at 8:46 PM
Infosec evaluated at the following risk:
CVSS Score: 7.0 x medium likelihood .8 = 5.6 medium
Dino YanceyMarch 27, 2023 at 5:02 PM
2022.1.13
noted that there are open CVEs for Spring Security, which AFAIK have not been addressed at all, even by moving to the latest micro version of what we’re currently using (3.2.x).
We need to look into upgrading as far as we can. It appears that we should be able to at least move to Spring Security 4.2.x without much trouble. It has only a few direct vulnerabilities that can hopefully be mitigated with backports.
Maven Repository: org.springframework.security » spring-security-core » 4.2.20.RELEASE (mvnrepository.com)