dbcve.org
Business Process ManagerApplication · Ibm

CVE-2015-0110

MEDIUM · 6.5 CVSS v3.0 Published 2017-09-15
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 (aka BPM) 7.5.x, 8.0.x, and 8.5.x and WebSphere Lombardi Edition (aka WLE) 7.2.x allow remote authenticated users to bypass intended access restrictions on internal service types via vectors involving the executeServiceByName URL.

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 Business Process Manager 7.5.x-8.5.x and WebSphere Lombardi Edition 7.2.x contain an access control bypass vulnerability where authenticated users can bypass intended restrictions on internal service types via the executeServiceByName URL endpoint, allowing unauthorized access to privileged service operations.

MitigationApply the relevant IBM security patch for this vulnerability. Additionally, review and tighten user role assignments and consider network-level restrictions to limit exposure until patching is complete.

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:= 7.5.0.0= 7.5.0.1= 7.5.1.0= 7.5.1.1= 7.5.1.2= 8.0.0.0= 8.0.1.0= 8.0.1.1= 8.0.1.2= 8.0.1.3= 8.5.0.0= 8.5.0.1
Websphere Application ServerApplication
Affected:= 7.2.0.0= 7.2.0.1= 7.2.0.2= 7.2.0.3= 7.2.0.4= 7.2.0.5

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
High
Availability
None

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

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 installed IBM product
    Determine if IBM Business Process Manager, WebSphere Lombardi Edition, or related WebSphere Application Server components are installed on the system. Look for IBM WebSphere directories or check installed software packages.
    Affected if The product is IBM Business Process Manager 7.5.x-8.5.x, WebSphere Lombardi Edition 7.2.x, or WebSphere Application Server 7.2.x
  2. Check product version
    Use the product's version detection method (such as the versionInfo command in WebSphere, the Installation Manager, or check product-specific configuration files) to obtain the exact installed version number.
    Affected if The installed version matches one of the affected versions: 7.5.0.0-7.5.1.2, 8.0.0.0-8.0.1.3, 8.5.0.0-8.5.0.1 for Business Process Manager; 7.2.0.0-7.2.0.5 for Lombardi Edition or WebSphere Application Server
  3. Verify executeServiceByName endpoint exposure
    Inspect web application configuration or proxy rules for the executeServiceByName URL endpoint. This endpoint should be restricted to authorized internal service calls only.
    Affected if The executeServiceByName endpoint is accessible without additional authorization checks beyond basic authentication
  4. Review authenticated user role assignments
    Check the user role mappings for the affected application. Determine which authenticated users have access to internal service operations.
    Affected if Users with standard (non-admin) authentication can potentially reach privileged service operations through this endpoint
  5. Audit internal service type access controls
    Review the access control configuration for internal service types to confirm whether proper restrictions are enforced on the executeServiceByName functionality.
    Affected if Internal service types lack proper role-based restrictions, allowing authenticated users to invoke privileged operations

Your environment is affected if you have IBM Business Process Manager 7.5.x-8.5.x, WebSphere Lombardi Edition 7.2.x, or WebSphere Application Server 7.2.x installed AND the executeServiceByName endpoint is accessible to authenticated users beyond intended restrictions.

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 relevant IBM security patch for this vulnerability. Additionally, review and tighten user role assignments and consider network-level restrictions to limit exposure until patching is complete.

Fix this in Business Process Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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