Jenkins Blue Ocean Plugin 1.25.3 and earlier does not perform a permission check in several HTTP endpoints, allowing attackers with Overall/Read permission to connect to an attacker-specified HTTP server.
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 |
---|---|---|---|
Blue_ocean | Jenkins | * | 1.25.3 (including) |
OCP-Tools-4.12-RHEL-8 | RedHat | jenkins-2-plugins-0:4.12.1686649756-1.el8 | * |
OCP-Tools-4.13-RHEL-8 | RedHat | jenkins-2-plugins-0:4.13.1686680473-1.el8 | * |
OpenShift Developer Tools and Services for OCP 4.11 | RedHat | jenkins-2-plugins-0:4.11.1683009941-1.el8 | * |
Red Hat OpenShift Container Platform 4.10 | RedHat | jenkins-2-plugins-0:4.10.1675144701-1.el8 | * |
Red Hat OpenShift Container Platform 4.8 | RedHat | jenkins-2-plugins-0:4.8.1672842762-1.el8 | * |
Red Hat OpenShift Container Platform 4.9 | RedHat | jenkins-2-plugins-0:4.9.1675668922-1.el8 | * |
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.