Cloud Pak for Automation vulnerabilitiesRanked by how likely they are to be used.
Cloud Pak for Automation is made by IBM. We track 7 published vulnerabilities in it, across 9 versions. None of them is on the list of flaws known to be exploited today. If you run Cloud Pak for Automation, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Cloud Pak for Automation vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Cloud Pak for Automation's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Cloud Pak for Automation flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 1.5%CVE-2020-4325Medium
The IBM Process Federation Server 18.0.0.1, 18.0.0.2, 19.0.0.1, 19.0.0.2, and 19.0.0.3 Global Teams REST API does not properly shutdown the thread pools that it creates to retrieve Global Teams information from the...
- 1.4%CVE-2021-20482High
IBM Cloud Pak for Automation 20.0.2 and 20.0.3 IF002 are vulnerable to an XML External Entity Injection (XXE) attack when processing XML data.
- 1.3%CVE-2021-20359Medium
IBM Cloud Pak for Automation 20.0.3, 20.0.2-IF002 - Business Automation Application Designer Component stores potentially sensitive information in log files that could be obtained by an unauthorized user.
- 0.9%CVE-2021-29775Medium
IBM Business Automation Workflow 19.0.03 and 20.0 and IBM Cloud Pak for Automation 20.0.3-IF002 and 21.0.1 are vulnerable to cross-site scripting.
- 0.8%CVE-2021-20358Medium
IBM Cloud Pak for Automation 20.0.3, 20.0.2-IF002 stores potentially sensitive information in clear text in API connection log files.
- 0.8%CVE-2021-29872Medium
IBM Cloud Pak for Automation 21.0.1 and 21.0.2 - Business Automation Studio Component is vulnerable to HTTP header injection, caused by improper validation of input by the HOST headers.
- 0.5%CVE-2021-38966Medium
IBM Cloud Pak for Automation 21.0.2 is vulnerable to cross-site scripting.
Running Cloud Pak for Automation? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
The IBM Process Federation Server 18.0.0.1, 18.0.0.2, 19.0.0.1, 19.0.0.2, and 19.0.0.3 Global Teams REST API does not properly shutdown the thread pools that it creates to retrieve Global Teams information from the federated systems. As a consequence, the Java Virtual Machine can't recover the memory used by those thread pools, which leads to an OutOfMemory exception when the Process Federation Server Global Teams REST API is used extensively. IBM X-Force ID: 177596.
- Matched to
- Cloud Pak for Automation on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 7 published vulnerabilities listed under the name Cloud Pak for Automation, across 9 versions.
None of Cloud Pak for Automation's vulnerabilities is on the list of flaws known to be exploited today.
Create a EdgeProtect account and track Cloud Pak for Automation. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.