Risk/Issue summary finding
Client-side Control Bypass (Ranger)
Risk/Issue summary description/detail
The Apache Ranger application relies on client-side controls to restrict user access to certain information and functionality. A user can bypass these controls (by modifying client-side parameters or directly browsing to specific API requests or resources) to view information without the required authorisation.
The attached screenshots show the "admin" user bypassing client-side controls to modify their Role from "User" to "Admin". Whilst submitting this request is unsuccessful and will not permanently change the user role, the GUI allows access to sections that were previously hidden.
Business impact / attack scenario
Low privilege users with restricted access are able to view information that is not intended for their viewing. As an example, the admin user can bypass client side controls to view configuration details for the HIVE_RANGER_E2E hive object.
Do not rely on client-side controls to restrict user access. Ensure that server-side controls are in place to restrict unauthorised access to sensitive information and APIs.
In the rangeradmin ui, on the users page, after clicking on a user. If you edit the html on the site (ie in Chrome) you can remove the 'disabled' tag so that the role of User becomes ungreyed out and you can change the role from User to Admin!