CVE-2018-1674
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 · uneditedIBM Business Process Manager 8.5 through 8.6 and 18.0.0.0 through 18.0.0.1 are vulnerable to SQL injection. A remote attacker could send specially-crafted SQL statements, which could allow the attacker to view, add, modify or delete information in the back-end database. IBM X-Force ID: 145109.
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 confidenceSQL injection vulnerability in IBM Business Process Manager versions 8.5 through 8.6 and 18.0.0.0 through 18.0.0.1 allows remote attackers to execute arbitrary SQL statements via specially-crafted input, enabling view, add, modify, or delete operations on the back-end database.
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= 18.0.0.0= 18.0.0.1>= 8.5.0.0, <= 8.5.0.2= 8.5.5.0= 8.5.6.0= 8.5.7.0= 8.6.0.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed IBM Business Process Manager or Business Automation Workflow versionLocate the installation directory and check the version file or use the versionInfo command from the bin directory (versionInfo.sh or versionInfo.bat). Look for the product version in the output.Affected if The installed version matches 8.5.0.0 through 8.5.0.2, 8.5.5.0, 8.5.6.0, 8.5.7.0, 8.6.0.0, 18.0.0.0, or 18.0.0.1.
-
Confirm the exact product name and buildIn the version output, verify the product name is either IBM Business Process Manager or IBM Business Automation Workflow and note the full build version number.Affected if The product is IBM Business Process Manager or IBM Business Automation Workflow at the affected versions listed.
-
Check if Process Designer or Process Center is accessibleDetermine whether the web interface (Process Designer, Process Center, or Process Portal) is accessible over the network. Attempt to access the URLs typically used for these components.Affected if The web-based components are exposed to network users who could submit specially-crafted SQL input.
-
Review exposed REST APIs and data access endpointsIdentify any custom or built-in REST endpoints that accept user input and query the back-end database. Check WebSphere integration settings for exposed data services.Affected if REST APIs or data endpoints that accept SQL-like input from users are accessible without strict input validation.
You are affected if IBM Business Process Manager or IBM Business Automation Workflow is installed at versions 8.5.0.0 through 8.5.0.2, 8.5.5.0, 8.5.6.0, 8.5.7.0, 8.6.0.0, 18.0.0.0, or 18.0.0.1 and the web interface or REST APIs are network-accessible.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply the IBM patch or upgrade to a fixed version of IBM Business Process Manager as specified in IBM's security bulletin.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1674 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-1674 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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