IBM Enterprise Build of Quarkus is affected by multiple vulnerabilities
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.
When a Quarkus application has multiple endpoints secured by individual OIDC provider tenants, such as "/oidc-provider1" that is secured by the OIDC Provider 1 and "/oidc-provider2" that is secured by the OIDC Provider 2, and an optional token introspection cache is also enabled, then a valid token issued by the OIDC Provider 1 that can be used to access "/oidc-provider1" can also be used to access "/oidc-provider2" that is secured by another OIDC Provider 2.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| IBM | Enterprise Build of Quarkus | >=3.27.1 <=3.27.5, >=3.33.1 <=3.33.3 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in IBM, strongest first
Embed
A live severity badge for an advisory, README or ticket