API Connect vulnerabilitiesRanked by how likely they are to be used.

Product73 versions
The short answer

API Connect is made by IBM. We track 78 published vulnerabilities in it, across 73 versions. None of them is on the list of flaws known to be exploited today. If you run API Connect, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which API Connect vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of API Connect's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which API Connect 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.

50% or more10% to 49%Under 10%
  1. 7.8%

    IBM API Connect 5.0.0.0 through 5.0.8.6 could allow an unauthorized user to obtain sensitive information about the system users using specially crafted HTTP requests.

    CVSS5.3Published25 Jun 2019
  2. 4.2%

    IBM API Connect 5.0.0.0 and 5.0.8.6 Developer Portal is vulnerable to command injection.

    CVSS10.0Published15 Apr 2019
  3. 3.4%

    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...

    CVSS8.1Published20 Dec 2018
  4. 3.2%

    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.

    CVSS4.9Published8 Jan 2019
  5. 2.8%

    IBM API Connect Developer Portal 5.0.0.0 through 5.0.8.2 could allow an unauthenticated attacker to execute system commands using specially crafted HTTP requests.

    CVSS9.8Published4 Apr 2018
  6. 2.8%

    IBM API Connect 2018.1 through 2018.4.1.5 could allow an attacker to obtain sensitive information from a specially crafted HTTP request that could aid an attacker in further attacks against the system.

    CVSS5.3Published25 Jun 2019
  7. 2.6%

    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.

    CVSS9.8Published8 Apr 2019
  8. 2.6%

    IBM API Connect 5.0.0.0 through 5.0.8.6 developer portal could allow a remote attacker to traverse directories on the system.

    CVSS7.5Published20 Aug 2019
  9. 2.5%

    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.

    CVSS7.5Published20 Nov 2018
  10. 2.4%

    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.

    CVSS5.3Published5 Sep 2018
EdgeProtect

Running API Connect? 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.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. 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.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 78 published vulnerabilities listed under the name API Connect, across 73 versions.

None of API Connect's vulnerabilities is on the list of flaws known to be exploited today.

Create a EdgeProtect account and track API Connect. 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.