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 Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.
Start learningUpgrade org.bouncycastle:bcpkix-debug-jdk14 to version 1.85 or higher.
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in JcePKCSPBEInputDecryptorProviderBuilder and JceOpenSSLPKCS8DecryptorProviderBuilder, which parse PBES2Parameters from attacker-supplied EncryptedPrivateKeyInfo, PKCS#12, or CMS structures and pass the scrypt N/r and PBKDF2 iteration count straight into key derivation without bounds checking. An attacker can exhaust the JVM heap (roughly 128*N*r bytes of scrypt memory) or pin a worker thread for extended periods with up to 2^31-1 PBKDF2 iterations, by submitting an encrypted private key, PKCS#12 file, or CMS message that declares large KDF cost parameters. The key derivation runs before any integrity or authenticity check, so exploitation only requires the application to attempt password-based decryption or PKCS12PfxPdu MAC verification of the attacker-supplied structure.