IBM Robotic Process Automation With Automation Anywhere
19 CVEs affecting IBM Robotic Process Automation With Automation Anywhere. Latest disclosed: 2021-05-07. Critical: 1, High: 2.
| CVE | Severity | Score | Published | Summary |
|---|---|---|---|---|
CVE-2019-4336 | Critical | 9.8 | 2019-07-01 | IBM Robotic Process Automation with Automation Anywhere 11 uses an inadequate account lockout setting that could allow a remote attacker to brute force account… |
CVE-2018-1547 | High | 8.0 | 2018-06-07 | IBM Robotic Process Automation with Automation Anywhere 10.0 could allow a remote attacker to execute arbitrary code on the system, caused by improper output e… |
CVE-2019-4298 | High | 7.1 | 2019-07-01 | IBM Robotic Process Automation with Automation Anywhere 11 uses a high privileged PostgreSQL account for database access which could allow a local user to perf… |
CVE-2020-4901 | Medium | 6.5 | 2021-05-07 | IBM Robotic Process Automation with Automation Anywhere 11.0 could allow an attacker on the network to obtain sensitive information or cause a denial of servic… |
CVE-2018-1877 | Medium | 6.2 | 2018-11-02 | IBM Robotic Process Automation with Automation Anywhere 11 could store highly sensitive information in the form of unencrypted passwords that would be availabl… |
CVE-2018-1876 | Medium | 6.2 | 2018-11-02 | IBM Robotic Process Automation with Automation Anywhere 11 could under certain cases, display the password in a Control Room log file after installation. IBM X… |
CVE-2018-1795 | Medium | 6.1 | 2018-10-05 | IBM Robotic Process Automation with Automation Anywhere Enterprise 10 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary… |
CVE-2019-4299 | Medium | 5.5 | 2019-07-01 | IBM Robotic Process Automation with Automation Anywhere 11 could allow a local user to obtain highly sensitive information from log files when debugging is ena… |
CVE-2018-1552 | Medium | 5.5 | 2018-11-02 | IBM Robotic Process Automation with Automation Anywhere 10.0 and 11.0 allows a remote attacker to execute arbitrary code on the system, caused by a missing res… |
CVE-2019-4297 | Medium | 5.4 | 2019-07-01 | IBM Robotic Process Automation with Automation Anywhere 11 could allow a remote authenticated attacker to conduct an LDAP injection. By using a specially craft… |
CVE-2018-1908 | Medium | 5.4 | 2019-03-14 | IBM Robotic Process Automation with Automation Anywhere 11 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript… |
CVE-2018-1812 | Medium | 5.4 | 2018-10-05 | IBM Robotic Process Automation with Automation Anywhere Enterprise 10 is vulnerable to persistent cross-site scripting, caused by missing escaping of a databas… |
CVE-2017-1751 | Medium | 5.4 | 2017-12-20 | IBM Robotic Process Automation with Automation Anywhere 10.0.0 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaSc… |
CVE-2019-4337 | Medium | 5.3 | 2019-07-01 | IBM Robotic Process Automation with Automation Anywhere 11 could allow an attacker to obtain sensitive information due to missing authentication in Ignite node… |
CVE-2018-1878 | Medium | 5.3 | 2018-11-02 | IBM Robotic Process Automation with Automation Anywhere 11 could disclose sensitive information in a web request that could aid in future attacks against the s… |
CVE-2019-4295 | Medium | 4.9 | 2019-07-01 | IBM Robotic Process Automation with Automation Anywhere 11 could allow an attacker with specialized access to obtain highly sensitive from the credential vault… |
CVE-2018-2006 | Medium | 4.9 | 2019-02-21 | IBM Robotic Process Automation with Automation Anywhere 11 could allow a remote attacker to traverse directories on the system. An attacker could send a specia… |
CVE-2018-1514 | Medium | 4.3 | 2018-06-07 | IBM Robotic Process Automation with Automation Anywhere 10.0 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and… |
CVE-2019-4296 | Low | 3.3 | 2019-07-01 | IBM Robotic Process Automation with Automation Anywhere 11 information disclosure could allow a local user to obtain e-mail contents from the client debug log… |