Vulmon
Recent Vulnerabilities
Product List
Research Posts
Trends
Blog
About
Contact
Vulmon Alerts
By Relevance
By Risk Score
By Publish Date
ibm robotic process automation 21.0.0 vulnerabilities and exploits
(subscribe to this query)
NA
CVE-2022-22334
IBM Robotic Process Automation 21.0.0, 21.0.1, and 21.0.2 could allow a user to access information from a tenant of which they should not have access. IBM X-Force ID: 219391.
Ibm Robotic Process Automation 21.0.0
Ibm Robotic Process Automation
668
VMScore
CVE-2022-22413
IBM Robotic Process Automation 21.0.0, 21.0.1, and 21.0.2 is vulnerable to SQL injection. A remote attacker could send specially crafted SQL statements, which could allow the malicious user to view, add, modify or delete information in the back-end database. IBM X-Force ID: 22302...
Ibm Robotic Process Automation 21.0.1
Ibm Robotic Process Automation 21.0.2
Ibm Robotic Process Automation 21.0.0
356
VMScore
CVE-2022-30607
IBM Robotic Process Automation 20.10.0, 20.12.5, 21.0.0, 21.0.1, and 21.0.2 contains a vulnerability that could allow a user to obtain sensitive information due to information properly masked in the control center UI. IBM X-Force ID: 227294.
Ibm Robotic Process Automation 20.10.0
Ibm Robotic Process Automation 20.12.5
Ibm Robotic Process Automation 21.0.0
Ibm Robotic Process Automation 21.0.1
Ibm Robotic Process Automation 21.0.2
NA
CVE-2022-35280
IBM Robotic Process Automation 21.0.0, 21.0.1, and 21.0.2 does not require that users should have strong passwords by default, which makes it easier for malicious users to compromise user accounts. IBM X-Force ID: 230634.
Ibm Robotic Process Automation For Cloud Pak 21.0.0
Ibm Robotic Process Automation For Cloud Pak 21.0.1
Ibm Robotic Process Automation For Cloud Pak 21.0.2
NA
CVE-2023-38734
IBM Robotic Process Automation 21.0.0 up to and including 21.0.7.1 and 23.0.0 up to and including 23.0.1 is vulnerable to incorrect privilege assignment when importing users from an LDAP directory. IBM X-Force ID: 262481.
Ibm Robotic Process Automation
Ibm Robotic Process Automation 23.0.0
Ibm Robotic Process Automation 23.0.1
NA
CVE-2022-46773
IBM Robotic Process Automation 21.0.0 - 21.0.7 and 23.0.0 is vulnerable to client-side validation bypass for credential pools. Invalid credential pools may be created as a result. IBM X-Force ID: 242951.
Ibm Robotic Process Automation As A Service
Ibm Robotic Process Automation For Cloud Pak 23.0.0
Ibm Robotic Process Automation For Cloud Pak
Ibm Robotic Process Automation 23.0.0
Ibm Robotic Process Automation
188
VMScore
CVE-2022-22434
IBM Robotic Process Automation 21.0.0, 21.0.1, and 21.0.2 could allow a user with physical access to create an API request modified to create additional objects. IBM X-Force ID: 224159.
Ibm Robotic Process Automation 21.0.1
Ibm Robotic Process Automation 21.0.2
Ibm Robotic Process Automation As A Service -
NA
CVE-2022-22490
IBM Robotic Process Automation 21.0.0, 21.0.1, and 21.0.2 could allow a privileged user to obtain sensitive Azure bot credential information. IBM X-Force ID: 226342.
Ibm Robotic Process Automation
Ibm Robotic Process Automation As A Service
Ibm Robotic Process Automation For Cloud Pak
NA
CVE-2022-36774
IBM Robotic Process Automation 21.0.0, 21.0.1, and 21.0.2 is vulnerable to man in the middle attacks through manipulation of the client proxy configuration. IBM X-Force ID: 233575.
Ibm Robotic Process Automation
Ibm Robotic Process Automation As A Service
Ibm Robotic Process Automation For Cloud Pak
NA
CVE-2023-35901
IBM Robotic Process Automation 21.0.0 up to and including 21.0.7.6 and 23.0.0 up to and including 23.0.6 is vulnerable to client side validation bypass which could allow invalid changes or values in some fields. IBM X-Force ID: 259380.
Ibm Robotic Process Automation
Ibm Robotic Process Automation As A Service
Ibm Robotic Process Automation For Cloud Pak
VMScore
CVSSv2
CVSSv3
VMScore
Recommendations:
path traversal
CVE-2024-33545
CVE-2024-35725
CVE-2024-32704
overflow
file upload
CVE-2024-0230
CVE-2024-32705
CVE-2024-23692
Vulnerability Notification Service
You don’t have to wait for vulnerability scanning results
Get Started
1
2
3
NEXT »