ManageIQ is an open-source management platform. In versions prior to jansa-4, kasparov-2, and lasker-1, there is a flaw in the MiqExpression module of ManageIQ where a low privilege user could enter a crafted Ruby string which would be evaluated. Successful exploitation will allow an attacker to execute arbitrary code with root privileges on the host system. There are patches for this issue in releases named jansa-4, kasparov-2, and lasker-1. If possible, restrict users, via RBAC, to only the part of the application that they need access to. While MiqExpression is widely used throughout the product, restricting users can limit the surface of the attack.
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Manageiq | Manageiq | jansa-1 (including) | jansa-1 (including) |
Manageiq | Manageiq | jansa-1-alpha1 (including) | jansa-1-alpha1 (including) |
Manageiq | Manageiq | jansa-1-beta1 (including) | jansa-1-beta1 (including) |
Manageiq | Manageiq | jansa-1-rc1 (including) | jansa-1-rc1 (including) |
Manageiq | Manageiq | jansa-1-rc2 (including) | jansa-1-rc2 (including) |
Manageiq | Manageiq | jansa-2 (including) | jansa-2 (including) |
Manageiq | Manageiq | jansa-3 (including) | jansa-3 (including) |
Manageiq | Manageiq | kasparov-1 (including) | kasparov-1 (including) |
Manageiq | Manageiq | kasparov-1-alpha1 (including) | kasparov-1-alpha1 (including) |
Manageiq | Manageiq | kasparov-1-beta1 (including) | kasparov-1-beta1 (including) |
Manageiq | Manageiq | kasparov-1-beta1.1 (including) | kasparov-1-beta1.1 (including) |
Manageiq | Manageiq | lasker-1-beta1 (including) | lasker-1-beta1 (including) |
When a product allows a user’s input to contain code syntax, it might be possible for an attacker to craft the code in such a way that it will alter the intended control flow of the product. Such an alteration could lead to arbitrary code execution. Injection problems encompass a wide variety of issues – all mitigated in very different ways. For this reason, the most effective way to discuss these weaknesses is to note the distinct features which classify them as injection weaknesses. The most important issue to note is that all injection problems share one thing in common – i.e., they allow for the injection of control plane data into the user-controlled data plane. This means that the execution of the process may be altered by sending code in through legitimate data channels, using no other mechanism. While buffer overflows, and many other flaws, involve the use of some further issue to gain execution, injection problems need only for the data to be parsed. The most classic instantiations of this category of weakness are SQL injection and format string vulnerabilities.