It was found that 3scales APIdocs does not validate the access token, in the case of invalid token, it uses session auth instead. This conceivably bypasses access controls and permits unauthorized information disclosure.
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 |
---|---|---|---|
3scale | Redhat | * | 2.11.0 (excluding) |
3scale API Management 2.11 on RHEL 7 | RedHat | 3scale-amp2/3scale-rhel7-operator:1.14.0-4 | * |
3scale API Management 2.11 on RHEL 7 | RedHat | 3scale-amp2/3scale-rhel7-operator-metadata:2.11.0-16 | * |
3scale API Management 2.11 on RHEL 7 | RedHat | 3scale-amp2/apicast-rhel7-operator:1.14.0-3 | * |
3scale API Management 2.11 on RHEL 7 | RedHat | 3scale-amp2/apicast-rhel7-operator-metadata:2.11.0-9 | * |
3scale API Management 2.11 on RHEL 7 | RedHat | 3scale-amp2/memcached-rhel7:1.4.16-38 | * |
3scale API Management 2.11 on RHEL 7 | RedHat | 3scale-amp2/system-rhel7:1.15.0-8 | * |
3scale API Management 2.11 on RHEL 8 | RedHat | 3scale-amp2/apicast-gateway-rhel8:1.20.0-6 | * |
3scale API Management 2.11 on RHEL 8 | RedHat | 3scale-amp2/backend-rhel8:1.14.0-3 | * |
3scale API Management 2.11 on RHEL 8 | RedHat | 3scale-amp2/toolbox-rhel8:1.6.0-7 | * |
3scale API Management 2.11 on RHEL 8 | RedHat | 3scale-amp2/zync-rhel8:1.14.0-3 | * |
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.