The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsLearn about Insertion of Sensitive Information into Log File vulnerabilities in an interactive lesson.
Start learningUpgrade org.springframework.vault:spring-vault-core
to version 2.3.3, 3.0.2 or higher.
Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File when attempting to revoke a Vault batch token.
Specifically, an application is vulnerable when all of the following are true:
The authentication mechanism creates Batch tokens
Usage of LifecycleAwareSessionManager
in an imperative-only arrangement
LifecycleAwareSessionManager.destroy()
is called by the application or the application shutdown hook
The logging level for LifecycleAwareSessionManager
or org.springframework.vault.authentication
is set at least to WARN
or a more detailed logging level.
The token revocation fails because either of:
An application is not vulnerable if any of the following is true:
The application uses ReactiveSessionManager
in a mixed reactive/imperative or reactive-only arrangement
LifecycleAwareSessionManager.destroy()
is never called by the application or the application shutdown hook
The logging level for LifecycleAwareSessionManager
or org.springframework.vault.authentication
is set to ERROR
or higher, such as OFF
The authentication mechanism creates Service tokens