IBM UrbanCode Deploy could allow a user to execute code using a specially crafted file upload that would replace code on the server. This code could be executed on the UCD agent machines that host customers production applications.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Urbancode_deploy | Ibm | 6.0 (including) | 6.0 (including) |
Urbancode_deploy | Ibm | 6.0.1 (including) | 6.0.1 (including) |
Urbancode_deploy | Ibm | 6.0.1.1 (including) | 6.0.1.1 (including) |
Urbancode_deploy | Ibm | 6.0.1.2 (including) | 6.0.1.2 (including) |
Urbancode_deploy | Ibm | 6.0.1.3 (including) | 6.0.1.3 (including) |
Urbancode_deploy | Ibm | 6.0.1.4 (including) | 6.0.1.4 (including) |
Urbancode_deploy | Ibm | 6.0.1.5 (including) | 6.0.1.5 (including) |
Urbancode_deploy | Ibm | 6.0.1.6 (including) | 6.0.1.6 (including) |
Urbancode_deploy | Ibm | 6.0.1.7 (including) | 6.0.1.7 (including) |
Urbancode_deploy | Ibm | 6.0.1.8 (including) | 6.0.1.8 (including) |
Urbancode_deploy | Ibm | 6.0.1.9 (including) | 6.0.1.9 (including) |
Urbancode_deploy | Ibm | 6.0.1.10 (including) | 6.0.1.10 (including) |
Urbancode_deploy | Ibm | 6.0.1.11 (including) | 6.0.1.11 (including) |
Urbancode_deploy | Ibm | 6.0.1.12 (including) | 6.0.1.12 (including) |
Urbancode_deploy | Ibm | 6.0.1.13 (including) | 6.0.1.13 (including) |
Urbancode_deploy | Ibm | 6.0.1.14 (including) | 6.0.1.14 (including) |
Urbancode_deploy | Ibm | 6.1 (including) | 6.1 (including) |
Urbancode_deploy | Ibm | 6.1.0.1 (including) | 6.1.0.1 (including) |
Urbancode_deploy | Ibm | 6.1.0.2 (including) | 6.1.0.2 (including) |
Urbancode_deploy | Ibm | 6.1.0.3 (including) | 6.1.0.3 (including) |
Urbancode_deploy | Ibm | 6.1.0.4 (including) | 6.1.0.4 (including) |
Urbancode_deploy | Ibm | 6.1.1 (including) | 6.1.1 (including) |
Urbancode_deploy | Ibm | 6.1.1.1 (including) | 6.1.1.1 (including) |
Urbancode_deploy | Ibm | 6.1.1.2 (including) | 6.1.1.2 (including) |
Urbancode_deploy | Ibm | 6.1.1.3 (including) | 6.1.1.3 (including) |
Urbancode_deploy | Ibm | 6.1.1.4 (including) | 6.1.1.4 (including) |
Urbancode_deploy | Ibm | 6.1.1.5 (including) | 6.1.1.5 (including) |
Urbancode_deploy | Ibm | 6.1.1.6 (including) | 6.1.1.6 (including) |
Urbancode_deploy | Ibm | 6.1.1.7 (including) | 6.1.1.7 (including) |
Urbancode_deploy | Ibm | 6.1.1.8 (including) | 6.1.1.8 (including) |
Urbancode_deploy | Ibm | 6.1.2 (including) | 6.1.2 (including) |
Urbancode_deploy | Ibm | 6.1.3 (including) | 6.1.3 (including) |
Urbancode_deploy | Ibm | 6.1.3.1 (including) | 6.1.3.1 (including) |
Urbancode_deploy | Ibm | 6.1.3.2 (including) | 6.1.3.2 (including) |
Urbancode_deploy | Ibm | 6.1.3.3 (including) | 6.1.3.3 (including) |
Urbancode_deploy | Ibm | 6.2.0.0 (including) | 6.2.0.0 (including) |
Urbancode_deploy | Ibm | 6.2.0.1 (including) | 6.2.0.1 (including) |
Urbancode_deploy | Ibm | 6.2.0.2 (including) | 6.2.0.2 (including) |
Urbancode_deploy | Ibm | 6.2.1 (including) | 6.2.1 (including) |
Urbancode_deploy | Ibm | 6.2.1.1 (including) | 6.2.1.1 (including) |
Urbancode_deploy | Ibm | 6.2.2 (including) | 6.2.2 (including) |
Urbancode_deploy | Ibm | 6.2.2.1 (including) | 6.2.2.1 (including) |
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: