GHSA-7cj3-x93g-gj76 Signature forgery in Spring Boot's Loader

• Maven org.springframework.boot:spring-boot-loader: >= 2.7.0, < 2.7.22 → fixed in 2.7.22 • Maven org.springframework.boot:spring-boot-loader-classic: >= 2.7.0, < 2.7.22 → fixed in 2.7.22 • Maven org.springframework.boot:spring-boot-loader: >= 3.0.0, < 3.0.17 → fixed in 3.0.17 • Maven org.springframework.boot:spring-boot-loader-classic: >= 3.0.0, < 3.0.17 → fixed in 3.0.17 • Maven org.springframework.boot:spring-boot-loader: >= 3.1.0, < 3.1.13 → fixed in 3.1.13 • Maven org.springframework.boot:spring-boot-loader-classic: >= 3.1.0, < 3.1.13 → fixed in 3.1.13 • Maven org.springframework.boot:spring-boot-loader: >= 3.2.0, < 3.2.9 → fixed in 3.2.9 • Maven org.springframework.boot:spring-boot-loader-classic: >= 3.2.0, < 3.2.9 → fixed in 3.2.9 • Maven org.springframework.boot:spring-boot-loader: >= 3.3.0, < 3.3.3 → fixed in 3.3.3 • Maven org.springframework.boot:spring-boot-loader-classic: >= 3.3.0, < 3.3.3 → fixed in 3.3.3

Applications that use spring-boot-loader or spring-boot-loader-classic and contain custom code that performs signature verification of nested jar files may be vulnerable to signature forgery where content that appears to have been signed by one signer has, in fact, been signed by another.