# CVE-2023-40571: weblogic-framework Deserialization of Untrusted Data vulnerability


- **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:** Not known
- **Fix available:** No
- **Published:** 25 Aug 2023
- **Updated:** 2 Oct 2024

## What is CVE-2023-40571?

CVE-2023-40571 is a critical vulnerability in dream0x01 weblogic-framework, published on 25 Aug 2023. 

### Official description

weblogic-framework is a tool for detecting weblogic vulnerabilities. Versions 0.2.3 and prior do not verify the returned data packets, and there is a deserialization vulnerability which may lead to remote code execution. When weblogic-framework gets the command echo, it directly deserializes the data returned by the server without verifying it. At the same time, the classloader loads a lot of deserialization calls. In this case, the malicious serialized data returned by the server will cause remote code execution. Version 0.2.4 contains a patch for this issue.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2023-40571?

It affects 1 product.


Products: Weblogic-Framework Project Weblogic-Framework.

## How do I fix CVE-2023-40571?

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

## Is CVE-2023-40571 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-40571 and fix it if it is affected.

What it is: CVE-2023-40571 is a critical vulnerability in dream0x01 weblogic-framework, published on 25 Aug 2023. 
Exploitation: There is no known exploitation of CVE-2023-40571 in the wild and no public exploit code.

Affected product: dream0x01 weblogic-framework. 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-2023-40571/ (Markdown: https://insights.sbomify.com/CVE-2023-40571/index.md)
```

## Sources

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

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