dbcve.org
CoherenceApplication · Oracle

CVE-2021-2371

HIGH · 7.5 CVSS v3.1 Published 2021-07-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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: Core). Supported versions that are affected are 3.7.1.0, 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0 and 14.1.1.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via T3, IIOP to compromise Oracle Coherence. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Coherence. CVSS 3.1 Base Score 7.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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

Denial of service vulnerability in Oracle Coherence Core component. Unauthenticated attackers with network access via T3 or IIOP protocols can send specially crafted requests causing Oracle Coherence to hang or repeatedly crash.

MitigationApply Oracle Critical Patch Update (CPU) or specific patch for CVE-2021-2371. Alternatively, restrict network access to T3/IIOP 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= 14.1.1.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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify Oracle Coherence installation
    Search for coherence.jar files or Coherence installation directories. Common paths include $ORACLE_HOME/coherence, /opt/oracle/coherence, or check for coherence*.jar in application lib directories.
    Affected if Oracle Coherence software is found on the system
  2. Determine Coherence version
    Check the coherence.jar manifest file (META-INF/MANIFEST.MF) for the Implementation-Version attribute, or look for a version.txt/product.version file in the Coherence home directory.
    Affected if Installed version matches 3.7.1.0, 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0 exactly
  3. Check if T3 protocol is enabled
    Inspect Coherence configuration files (coherence-cache-config.xml, tangosol-coherence.xml, or tangosol-coherence-override.xml) for <cluster-config> or <unicast-listener> sections containing T3 protocol settings. Also check if the system property tangosol.coherence.mode includes 't3'.
    Affected if T3 protocol is explicitly enabled or configured in Coherence configuration files
  4. Check if IIOP protocol is enabled
    Inspect Coherence configuration for IIOP settings. Look for iiop-config.xml, or check coherence-cache-config.xml for <iiop-enabled>true</iiop-enabled> or similar IIOP service definitions.
    Affected if IIOP protocol is enabled in Coherence configuration
  5. Verify network exposure of T3/IIOP ports
    Check listening ports using netstat or ss commands. T3 typically uses port 7574 (or configurable), IIOP uses port 9000-9001 range. Determine if these ports are accessible from untrusted networks.
    Affected if T3 or IIOP ports are bound to 0.0.0.0 or otherwise exposed to untrusted network segments

The environment is affected if Oracle Coherence is installed with a version matching 3.7.1.0, 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0, or 14.1.1.0.0 AND either T3 or IIOP protocol is enabled and accessible over 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.

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

Apply Oracle Critical Patch Update (CPU) or specific patch for CVE-2021-2371. Alternatively, restrict network access to T3/IIOP ports or disable these protocols if not required.

Fix this in Coherence Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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