AI analysis
Katello’s RegistryProxiesController has an authorization-bypass flaw (CWE-203) in the registry_authorize filter. Unauthorized requests are detected and an error is started, but a missing return lets execution continue into later business-logic and database checks. Differential responses then leak internal state, so a low-privileged attacker can enumerate valid users, organizations, and products across the instance. Confidentiality impact is low (CVSS 3.1 4.3); integrity and availability are not affected. The issue is fixed in Katello 4.21.2 and 5.0.1, is not on the CISA KEV list, and no public proof-of-concept is known.
What to do: Upgrade Katello (rubygem-katello) to 4.21.2 or 5.0.1, the releases that fix this issue. Until upgraded, restrict network access to the registry proxy to trusted users and review logs for unexpected registry authorization requests that return differing error responses.
Affected
| Red Hat rubygem-katello (Katello) | Fixed in 4.21.2 and 5.0.1; earlier releases in those lines are affected |
Estimated exposure
—No basis for an estimate.
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description
A flaw was found in rubygem-katello. The RegistryProxiesController in Katello contains an authorization bypass vulnerability due to an execution fall-through in the registry_authorize filter. While the application identifies unauthorized requests and triggers an error response via the unauthorized method, it fails to halt the execution of the current code path (missing return statement). This failure in the control flow allows the application to proceed into subsequent business logic and database validation filters. Consequently, the application reveals its internal state through differential responses, allowing an unprivileged attacker to enumerate valid Users, Organizations, and Products across the entire instance.