Elastic X-Pack Security versions 5.0.0 to 5.4.0 contain a privilege escalation bug in the run_as functionality. This bug prevents transitioning into the specified user specified in a run_as request. If a role has been created using a template that contains the _user properties, the behavior of run_as will be incorrect. Additionally if the run_as user specified does not exist, the transition will not happen.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| X-pack | Elastic | 5.0.0 (including) | 5.0.0 (including) |
| X-pack | Elastic | 5.0.1 (including) | 5.0.1 (including) |
| X-pack | Elastic | 5.0.2 (including) | 5.0.2 (including) |
| X-pack | Elastic | 5.1.0 (including) | 5.1.0 (including) |
| X-pack | Elastic | 5.1.1 (including) | 5.1.1 (including) |
| X-pack | Elastic | 5.2.0 (including) | 5.2.0 (including) |
| X-pack | Elastic | 5.2.1 (including) | 5.2.1 (including) |
| X-pack | Elastic | 5.2.2 (including) | 5.2.2 (including) |
| X-pack | Elastic | 5.3.0 (including) | 5.3.0 (including) |
| X-pack | Elastic | 5.3.1 (including) | 5.3.1 (including) |
| X-pack | Elastic | 5.3.2 (including) | 5.3.2 (including) |
| X-pack | Elastic | 5.3.3 (including) | 5.3.3 (including) |
| X-pack | Elastic | 5.4.0 (including) | 5.4.0 (including) |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: