dbcve.org
Business Process Management SuiteApplication · Oracle

CVE-2018-3100

CRITICAL · 9.1 CVSS v3.0 Published 2018-07-18
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
Vulnerability in the Oracle Business Process Management Suite component of Oracle Fusion Middleware (subcomponent: Process Analysis & Discovery). Supported versions that are affected are 11.1.1.7.0, 11.1.1.9.0, 12.1.3.0.0, 12.2.1.2.0 and 12.2.1.3.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Business Process Management Suite. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Business Process Management Suite accessible data as well as unauthorized access to critical data or complete access to all Oracle Business Process Management Suite accessible data. CVSS 3.0 Base Score 9.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).

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

A detailed technical summary for this CVE is being prepared.

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 Management SuiteApplication
Affected:= 11.1.1.7.0= 11.1.1.9.0= 12.1.3.0.0= 12.2.1.2.0= 12.2.1.3.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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
Patch available Apply the vendor patch
Vendor patch www.oracle.com →
Recommended fix High confidence

Oracle BPMS 12.2.1.3.0 (or latest 12.2.x release) / Oracle BPMS 11.1.1.9.0 or later for 11g line

  1. 1. Review the Oracle July 2018 Critical Patch Update advisory at http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html for the specific patch for your version
  2. 2. Identify the exact patch number (e.g., WLS or BPMS patch) for your installed Oracle BPMS version from the advisory
  3. 3. Download and apply the July 2018 CPU patch for your specific version (11.1.1.7.0, 11.1.1.9.0, 12.1.3.0.0, or 12.2.1.2.0) using Oracle OPatch
  4. 4. Alternatively, upgrade to a later patched version: For 11.1.x line upgrade to 11.1.1.9.0 or later; For 12.1.3.x upgrade to 12.1.3.0.1 or later; For 12.2.1.2.x upgrade to 12.2.1.3.0 which includes the fix
  5. 5. After patching/upgrade, restart all Oracle WebLogic Server and BPMS components
  6. 6. Verify the vulnerability is remediated by confirming the patch is applied and testing the Process Analysis & Discovery functionality
Caveat Oracle mid-year patch upgrades typically include cumulative fixes; test in non-production first as some deprecated APIs or configuration changes may occur

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

We can apply and verify the patch for your build — typical engagement from $2,300. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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