Versions
10.0.1.0
5.0.0.1
5.0.8.10
2018.4.1.1
2018.2.3
5.0.3.0
2018.4.1.3
2018.1.0
2018.2.1
5.0.6.2
2018.1
2018.4.1.4
5.0.2.0
2018.4.1.7
5.0.8.7
10.0.1.1
2018.3.6
5.0.7.0
2018.3.3
2018.4.12
5.0.0.0-5.0.8.3
2018.3.2
5.0.8.6
5.0.8.2
2018.3.1
5.0.6.5
2018.2.4
5.0.8.5
5.0.8.1
5.0.1.0
2018.2.5
2018.4.1.12
2018.2.8
5.0.6.4
5.0
2018.2.2
10.0.1.4
5.0.5.0
2018.2.10
5.0.7.1
2018.3.7
10.0.0.0
2018.4.1.0
2018.4.1.10
5.0.6.1
5.0.8.0
5.0.7.2
2018.2.11
2018.4.1.2
2018.4.1
5.0.8.7iFix3
5.0.8.8
2018.4.1.6
2018.4.1.13
2018.4.1.11
5.0.8.3
2018.2.7
5.0.6.6
V10.0.5.3, V10.0.6.0
2018.4.1.5
5.0.8.11
2018.2.9
5.0.4.0
2018.1.0.0
5.0.8.4
5.0.0.0
5.0.6.3
5.0.6.0
2018.3.4
2018.2.6
Recent CVEs
CVE-2023-47722
IBM API Connect V10.0.5.3 and V10.0.6.0 stores user credentials in browser cache which can be read by a local user. IBM X-Force ID: 271912.
CVE-2021-38997
IBM API Connect V10.0.0.0 through V10.0.5.0, V10.0.1.0 through V10.0.1.7, and V2018.4.1.0 through 2018.4.1.19 is vulnerable to HTTP header injection, caused by improper validation of input by the HOST headers. This could allow an attacker to conduct various attacks against the vulnerable system, including cross-site scripting, cache poisoning or session hijacking. IBM X-Force ID: 213212.
CVE-2021-20440
IBM API Connect 10.0.0.0, and 2018.4.1.0 through 2018.4.1.13 does not restrict member registration to the intended recepient. An attacker who is a valid user in the user registry used by API Manager can use a stolen invitation link and register themselves as a member of an API provider organization. IBM X-Force ID: 196536.
CVE-2020-4903
IBM API Connect V10 and V2018 could allow an attacker who has intercepted a registration invitation link to impersonate the registered user or obtain sensitive information. IBM X-Force ID: 191105.
CVE-2020-4695
IBM API Connect V10 is impacted by insecure communications during database replication. As the data replication happens over insecure communication channels, an attacker can view unencrypted data leading to a loss of confidentiality.
CVE-2020-4828
IBM API Connect 10.0.0.0 through 10.0.1.0 and 2018.4.1.0 through 2018.4.1.13 is vulnerable to web cache poisoning, caused by improper input validation by modifying HTTP request headers. IBM X-Force ID: 189842.
CVE-2020-4827
IBM API Connect 10.0.0.0 through 10.0.1.0 and 2018.4.1.0 through 2018.4.1.13 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts. IBM X-Force ID: 189841.
CVE-2020-4826
IBM API Connect 10.0.0.0 through 10.0.1.0 and 2018.4.1.0 through 2018.4.1.13 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts. IBM X-Force ID: 189840.
CVE-2020-4825
IBM API Connect 10.0.0.0 through 10.0.1.0 and 2018.4.1.0 through 2018.4.1.13 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 189839.
CVE-2020-4640
Certain IBM API Connect 10.0.0.0 through 10.0.1.0 and 2018.4.1.0 through 2018.4.1.13 configurations can result in sensitive information in the URL fragment identifiers. This information can be cached in the intermediate nodes like proxy servers, cdn, logging platforms, etc. An attacker can make use of this information to perform attacks by impersonating a user. IBM X-Force ID: 185510.