spring-security-core is vulnerable to Observable Timing Discrepancy
59
Medium Risk
spring-security-core compares some secret values with String.equals() instead of a constant-time method. Response time then leaks how many leading characters matched. An attacker who can send many guesses and measure latency may recover Digest responses, token keys, or Password4j secrets character by character. The patch compares those values in constant time.
You are affected if you are using a version that falls within the vulnerable range and you use Digest authentication, KeyBasedPersistenceTokenService, or Password4j password encoders.
spring-security-core is vulnerable to Observable Timing Discrepancy in versions 5.7.0 - 7.0.6 and 7.1.0 - 7.1.0.
Upgrade the org.springframework.security:spring-security-core library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant