The default configuration in Elasticsearch before 1.2 enables dynamic scripting, which allows remote attackers to execute arbitrary MVEL expressions and Java code via the source parameter to _search. NOTE: this only violates the vendors intended security policy if the user does not run Elasticsearch in its own independent virtual machine.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Elasticsearch | Elasticsearch | * | 1.1.1 (including) |
Fuse ESB Enterprise 7.1.0 | RedHat | * | |
Fuse Management Console 7.1.0 | RedHat | * | |
Fuse MQ Enterprise 7.1.0 | RedHat | * | |
Red Hat JBoss A-MQ 6.1 | RedHat | * | |
Red Hat JBoss Fuse 6.1 | RedHat | * | |
Red Hat Subscription Asset Manager 1.4 | RedHat | katello-configure-0:1.4.5.1-3.el6sam | * |
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: