dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 May 2022.
Access ManagerApplication · Oracle

CVE-2020-2555

CRITICAL · 9.8 CVSS v3.1 Published 2020-01-15
Fix available
A fix is available. Upgrade to after 11.3.2 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit 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 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 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

This is a critical unauthenticated remote code execution vulnerability in Oracle Coherence's deserialization handling within the Caching, CacheStore, and Invocation components. The vulnerability is exploited via the T3 protocol (Oracle's WebLogic/Coherence communication protocol) by sending specially crafted serialized Java objects that bypass existing gadget chain protections, leading to complete system compromise.

MitigationApply Oracle Critical Patch Update (CPU) or upgrade to a patched version of Oracle Coherence (12.2.1.4.0+ or 14.1.1.0.0+). If immediate patching is not possible, disable T3/IIOP protocols and restrict network access to Coherence ports.

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
Access ManagerApplication
Affected:= 11.1.2.3.0
CoherenceApplication
Affected:= 3.7.1.0= 12.1.3.0.0= 12.2.1.3.0= 12.2.1.4.0
Commerce PlatformApplication
Affected:>= 11.3.0, <= 11.3.2= 11.0.0= 11.1.0= 11.2.0
Communications Diameter Signaling RouterApplication
Affected:>= 8.0.0, <= 8.2.2
Healthcare Data RepositoryApplication
Affected:= 7.0.1
Rapid PlanningApplication
Affected:= 12.1= 12.2
Retail Assortment PlanningApplication
Affected:= 15.0= 16.0
Utilities FrameworkApplication
Affected:>= 4.3.0.1.0, <= 4.3.0.6.0= 4.2.0.2.0= 4.2.0.3.0= 4.4.0.0.0= 4.4.0.2.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 Oracle Coherence installation and version
    Locate Coherence installation directories and check version files or use coherence versioning commands. Common locations include ORACLE_HOME/coherence or check product inventory files. Compare your installed version to affected versions: 3.7.1.0, 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0
    Affected if Your environment runs any of the affected Coherence versions listed in the CVE
  2. Identify other affected Oracle products
    Review installed Oracle products against the list: Oracle Access Manager 11.1.2.3.0, Oracle Commerce Platform 11.0.0-11.3.2, Oracle Communications Diameter Signaling Router 8.0.0-8.2.2, Oracle Healthcare Data Repository 7.0.1, Oracle Rapid Planning 12.1-12.2, Oracle Retail Assortment Planning 15.0-16.0, Oracle Utilities Framework 4.2.0.2.0-4.4.0.2.0
    Affected if Any of these specific product versions are installed in your environment
  3. Determine if T3 protocol is enabled
    Check Coherence configuration files (typically tangosol-coherence.xml or coherence-cache-config.xml) for T3 protocol settings. The T3 protocol is often configured in the cluster configuration or explicitly defined in the operational config. Look for T3-related network transport definitions.
    Affected if T3 protocol is explicitly enabled in your Coherence or product configuration
  4. Check for exposed T3 network listeners
    Scan for listening ports commonly used by Coherence T3 (default port 7778, also ports in the 9000-9100 range). Use netstat or port scanning tools to identify if Coherence T3 ports are accessible on network interfaces. Check firewall rules and Coherence cluster member configurations for exposed T3 endpoints.
    Affected if T3 protocol ports are listening and accessible from network locations where untrusted users could connect

Your environment is affected if you run any of the listed product versions AND the T3 protocol is enabled and network-accessible in your deployment.

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
Upgrade available Upgrade to a release after 11.3.2
Vendor patch www.oracle.com →
Interim mitigation

Apply Oracle Critical Patch Update (CPU) or upgrade to a patched version of Oracle Coherence (12.2.1.4.0+ or 14.1.1.0.0+). If immediate patching is not possible, disable T3/IIOP protocols and restrict network access to Coherence ports.

Recommended fix High confidence

Oracle Coherence 12.2.1.4.3+ or 12.2.1.3.5+ or 12.1.3.0.5+ or 3.7.1.17+ (apply January 2020 CPU)

  1. 1. Identify the exact Oracle Coherence version in use by checking the manifest or installation directory
  2. 2. Download and apply the January 2020 Critical Patch Update (CPU) from Oracle Support
  3. 3. For Coherence 3.7.1.0, upgrade to version 3.7.1.17 or later
  4. 4. For Coherence 12.1.3.0.0, upgrade to version 12.1.3.0.5 or later
  5. 5. For Coherence 12.2.1.3.0, upgrade to version 12.2.1.3.5 or later
  6. 6. For Coherence 12.2.1.4.0, upgrade to version 12.2.1.4.3 or later
  7. 7. Restart all Coherence cache servers and affected dependent services after patching
  8. 8. Verify the patch was applied successfully by checking the Coherence version and testing the T3 endpoint
Caveat Patch application may require downtime for Coherence cluster restart; test thoroughly in non-production environment before production deployment

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

Fix this in Access Manager Exploited in the wild — priority engagement
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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