dbcve.org
CoherenceApplication · Oracle

CVE-2020-2915

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Vulnerability in the Oracle Coherence product of Oracle Fusion Middleware (component: Caching, CacheStore, Invocation). Supported versions that are affected are 3.7.1.0, 12.1.3.0.0, 12.2.1.3.0 and 12.2.1.4.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via IIOP, T3 to compromise Oracle Coherence. Successful attacks of this vulnerability can result in takeover of Oracle Coherence. CVSS 3.0 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

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

Critical deserialization vulnerability in Oracle Coherence allowing unauthenticated remote code execution via IIOP or T3 network protocols. Attackers can achieve complete takeover of the Coherence service without any credentials.

MitigationApply Oracle Critical Patch Update (CPU) containing the fix for CVE-2020-2915. If immediate patching is not possible, restrict network access to IIOP (port 9001) and T3 (port 7001) ports or disable these protocols if not required.

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
CoherenceApplication
Affected:= 3.7.1.0= 12.1.3.0.0= 12.2.1.3.0= 12.2.1.4.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
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Identify if Oracle Coherence is installed
    Check for Coherence processes running on the system (look for 'coherence' or 'oracle.coherence' in process list) or look for Coherence installation directories on the system
    Affected if Coherence is found running or installed on the system
  2. Determine the installed Coherence version
    Locate and read the Coherence product version file, typically found in the Coherence home directory or check the product's manifest/wrapper properties
    Affected if The installed version matches 3.7.1.0, 12.1.3.0.0, 12.2.1.3.0, or 12.2.1.4.0
  3. Check if IIOP protocol is enabled
    Inspect Coherence configuration files for IIOP settings (typically in tangosol-coherence.xml or similar coherence-config files) or check if port 9001 is listening
    Affected if IIOP protocol is enabled and port 9001 is open/listening
  4. Check if T3 protocol is enabled
    Inspect Coherence configuration files for T3 settings or check if port 7001 is listening
    Affected if T3 protocol is enabled and port 7001 is open/listening

A user is affected if they have Oracle Coherence installed with a matching vulnerable version AND either IIOP (port 9001) or T3 (port 7001) protocols are enabled and exposed on the network.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update (CPU) containing the fix for CVE-2020-2915. If immediate patching is not possible, restrict network access to IIOP (port 9001) and T3 (port 7001) ports or disable these protocols if not required.

Recommended fix High confidence

Oracle Coherence 12.2.1.4.1 (or later 12.2.x) or Oracle Coherence 14.1.1.0.0

  1. 1. Identify Oracle Coherence deployment versions (3.7.1.0, 12.1.3.0.0, 12.2.1.3.0, or 12.2.1.4.0) in the environment
  2. 2. If running 12.2.1.x versions, upgrade to Oracle Coherence 12.2.1.4.1 or later (patch 31246887 contains the fix)
  3. 3. For 12.1.3.0.0, apply Oracle Critical Patch Update January 2020 (or later) patch bundle for WebLogic/Coherence
  4. 4. For 3.7.1.0, this is an older unsupported version - upgrade to a supported major version such as Oracle Coherence 14.1.1.0.0 or later
  5. 5. After upgrade, restrict network exposure: disable T3/IIOP protocols if not required, or restrict access to trusted networks only
  6. 6. Verify the fix by confirming the Coherence version and reviewing Oracle January 2020 CPU documentation
Caveat Upgrading major versions may require compatibility testing - verify application code works with the newer Coherence release, especially around serialization and cache configuration APIs

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

Fix this in Coherence Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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