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 Reversible One-Way Hash vulnerabilities in an interactive lesson.
Start learningThere is no fixed version for RHEL:7
rh-dotnet60-dotnet-sdk-6.0-source-built-artifacts
.
Note: Versions mentioned in the description apply only to the upstream rh-dotnet60-dotnet-sdk-6.0-source-built-artifacts
package and not the rh-dotnet60-dotnet-sdk-6.0-source-built-artifacts
package as distributed by RHEL
.
See How to fix?
for RHEL:7
relevant fixed versions and status.
crypto-js is a JavaScript library of crypto standards. Prior to version 4.2.0, crypto-js PBKDF2 is 1,000 times weaker than originally specified in 1993, and at least 1,300,000 times weaker than current industry standard. This is because it both defaults to SHA1, a cryptographic hash algorithm considered insecure since at least 2005, and defaults to one single iteration, a 'strength' or 'difficulty' value specified at 1,000 when specified in 1993. PBKDF2 relies on iteration count as a countermeasure to preimage and collision attacks. If used to protect passwords, the impact is high. If used to generate signatures, the impact is high. Version 4.2.0 contains a patch for this issue. As a workaround, configure crypto-js to use SHA256 with at least 250,000 iterations.