Total
78 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2019-4155 | 1 Ibm | 1 Api Connect | 2024-02-04 | 7.5 HIGH | 9.8 CRITICAL |
| IBM API Connect's Developer Portal 2018.1 and 2018.4.1.3 is impacted by a privilege escalation vulnerability when integrated with an OpenID Connect (OIDC) user registry. IBM X-Force ID: 158544. | |||||
| CVE-2018-2013 | 1 Ibm | 1 Api Connect | 2024-02-04 | 5.0 MEDIUM | 5.3 MEDIUM |
| IBM API Connect 2018.1 through 2018.4.1.5 could disclose sensitive information to an unauthorized user that could aid in further attacks against the system. IBM X-Force ID: 155193. | |||||
| CVE-2018-2009 | 1 Ibm | 1 Api Connect | 2024-02-04 | 4.0 MEDIUM | 6.5 MEDIUM |
| IBM API Connect v2018.1 and 2018.4.1 is affected by an information disclosure vulnerability in the consumer API. Any registered user can obtain a list of all other users in all other orgs, including email id/names, etc. IBM X-Force ID: 155148. | |||||
| CVE-2019-4051 | 1 Ibm | 1 Api Connect | 2024-02-04 | 5.0 MEDIUM | 5.3 MEDIUM |
| Some URIs in IBM API Connect 2018.1 and 2018.4.1.3 disclose system specification information like the machine id, system uuid, filesystem paths, network interface names along with their mac addresses. An attacker can use this information in targeted attacks. IBM X-Force ID: 156542. | |||||
| CVE-2019-4202 | 1 Ibm | 1 Api Connect | 2024-02-04 | 10.0 HIGH | 10.0 CRITICAL |
| IBM API Connect 5.0.0.0 and 5.0.8.6 Developer Portal is vulnerable to command injection. An attacker with a specially crafted request can run arbitrary code on the server and gain complete access to the system. IBM X-Force ID: 159123. | |||||
| CVE-2018-1874 | 1 Ibm | 1 Api Connect | 2024-02-04 | 2.1 LOW | 4.6 MEDIUM |
| IBM API Connect 5.0.0.0 through 5.0.8.5 could display highly sensitive information to an attacker with physical access to the system. IBM X-Force ID: 151636. | |||||
| CVE-2018-1976 | 1 Ibm | 1 Api Connect | 2024-02-04 | 4.0 MEDIUM | 4.9 MEDIUM |
| IBM API Connect 5.0.0.0 through 5.0.8.4 is impacted by sensitive information disclosure via a REST API that could allow a user with administrative privileges to obtain highly sensitive information. IBM X-Force ID: 154031. | |||||
| CVE-2018-1932 | 1 Ibm | 1 Api Connect | 2024-02-04 | 4.0 MEDIUM | 4.9 MEDIUM |
| 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 management server that could allow an authenticated user to obtain highly sensitive information. IBM X-Force ID: 153175. | |||||
| CVE-2018-1638 | 1 Ibm | 1 Api Connect | 2024-02-04 | 6.8 MEDIUM | 8.1 HIGH |
| IBM API Connect 5.0.0.0-5.0.8.3 Developer Portal does not enforce Two Factor Authentication (TFA) while resetting a user password but enforces it for all other login scenarios. IBM X-Force ID: 144483. | |||||
| CVE-2018-1859 | 1 Ibm | 1 Api Connect | 2024-02-04 | 6.5 MEDIUM | 4.7 MEDIUM |
| IBM API Connect 5.0.0.0 through 5.0.8.4 could allow a user authenticated as an administrator with limited rights to escalate their privileges. IBM X-Force ID: 151258. | |||||
| CVE-2018-1784 | 1 Ibm | 1 Api Connect | 2024-02-04 | 7.5 HIGH | 9.8 CRITICAL |
| 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. IBM X-Force ID: 148807. | |||||
| CVE-2018-1779 | 1 Ibm | 1 Api Connect | 2024-02-04 | 5.0 MEDIUM | 7.5 HIGH |
| IBM API Connect 2018.1 through 2018.3.7 could allow an unauthenticated attacker to cause a denial of service due to not setting limits on JSON payload size. IBM X-Force ID: 148802. | |||||
| CVE-2018-1973 | 1 Ibm | 1 Api Connect | 2024-02-04 | 9.0 HIGH | 7.2 HIGH |
| IBM API Connect 5.0.0.0 through 5.0.8.4 allows a user with limited 'API Administrator level access to give themselves full 'Administrator' level access through the members functionality. IBM X-Force ID: 153914. | |||||
| CVE-2018-1599 | 1 Ibm | 1 Api Connect | 2024-02-04 | 3.5 LOW | 5.4 MEDIUM |
| 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. By persuading a victim to visit a malicious Web site, a remote attacker could exploit this vulnerability to hijack the victim's click actions and possibly launch further attacks against the victim. IBM X-Force ID: 143744. | |||||
| CVE-2018-1789 | 1 Ibm | 1 Api Connect | 2024-02-04 | 6.5 MEDIUM | 9.9 CRITICAL |
| IBM API Connect v2018.1.0 through v2018.3.4 could allow an attacker to send a specially crafted request to conduct a server side request forgery attack. IBM X-Force ID: 148939. | |||||
| CVE-2018-1774 | 1 Ibm | 1 Api Connect | 2024-02-04 | 6.8 MEDIUM | 7.8 HIGH |
| 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 analytics that could contain malicious commands that would be executed once opened by an administrator. IBM X-Force ID: 148692. | |||||
| CVE-2018-1778 | 1 Ibm | 1 Api Connect | 2024-02-04 | 9.3 HIGH | 8.1 HIGH |
| 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 if the AccessToken Model is exposed over a REST API, it is then possible for anyone to create an AccessToken for any User provided they know the userId and can hence get access to the other user’s data / access to their privileges (if the user happens to be an Admin for example). IBM X-Force ID: 148801. | |||||
| CVE-2019-4008 | 1 Ibm | 1 Api Connect | 2024-02-04 | 5.0 MEDIUM | 9.8 CRITICAL |
| API Connect V2018.1 through 2018.4.1.1 is impacted by access token leak. Authorization tokens in some URLs can result in the tokens being written to log files. IBM X-Force ID: 155626. | |||||
| CVE-2018-1712 | 1 Ibm | 1 Api Connect | 2024-02-04 | 7.5 HIGH | 9.9 CRITICAL |
| IBM API Connect's Developer Portal 5.0.0.0 through 5.0.8.3 is vulnerable to Server Side Request Forgery. An attacker, using specially crafted input parameters can trick the server into making potentially malicious calls within the trusted network. IBM X-Force ID: 146370. | |||||
| CVE-2016-1000232 | 3 Ibm, Redhat, Salesforce | 3 Api Connect, Openshift Container Platform, Tough-cookie | 2024-02-04 | 5.0 MEDIUM | 5.3 MEDIUM |
| NodeJS Tough-Cookie version 2.2.2 contains a Regular Expression Parsing vulnerability in HTTP request Cookie Header parsing that can result in Denial of Service. This attack appear to be exploitable via Custom HTTP header passed by client. This vulnerability appears to have been fixed in 2.3.0. | |||||