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 org.apache.camel:camel-keycloak to version 4.18.5, 4.22.2 or higher.
Affected versions of this package are vulnerable to Insufficient Session Expiration via the KeycloakSecurityProcessor in the camel-keycloak component. When token introspection and result caching are enabled, a caller can keep sending an access token that Camel introspected and cached while it was active after its exp time; because the processor checks only the cached result’s active status and the cache lifetime is based on insertion-time TTL, requests remain authorized with the expired token’s existing roles and permissions until the entry expires. Token introspection is not enabled by default, and this flaw grants no permissions beyond those already carried by the token.
Notes
KeycloakSecurityPolicy.useTokenIntrospection=true (false by default); local JWT verification is unaffected. Result caching must also be enabled via introspectionCacheEnabled (true by default).Workarounds
introspectionCacheEnabled=false on KeycloakSecurityPolicy so every request is checked against Keycloak’s introspection endpoint, which reports expired tokens as inactive.