While investigating ARTEMIS-2964 it was found that the creation of advisory messages in the OpenWire protocol head of Apache ActiveMQ Artemis 2.15.0 bypassed policy based access control for the entire session. Production of advisory messages was not subject to access control in error.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Activemq_artemis | Apache | 2.15.0 (including) | 2.15.0 (including) |
| Red Hat AMQ | RedHat | * | |
| Red Hat AMQ 7.8.1 | RedHat | * | |
| Activemq | Ubuntu | bionic | * |
| Activemq | Ubuntu | groovy | * |
| Activemq | Ubuntu | hirsute | * |
| Activemq | Ubuntu | impish | * |
| Activemq | Ubuntu | kinetic | * |
| Activemq | Ubuntu | trusty | * |
| Activemq | Ubuntu | upstream | * |
| Activemq | Ubuntu | xenial | * |
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: