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 github.com/rancher/rancher/pkg/api/norman/customization/clusterregistrationtokens to version 2.11.16-alpha2, 2.12.12-alpha2, 2.13.8-alpha2, 2.14.4-alpha2 or higher.
Affected versions of this package are vulnerable to Information Exposure in pkg/api/norman/customization/clusterregistrationtokens/import.go is vulnerable to an unauthenticated cluster-existence oracle through the /v3/import/{token}_{clusterId}.yaml import endpoint. An attacker can enumerate valid cluster IDs and infer whether a cluster has private registry secrets configured by sending import requests with guessed cluster IDs and observing the different responses. When the handler looks up the cluster before checking the token, a nonexistent cluster returns HTTP 200, while a valid cluster that reaches the private-registry code path can trigger a HTTP 502 Bad Gateway via a nil pointer dereference. This lets an unauthenticated remote attacker fingerprint cluster presence and registry configuration, exposing infrastructure details useful for follow-on attacks.