VendorsIBMapi_connect5.0.6.1
Vulnerabilities

IBM API Connect 5.0.6.1

Ranked by severity, then by exploit likelihood. Click a CVE ID for its full record.

6CVEs
CVE-2017-1322
IBM API Connect 5.0.6.0 is vulnerable to an XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose highly sensitive information or consume memory resources. IBM X-Force ID: 125918.
Published 2017-06-27 · Modified
8.2EPSS 0.023
CVE-2017-1379
IBM API Connect 5.0.0.0 could allow a remote attacker to obtain sensitive information, caused by improper handling of requests to the Developer Portal. IBM X-Force ID: 127002.
Published 2017-06-15 · Modified
7.5EPSS 0.020
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. 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: 131291.
Published 2017-09-25 · Modified
6.1EPSS 0.009
CVE-2017-1386
IBM API Connect 5.0.0.0 could allow a user to bypass policy restrictions and create non-compliant passwords which could be intercepted and decrypted using man in the middle techniques. IBM X-Force ID: 127160.
Published 2017-07-31 · Modified
5.9EPSS 0.012
CVE-2017-1328
IBM API Connect 5.0.0.0 - 5.0.6.0 could allow a remote attacker to bypass security restrictions of the api, caused by improper handling of security policy. By crafting a suitable request, an attacker could exploit this vulnerability to bypass security and use the vulnerable API. IBM X-Force ID: 126230.
Published 2017-06-27 · Modified
5.3EPSS 0.017
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 to the application plan. IBM X-Force ID: 131545.
Published 2017-09-25 · Modified
4.3EPSS 0.009