dbcve.org
Business Process ManagerApplication · Ibm

CVE-2017-1628

MEDIUM · 6.5 CVSS v3.0 Published 2017-11-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Business Process Manager 8.6.0.0 allows authenticated users to stop and resume the Event Manager by calling a REST API with incorrect authorization checks.

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 · moderate confidence

IBM Business Process Manager 8.6.0.0 contains an improper authorization vulnerability in its REST API. Authenticated users without proper administrative privileges can stop and resume the Event Manager by calling REST endpoints, as authorization checks are incorrectly implemented or missing for these sensitive operations.

MitigationApply the IBM security patch for CVE-2017-1628. Until patched, restrict network access to the REST API endpoints and ensure only users with appropriate administrative roles have access to BPM management interfaces.

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
Business Process ManagerApplication
Affected:= 8.6.0.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checks

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

  1. Confirm IBM BPM version 8.6.0.0 is installed
    Check the installed product version via the IBM BPM installation directory, version file, or WebSphere Administrative Console under 'Product Information'. Look for version 8.6.0.0 specifically.
    Affected if The installed version is exactly 8.6.0.0 (no patches applied)
  2. Verify REST API endpoints are accessible
    Confirm the IBM BPM REST API is enabled and network-accessible. Check WebSphere Application Server configuration for REST API servlet mappings and ensure the endpoints are not blocked at the network or container level.
    Affected if REST API endpoints are exposed and reachable from the network where untrusted users operate
  3. Review REST API authorization configuration
    Inspect the REST API security configuration in the IBM BPM or WebSphere admin console. Look for the authorization settings that govern which roles can access the /rest/bpm/ops/EventManager endpoints.
    Affected if Authorization checks for Event Manager REST endpoints are missing, disabled, or incorrectly configured to allow non-admin authenticated users
  4. Identify users with REST API access
    List all users and groups granted access to the BPM REST API via WebSphere security roles. Check whether non-administrative users have been assigned permissions to invoke management operations.
    Affected if Non-administrative users or groups have been granted REST API access that includes Event Manager operations
  5. Test Event Manager REST endpoint access with limited user
    Using a test account without administrative privileges, attempt to call the REST endpoints for stopping or resuming the Event Manager (such as POST to /rest/bpm/ops/EventManager/stop or /resume). Observe whether the operation succeeds without proper authorization.
    Affected if The REST call succeeds and the Event Manager can be stopped or resumed by a non-administrative authenticated user

A user is affected if IBM BPM version 8.6.0.0 is running with REST API accessible, and non-administrative authenticated users can successfully stop or resume the Event Manager via REST endpoints due to missing or inadequate authorization checks.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the IBM security patch for CVE-2017-1628. Until patched, restrict network access to the REST API endpoints and ensure only users with appropriate administrative roles have access to BPM management interfaces.

Fix this in Business Process Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-1628 — 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-2017-1628 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