dbcve.org
Api ConnectApplication · Ibm

CVE-2018-1712

CRITICAL · 9.9 CVSS v3.0 Published 2018-08-16
Fix available
A fix is available. Upgrade to after 5.0.8.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

IBM API Connect Developer Portal versions 5.0.0.0 through 5.0.8.3 contains a Server Side Request Forgery (SSRF) vulnerability. Attackers can craft malicious input parameters to coerce the server into making unauthorized requests to internal resources within the trusted network, potentially exposing internal services and data.

MitigationUpgrade IBM API Connect Developer Portal to version 5.0.8.4 or later. Additionally, implement input validation, restrict server-side request capabilities, and apply network segmentation to limit internal resource exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Api ConnectApplication
Affected:>= 5.0.0.0, <= 5.0.8.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the IBM API Connect Developer Portal installation
    Locate the installation directory or check the product inventory in your environment to confirm IBM API Connect Developer Portal is deployed
    Affected if IBM API Connect Developer Portal is present in the environment
  2. Determine the installed version of the Developer Portal
    Access the product administrative interface, check the built-in version command, or inspect the version manifest file in the installation directory
    Affected if The version returned is 5.0.0.0, 5.0.1.0, 5.0.2.0, 5.0.3.0, 5.0.4.0, 5.0.5.0, 5.0.6.0, 5.0.7.0, 5.0.8.0, 5.0.8.1, 5.0.8.2, or 5.0.8.3
  3. Compare the installed version against the affected range
    Verify that the installed version falls between 5.0.0.0 and 5.0.8.3 inclusive
    Affected if The installed version is greater than or equal to 5.0.0.0 and less than or equal to 5.0.8.3
  4. Confirm the Developer Portal component is exposed
    Check network accessibility of the Developer Portal web interface or API endpoints
    Affected if The Developer Portal is network-accessible to users or systems that could submit crafted requests

The environment is affected if IBM API Connect Developer Portal version 5.0.0.0 through 5.0.8.3 is installed and network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 5.0.8.3
Interim mitigation

Upgrade IBM API Connect Developer Portal to version 5.0.8.4 or later. Additionally, implement input validation, restrict server-side request capabilities, and apply network segmentation to limit internal resource exposure.

Recommended fix Moderate confidence

IBM API Connect 5.0.8.4 or later (latest 5.0.x release)

  1. Identify the current IBM API Connect version installed by accessing the API Connect management console or running the 'apic version' command
  2. Review IBM's official support lifecycle documentation for API Connect 5.0.x to confirm the latest available fix pack
  3. Upgrade to the latest available 5.0.x fix pack (5.0.8.4 or later) that addresses CVE-2018-1712
  4. After upgrade, verify the Developer Portal SSRF vulnerability is resolved by reviewing IBM's security bulletin for this CVE
  5. Confirm the upgrade by running 'apic version' and checking that the version is >= 5.0.8.4
Caveat Minor: Review IBM's upgrade notes for 5.0.8.4 for any configuration or compatibility considerations specific to the Developer Portal

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Api Connect Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1712 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1712 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data