# CVE-2015-4852: Oracle WebLogic Server Deserialization of Untrusted Data

> Remote attackers can execute arbitrary commands on Oracle WebLogic Server by sending crafted serialized Java objects via the T3 protocol.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** Yes
- **Published:** 18 Nov 2015
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-7r6v-mxc2-pg49, UBUNTU-CVE-2015-4852, USN-6936-1

## What is CVE-2015-4852?

CVE-2015-4852 is a critical unsafe deserialization vulnerability in Oracle Weblogic Server, published on 18 Nov 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WLS Security component in Oracle WebLogic Server 10.3.6.0, 12.1.2.0, 12.1.3.0, and 12.2.1.0 allows remote attackers to execute arbitrary commands via a crafted serialized Java object in T3 protocol traffic to TCP port 7001, related to oracle_common/modules/com.bea.core.apache.commons.collections.jar. NOTE: the scope of this CVE is limited to the WebLogic Server product.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2015-4852?

It affects 3 products.


Products: Oracle Storagetek Tape Analytics Sw Tool, Oracle Virtual Desktop Infrastructure, Oracle Weblogic Server.

## How do I fix CVE-2015-4852?

Apply the vendor's patch. US federal agencies must fix it by 3 May 2022.

## Is CVE-2015-4852 being exploited?

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

Public exploit code:

- Python script to exploit CVE-2015-4852. (github_poc): https://github.com/roo7break/serialator
- CVE-2015-4852、CVE-2016-0638、CVE-2016-3510、CVE-2019-2890漏洞POC (github_poc): https://github.com/zhzhdoai/Weblogic_Vuln
- CVE-2015-4852 Oracle WebLogic Scanner (github_poc): https://github.com/AndersonSingh/serialization-vulnerability-scanner
- https://github.com/nex1less/CVE-2015-4852 (github_poc): https://github.com/nex1less/CVE-2015-4852
- Oracle Weblogic Server Deserialization RCE - Raw Object (metasploit)
- Websphere/JBoss/OpenNMS/Symantec Endpoint Protection Manager - Java Deserialization Remote Code Execution (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-4852 and fix it if it is affected.

What it is: CVE-2015-4852 is a critical unsafe deserialization vulnerability in Oracle Weblogic Server, published on 18 Nov 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2015-4852 in the wild since at least 3 Nov 2021.

Affected product: Oracle Weblogic Server. 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-2015-4852/ (Markdown: https://insights.sbomify.com/CVE-2015-4852/index.md)
```

## Sources

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

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