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 applicationsUpgrade Chainguard
rancher-agent-2.10
to version 2.10.0-r1 or higher.
Note: Versions mentioned in the description apply only to the upstream rancher-agent-2.10
package and not the rancher-agent-2.10
package as distributed by Chainguard
.
See How to fix?
for Chainguard
relevant fixed versions and status.
golang-jwt is a Go implementation of JSON Web Tokens. Unclear documentation of the error behavior in ParseWithClaims
can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by ParseWithClaims
return both error codes. If users only check for the jwt.ErrTokenExpired
using error.Is
, they will ignore the embedded jwt.ErrTokenSignatureInvalid
and thus potentially accept invalid tokens. A fix has been back-ported with the error handling logic from the v5
branch to the v4
branch. In this logic, the ParseWithClaims
function will immediately return in "dangerous" situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release. We are aware that this changes the behaviour of an established function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors ("dangerous" ones first), so that you are not running in the case detailed above.