# CVE-2017-10352: Denial of service in WebLogic Server

> Unauthenticated attackers can cause complete denial of service and unauthorized data access in Oracle WebLogic Server via HTTP.

- **Severity:** Critical 9.9 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2017
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-8mmg-3wxv-vmg6

## What is CVE-2017-10352?

CVE-2017-10352 is a critical denial of service 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 - Web Services). The supported version that is affected are 10.3.6.0.0, 12.1.3.0.0, 12.2.1.1.0, 12.2.1.2.0 and 12.2.1.3.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle WebLogic Server. While the vulnerability is in Oracle WebLogic Server, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle WebLogic Server as well as unauthorized update, insert or delete access to some of Oracle WebLogic Server accessible data and unauthorized read access to a subset of Oracle WebLogic Server accessible data. CVSS 3.0 Base Score 9.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:H).

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

It affects 1 product.


Products: Oracle Weblogic Server.

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

No fix has been published for CVE-2017-10352 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-10352 being exploited?

There is no known exploitation of CVE-2017-10352 in the wild and no public exploit code.

Public exploit code:

- CVE-2017-10352 CVE-2017-10271 weblogic-XMLDecoder (github_poc): https://github.com/bigsizeme/weblogic-XMLDecoder

## 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-10352 and fix it if it is affected.

What it is: CVE-2017-10352 is a critical denial of service 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: There is no known exploitation of CVE-2017-10352 in the wild and no public exploit code.

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

## Sources

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

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