A flaw was found in the Eclipse Che up to version 7.8.x, where it did not properly restrict access to workspace pods. An authenticated user can exploit this flaw to bypass JWT proxy and gain access to the workspace pods of another user. Successful exploitation requires knowledge of the service name and namespace of the target pod.
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Che | Eclipse | * | 7.9.0 (excluding) |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/crw-2-rhel8-operator:2.1-19 | * |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/crw-2-rhel8-operator-metadata:2.1-41 | * |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/devfileregistry-rhel8:2.1-72 | * |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/imagepuller-rhel8:2.1-15 | * |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/jwtproxy-rhel8:2.1-11 | * |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/machineexec-rhel8:2.1-9 | * |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/pluginbroker-artifacts-rhel8:2.1-9 | * |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/pluginbroker-metadata-rhel8:2.1-9 | * |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/plugin-java11-rhel8:2.1-10 | * |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/plugin-kubernetes-rhel8:2.1-7 | * |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/plugin-openshift-rhel8:2.1-7 | * |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/pluginregistry-rhel8:2.1-86 | * |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/server-rhel8:2.1-19 | * |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/stacks-cpp-rhel8:2.1-6 | * |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/stacks-dotnet-rhel8:2.1-8 | * |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/stacks-golang-rhel8:2.1-7 | * |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/stacks-java-rhel8:2.1-7 | * |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/stacks-node-rhel8:2.1-7 | * |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/stacks-php-rhel8:2.1-9 | * |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/stacks-python-rhel8:2.1-5 | * |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/theia-dev-rhel8:2.1-38 | * |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/theia-endpoint-rhel8:2.1-32 | * |
Red Hat CodeReady Workspaces 2.0 | RedHat | codeready-workspaces/theia-rhel8:2.1-30 | * |
Assuming a user with a given identity, authorization is the process of determining whether that user can access a given resource, based on the user’s privileges and any permissions or other access-control specifications that apply to the resource. When access control checks are not applied, users are able to access data or perform actions that they should not be allowed to perform. This can lead to a wide range of problems, including information exposures, denial of service, and arbitrary code execution.