# CVE-2023-3223: Undertow: outofmemoryerror due to @multipartconfig handling

> Attackers can cause a Denial of Service in Undertow by sending large multipart requests, potentially bypassing file size limits.

- **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:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Sep 2023
- **Updated:** 2 Aug 2024
- **Also known as:** DEBIAN-CVE-2023-3223, GHSA-65h2-wf7m-q2v8, UBUNTU-CVE-2023-3223

## What is CVE-2023-3223?

CVE-2023-3223 is a high-severity denial of service vulnerability in Redhat Jboss Enterprise Application Platform, published on 27 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in undertow. Servlets annotated with @MultipartConfig may cause an OutOfMemoryError due to large multipart content. This may allow unauthorized users to cause remote Denial of Service (DoS) attack. If the server uses fileSizeThreshold to limit the file size, it's possible to bypass the limit by setting the file name in the request to null.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value)

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

2 open source packages ship an affected version, including io.undertow:undertow-parent. It affects 7 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.undertow:undertow-parent` | Maven | All versions | 2.2.24.Final |
| `io.undertow:undertow-parent` | Maven | All versions | 2.2.24.Final |

Products: Redhat Jboss Enterprise Application Platform, Redhat Jboss Enterprise Application Platform Text-Only Advisories, Redhat Openshift Container Platform, Redhat Openshift Container Platform for Ibm Linuxone, Redhat Openshift Container Platform for Power, Redhat Single Sign-On, Redhat Undertow.

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

Upgrade io.undertow:undertow-parent to 2.2.24.Final or later.

## Is CVE-2023-3223 being exploited?

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

## Other vulnerabilities in Redhat Jboss Enterprise Application Platform

- [CVE-2017-12149](https://insights.sbomify.com/CVE-2017-12149/): Red Hat JBoss Application Server Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2010-1428](https://insights.sbomify.com/CVE-2010-1428/): Red Hat JBoss Information Disclosure (medium 5.9, exploited in the wild)
- [CVE-2010-0738](https://insights.sbomify.com/CVE-2010-0738/): Red Hat JBoss Authentication Bypass (low 3.7, exploited in the wild)
- [CVE-2016-3690](https://insights.sbomify.com/CVE-2016-3690/): Deserialization in n/a (critical 9.8)
- [CVE-2017-7504](https://insights.sbomify.com/CVE-2017-7504/): Deserialization in JBoss (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-3223 is a high-severity denial of service vulnerability in Redhat Jboss Enterprise Application Platform, published on 27 Sep 2023. 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-2023-3223 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.undertow:undertow-parent (Maven): affected all versions; fixed in 2.2.24.Final
- io.undertow:undertow-parent (Maven): affected all versions; fixed in 2.2.24.Final

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

## Sources

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

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