# CVE-2017-10271: Oracle Corporation WebLogic Server Remote Code Execution

> Unauthenticated attackers can compromise Oracle WebLogic Server via T3 protocol, leading to server takeover and denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Yes, since 10 Feb 2022 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2017
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-h7p4-68h5-84f3

## What is CVE-2017-10271?

CVE-2017-10271 is a high-severity authentication bypass vulnerability in Oracle Weblogic Server, published on 19 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Oracle WebLogic Server component of Oracle Fusion Middleware (subcomponent: WLS Security). Supported versions that are affected are 10.3.6.0.0, 12.1.3.0.0, 12.2.1.1.0 and 12.2.1.2.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via T3 to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in takeover of Oracle WebLogic Server. CVSS 3.0 Base Score 7.5 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2017-10271?

It affects 1 product.


Products: Oracle Weblogic Server.

## How do I fix CVE-2017-10271?

No fix has been published for CVE-2017-10271 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 10 Aug 2022.

## Is CVE-2017-10271 being exploited?

Yes. Attackers have exploited CVE-2017-10271 in the wild since at least 10 Feb 2022, including in ransomware campaigns.

Public exploit code:

- Java反序列化漏洞利用工具V1.0    Java反序列化相关漏洞的检查工具，采用JDK 1.8+NetBeans8.2开发，软件运行必须安装JDK 1.8或者以上版本。   支持：weblogic xml反序列化漏洞 CVE-2017-10271/CNVD-C-2019-48814/CVE-2019-2725检查。 (github_poc): https://github.com/shack2/javaserializetools
- WebLogic Exploit (github_poc): https://github.com/c0mmand3rOpSec/CVE-2017-10271
- Oracle WebLogic WLS-WSAT Remote Code Execution Exploit (CVE-2017-10271) (github_poc): https://github.com/kkirsche/CVE-2017-10271
- WebLogic CNVD-C-2019_48814 CVE-2017-10271 Scan By 7kbstorm (github_poc): https://github.com/7kbstorm/WebLogic_CNVD_C2019_48814
- CVE-2019-2725poc汇总 更新绕过CVE-2017-10271补丁POC (github_poc): https://github.com/SkyBlueEternal/CNVD-C-2019-48814-CNNVD-201904-961
- CVE-2017-10271 WEBLOGIC RCE  (TESTED) (github_poc): https://github.com/1337g/CVE-2017-10271

## Other vulnerabilities in Oracle Weblogic Server

- [CVE-2020-14750](https://insights.sbomify.com/CVE-2020-14750/): Oracle WebLogic Server Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2020-14882](https://insights.sbomify.com/CVE-2020-14882/): Oracle WebLogic Server Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2020-14644](https://insights.sbomify.com/CVE-2020-14644/): Oracle WebLogic Server Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2020-2883](https://insights.sbomify.com/CVE-2020-2883/): Oracle WebLogic Server Unspecified (critical 9.8, exploited in the wild)
- [CVE-2020-2551](https://insights.sbomify.com/CVE-2020-2551/): Oracle Fusion Middleware Unspecified (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-10271 and fix it if it is affected.

What it is: CVE-2017-10271 is a high-severity authentication bypass vulnerability in Oracle Weblogic Server, published on 19 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2017-10271 in the wild since at least 10 Feb 2022, including in ransomware campaigns.

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-2017-10271/ (Markdown: https://insights.sbomify.com/CVE-2017-10271/index.md)
```

## Sources

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

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