8000 Upgrade spring-security-crypto to 6.4.4 by matthew1001 · Pull Request #8448 · hyperledger/besu · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Upgrade spring-security-crypto to 6.4.4 #8448

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

matthew1001
Copy link
Contributor

PR description

Upgrades the version of spring-security-crypto to address a HIGH severity CVE:

┌─────────────────────────────────────────────────────┬────────────────┬──────────┬────────┬───────────────────┬──────────────────────────────────────────────────────┬──────────────────────────────────────────────────┐
│                       Library                       │ Vulnerability  │ Severity │ Status │ Installed Version │                    Fixed Version                     │                      Title                       │
├─────────────────────────────────────────────────────┼────────────────┼──────────┼────────┼───────────────────┼──────────────────────────────────────────────────────┼──────────────────────────────────────────────────┤
│ org.springframework.security:spring-security-crypto │ CVE-2025-22228 │ HIGH     │ fixed  │ 6.4.3             │ 6.3.8, 6.4.4, 6.2.10, 6.1.14, 6.0.16, 5.8.18, 5.7.16 │ Spring Security Does Not Enforce Password Length │
│ (spring-security-crypto-6.4.3.jar)                  │                │          │        │                   │                                                      │ https://avd.aquasec.com/nvd/cve-2025-22228       │
│                                                     │                │          │        │                   │                                                      │                                                  │
│                                                     │                │          │        │                   │                                                      │                                                  │
│                                                     │                │          │        │                   │                                                      │                                                  │
│                                                     │                │          │        │                   │                                                      │                                                  │
│                                                     │                │          │        │                   │                                                      │                                                  │
│                                                     │                │          │        │                   │                          
8000
                            │                                                  │
└─────────────────────────────────────────────────────┴────────────────┴──────────┴────────┴───────────────────┴──────────────────────────────────────────────────────┴──────────────────────────────────────────────────┘

@matthew1001
Copy link
Contributor Author

Hmm - seeing

One artifact failed verification: spring-security-crypto-6.4.4.pom (org.springframework.security:spring-security-crypto:6.4.4) from repository MavenRepo

@matthew1001
Copy link
Contributor Author

I'm not sure what the issue is with the verification failure. I had recreated it locally, now I can't, so I've re-run the failed GHAs. Maybe an outage of some sort? distTar was also failing for a different reason (:checkLicense failure) but for other components.

Signed-off-by: Matthew Whitehead <matthew1001@gmail.com>
@matthew1001 matthew1001 force-pushed the spring-security-crypto-cve-2025-22228 branch from a2e3d5f to 8ade7f4 Compare March 21, 2025 15:02
@matthew1001
Copy link
Contributor Author

So it looks like gradlew --write-verification-metadata sha256 spotlessCheck isn't adding pom entries to the verification-metadata.xml. Manually adding

 <artifact name="spring-security-crypto-6.4.4.pom">
     <sha256 value="79bb9a97ea5d3c45fdc4731ea6ac69b2c2ffff4c13c2341f58503a4b6a23b1ce" origin="Generated by Gradle"/>
</artifact>

has fixed the compilation check.

@macfarla
Copy link
Contributor

prob worth a changelog entry since it's a CVE

Signed-off-by: Matthew Whitehead <matthew1001@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0