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.
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
Link | Tags |
---|---|
https://discuss.elastic.co/t/elastic-stack-5-4-1-and-5-3-3-security-updates/87952 | vendor advisory |
https://www.elastic.co/blog/elasticsearch-5-4-1-and-5-3-3-released | patch vendor advisory |
https://www.elastic.co/community/security | vendor advisory |