Solutions Business ManagerApplication · Microfocus

CVE-2018-7682

MEDIUM · 6.5 CVSS v3.0 Published 2018-06-22
Fix available
A fix is available. Upgrade to 11.4 or later.
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
Micro Focus Solutions Business Manager versions prior to 11.4 allows a user to invoke SBM RESTful services across domains.

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

Micro Focus Solutions Business Manager versions prior to 11.4 contains a cross-domain vulnerability in its RESTful services implementation, allowing users to invoke SBM RESTful services across different domains. This is likely a missing or misconfigured Cross-Origin Resource Sharing (CORS) policy or similar origin validation flaw in the web service layer.

MitigationUpgrade to Solutions Business Manager version 11.4 or later, which contains the fix for proper cross-domain request validation in RESTful services.

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
Solutions Business ManagerApplication
Affected:< 11.4

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

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 Solutions Business Manager version
    Locate the installed Solutions Business Manager version - typically found in the product's About section, installation directory, or by querying the system inventory. Common locations include the program files directory or the SBM application administration interface.
    Affected if The installed version is any release prior to 11.4 (for example, 11.3.x, 11.2.x, earlier versions).
  2. Confirm RESTful services are exposed
    Determine if the SBM RESTful services endpoint is accessible. This is typically at a URL path such as /sbmservices/rest/ or /api/ under the SBM web application root. Check if these endpoints respond to HTTP requests.
    Affected if RESTful services are enabled and reachable over the network (even on localhost).
  3. Test CORS response headers on REST endpoints
    Send an HTTP request to a RESTful service endpoint (such as a GET request to a data service) with an Origin header set to a different domain (for example, http://malicious-site.com). Inspect the response headers for Access-Control-Allow-Origin and Access-Control-Allow-Credentials headers.
    Affected if The response includes Access-Control-Allow-Origin: * (wildcard) or reflects the arbitrary Origin value back without proper validation, indicating missing origin validation.
  4. Review CORS configuration if accessible
    If you have administrative access to the SBM configuration, locate the web service or application server configuration files (typically in the SBM configuration directory or the underlying application server settings) and examine CORS-related settings.
    Affected if No origin validation is configured, or the configuration explicitly allows arbitrary cross-origin requests.

You are affected if Solutions Business Manager version is below 11.4 AND the RESTful services are accessible with improper or missing CORS origin validation.

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
Upgrade available Upgrade to 11.4 or later
Fixed in 11.4
Interim mitigation

Upgrade to Solutions Business Manager version 11.4 or later, which contains the fix for proper cross-domain request validation in RESTful services.

Fix this in Solutions Business Manager 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-7682 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-7682 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