| CVE-2018-1976 |
IBM API Connect 5.0.0.0 through 5.0.8.4 is impacted by sensitive information disclosure via a REST API that could…
|
4.9
Medium
|
Jan 29, 2019 |
| CVE-2018-1932 |
IBM API Connect 5.0.0.0 through 5.0.8.4 is affected by a vulnerability in the role-based access control in the…
|
4.9
Medium
|
Jan 8, 2019 |
| CVE-2018-1859 |
IBM API Connect 5.0.0.0 through 5.0.8.4 could allow a user authenticated as an administrator with limited rights to…
|
4.3
Medium
|
Jan 4, 2019 |
| CVE-2018-1973 |
IBM API Connect 5.0.0.0 through 5.0.8.4 allows a user with limited 'API Administrator level access to give themselves…
|
7.2
High
|
Dec 20, 2018 |
| CVE-2018-1778 |
IBM LoopBack (IBM API Connect 2018.1, 2018.4.1, 5.0.8.0, and 5.0.8.4) could allow an attacker to bypass authentication…
|
7.7
High
|
Dec 20, 2018 |
| CVE-2018-1784 |
IBM API Connect 5.0.0.0 and 5.0.8.4 is affected by a NoSQL Injection in MongoDB connector for the LoopBack framework
|
7.1
High
|
Dec 20, 2018 |
| CVE-2018-1779 |
IBM API Connect 2018.1 through 2018.3.7 could allow an unauthenticated attacker to cause a denial of service due to…
|
7.5
High
|
Nov 20, 2018 |
| CVE-2018-1774 |
IBM API Connect 5.0.0.0, 5.0.8.4, 2018.1 and 2018.3.6 is vulnerable to CSV injection via the developer portal and…
|
8.9
High
|
Nov 9, 2018 |
| CVE-2018-1789 |
IBM API Connect v2018.1.0 through v2018.3.4 could allow an attacker to send a specially crafted request to conduct a…
|
8.4
High
|
Sep 7, 2018 |
| CVE-2018-1599 |
IBM API Connect 5.0.0.0 through 5.0.8.3 could allow a remote attacker to hijack the clicking action of the victim
|
5.4
Medium
|
Aug 22, 2018 |
| CVE-2018-1712 |
IBM API Connect's Developer Portal 5.0.0.0 through 5.0.8.3 is vulnerable to Server Side Request Forgery
|
8.6
High
|
Aug 16, 2018 |
| CVE-2018-1638 |
IBM API Connect 5.0.0.0-5.0.8.3 Developer Portal does not enforce Two Factor Authentication (TFA) while resetting a user…
|
5.9
Medium
|
Jul 31, 2018 |
| CVE-2018-1548 |
IBM API Connect 2018.1.0.0, 2018.2.1, 2018.2.2, 2018.2.3, and 2018.2.4 contains a vulnerability that could allow an…
|
4.3
Medium
|
Jul 9, 2018 |
| CVE-2018-1546 |
IBM API Connect 5.0.0.0 through 5.0.8.3 could allow a remote attacker to obtain sensitive information, caused by the…
|
5.9
Medium
|
Jul 6, 2018 |
| CVE-2018-1532 |
IBM API Connect 5.0.0.0 through 5.0.8.2 does not properly update the SESSIONID with each request, which could allow a…
|
4.3
Medium
|
May 31, 2018 |
| CVE-2018-1468 |
IBM API Connect 5.0.8.1 and 5.0.8.2 could allow a user to get access to internal environment and sensitive API details…
|
Not rated
|
May 2, 2018 |
| CVE-2018-1389 |
IBM API Connect 5.0.0.0 through 5.0.8.2 is impacted by generated LoopBack APIs for a Model using the BelongsTo/HasMany…
|
Not rated
|
Apr 30, 2018 |
| CVE-2018-1430 |
IBM API Connect 5.0.0.0 through 5.0.8.2 is vulnerable to cross-site scripting
|
Not rated
|
Apr 30, 2018 |
| CVE-2018-1469 |
IBM API Connect Developer Portal 5.0.0.0 through 5.0.8.2 could allow an unauthenticated attacker to execute system…
|
9.8
Critical
|
Apr 4, 2018 |
| CVE-2018-1382 |
IBM API Connect 5.0.0.0 is vulnerable to cross-site scripting
|
Not rated
|
Feb 7, 2018 |
| CVE-2017-1785 |
IBM API Connect 5.0.7 and 5.0.8 could allow an authenticated remote user to modify query parameters to obtain…
|
Not rated
|
Feb 7, 2018 |
| CVE-2017-1555 |
IBM API Connect 5.0.0.0 through 5.0.7.2 could allow an authenticated user to generate an API token when not subscribed…
|
Not rated
|
Sep 25, 2017 |
| CVE-2017-1551 |
IBM API Connect 5.0.0.0 through 5.0.7.2 could allow a remote attacker to hijack the clicking action of the victim
|
Not rated
|
Sep 25, 2017 |
| CVE-2017-1556 |
IBM API Connect 5.0.7.0 through 5.0.7.2 is vulnerable to a regular expression attack that could allow an authenticated…
|
Not rated
|
Sep 13, 2017 |
| CVE-2017-1386 |
IBM API Connect 5.0.0.0 could allow a user to bypass policy restrictions and create non-compliant passwords which…
|
Not rated
|
Jul 31, 2017 |