# CVE-2020-2555: Oracle Multiple Products Remote Code Execution

> Unauthenticated attackers can achieve full system takeover via network access due to unsafe deserialization in Oracle Coherence.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jan 2020
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-gm93-pfh3-mrf3

## What is CVE-2020-2555?

CVE-2020-2555 is a critical unsafe deserialization vulnerability in Oracle Access Manager, published on 15 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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).

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2020-2555?

It affects 9 products.


Products: Oracle Access Manager, Oracle Coherence, Oracle Commerce Platform, Oracle Communications Diameter Signaling Router, Oracle Healthcare Data Repository, Oracle Rapid Planning, Oracle Retail Assortment Planning, Oracle Utilities Framework, Oracle Webcenter Portal.

## How do I fix CVE-2020-2555?

No fix has been published for CVE-2020-2555 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2020-2555 being exploited?

Yes. Attackers have exploited CVE-2020-2555 in the wild since at least 3 Nov 2021.

Public exploit code:

- Weblogic com.tangosol.util.extractor.ReflectionExtractor RCE (github_poc): https://github.com/Y4er/CVE-2020-2555
- CVE-2020-2555 Python POC (github_poc): https://github.com/wsfengfan/CVE-2020-2555
- CVE-2020-2555 (github_poc): https://github.com/Maskhe/cve-2020-2555
- https://github.com/Hu3sky/CVE-2020-2555 (github_poc): https://github.com/Hu3sky/CVE-2020-2555
- poc for CVE-2020-2555 (github_poc): https://github.com/Qynklee/POC_CVE-2020-2555
- WebLogic Server Deserialization RCE - BadAttributeValueExpException (metasploit)

## Other vulnerabilities in Oracle Access Manager

- [CVE-2021-35587](https://insights.sbomify.com/CVE-2021-35587/): Oracle Fusion Middleware Unspecified (critical 9.8, exploited in the wild)
- [CVE-2026-71133](https://insights.sbomify.com/CVE-2026-71133/): Auth bypass in Oracle Access Manager (critical 10.0)
- [CVE-2026-60358](https://insights.sbomify.com/CVE-2026-60358/): Auth bypass in Oracle Access Manager (critical 10.0)
- [CVE-2026-71163](https://insights.sbomify.com/CVE-2026-71163/): Missing authorization in Oracle Access Manager (critical 9.9)
- [CVE-2026-73945](https://insights.sbomify.com/CVE-2026-73945/): Auth bypass in Oracle Access Manager (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-2555 and fix it if it is affected.

What it is: CVE-2020-2555 is a critical unsafe deserialization vulnerability in Oracle Access Manager, published on 15 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2020-2555 in the wild since at least 3 Nov 2021.

Affected product: Oracle Access Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-2555/ (Markdown: https://insights.sbomify.com/CVE-2020-2555/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-2555
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-2555
- OSV: https://osv.dev/vulnerability/CVE-2020-2555

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-2555/
Summaries are generated and may contain mistakes; the official description above is the record.