Distribution is a toolkit to pack, ship, store, and deliver container content. Systems running registry versions 3.0.0-beta.1 through 3.0.0-rc.2 with token authentication enabled may be vulnerable to an issue in which token authentication allows an attacker to inject an untrusted signing key in a JSON web token (JWT). The issue lies in how the JSON web key (JWK) verification is performed. When a JWT contains a JWK header without a certificate chain, the code only checks if the KeyID (kid) matches one of the trusted keys, but doesnt verify that the actual key material matches. A fix for the issue is available at commit 5ea9aa028db65ca5665f6af2c20ecf9dc34e5fcd and expected to be a part of version 3.0.0-rc.3. There is no way to work around this issue without patching if the system requires token authentication.
The system’s authorization functionality does not prevent one user from gaining access to another user’s data or record by modifying the key value identifying the data.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat OpenShift Container Platform 4.17 | RedHat | openshift4/ose-operator-framework-tools-rhel9:v4.17.0-202503052005.p0.ge9262fe.assembly.stream.el9 | * |
| Red Hat OpenShift Container Platform 4.17 | RedHat | openshift4/ose-operator-lifecycle-manager-rhel9:v4.17.0-202503052005.p0.ge9262fe.assembly.stream.el9 | * |
| Red Hat OpenShift Container Platform 4.17 | RedHat | openshift4/ose-operator-registry-rhel9:v4.17.0-202503052005.p0.ge9262fe.assembly.stream.el9 | * |
| Red Hat OpenShift Container Platform 4.18 | RedHat | openshift4/ose-operator-framework-tools-rhel9:v4.18.0-202503041603.p0.g877b6fd.assembly.stream.el9 | * |
| Red Hat OpenShift Container Platform 4.18 | RedHat | openshift4/ose-operator-lifecycle-manager-rhel9:v4.18.0-202503041603.p0.g877b6fd.assembly.stream.el9 | * |
| Red Hat OpenShift Container Platform 4.18 | RedHat | openshift4/ose-operator-registry-rhel9:v4.18.0-202503041603.p0.g877b6fd.assembly.stream.el9 | * |
| Red Hat OpenShift Container Platform 4.18 | RedHat | redhat/redhat-operator-index:v4.18.0-202503041603.p0.g877b6fd.assembly.stream.el9 | * |
Retrieval of a user record occurs in the system based on some key value that is under user control. The key would typically identify a user-related record stored in the system and would be used to lookup that record for presentation to the user. It is likely that an attacker would have to be an authenticated user in the system. However, the authorization process would not properly check the data access operation to ensure that the authenticated user performing the operation has sufficient entitlements to perform the requested data access, hence bypassing any other authorization checks present in the system. For example, attackers can look at places where user specific data is retrieved (e.g. search screens) and determine whether the key for the item being looked up is controllable externally. The key may be a hidden field in the HTML form field, might be passed as a URL parameter or as an unencrypted cookie variable, then in each of these cases it will be possible to tamper with the key value. One manifestation of this weakness is when a system uses sequential or otherwise easily-guessable session IDs that would allow one user to easily switch to another user’s session and read/modify their data.