A Broken Access Control vulnerability in Active Job versions >= 4.2.0 allows an attacker to craft user input which can cause Active Job to deserialize it using GlobalId and give them access to information that they should not have. This vulnerability has been fixed in versions 4.2.11, 5.0.7.1, 5.1.6.1, and 5.2.1.1.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Rails | Rubyonrails | 4.2.0 (including) | 4.2.11 (excluding) |
| Rails | Rubyonrails | 5.0.0 (including) | 5.0.7.1 (excluding) |
| Rails | Rubyonrails | 5.1.0 (including) | 5.1.6.1 (excluding) |
| Rails | Rubyonrails | 5.2.0 (including) | 5.2.1.1 (excluding) |
| CloudForms Management Engine 5.9 | RedHat | cfme-0:5.9.9.1-1.el7cf | * |
| CloudForms Management Engine 5.9 | RedHat | cfme-amazon-smartstate-0:5.9.9.1-1.el7cf | * |
| CloudForms Management Engine 5.9 | RedHat | cfme-appliance-0:5.9.9.1-1.el7cf | * |
| CloudForms Management Engine 5.9 | RedHat | cfme-gemset-0:5.9.9.1-1.el7cf | * |
| Rails | Ubuntu | bionic | * |
| Rails | Ubuntu | cosmic | * |
| Rails | Ubuntu | eoan | * |
| Rails | Ubuntu | esm-apps/bionic | * |
| Rails | Ubuntu | esm-apps/focal | * |
| Rails | Ubuntu | esm-apps/jammy | * |
| Rails | Ubuntu | esm-apps/xenial | * |
| Rails | Ubuntu | focal | * |
| Rails | Ubuntu | groovy | * |
| Rails | Ubuntu | hirsute | * |
| Rails | Ubuntu | impish | * |
| Rails | Ubuntu | jammy | * |
| Rails | Ubuntu | kinetic | * |
| Rails | Ubuntu | upstream | * |
| Rails | Ubuntu | xenial | * |
| Ruby-actionpack-3.2 | Ubuntu | trusty | * |
| Ruby-activemodel-3.2 | Ubuntu | trusty | * |
| Ruby-activerecord-3.2 | Ubuntu | trusty | * |
| Ruby-activesupport-3.2 | Ubuntu | trusty | * |
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: