# CVE-2023-5245: Zip slip in mleap

> Attackers can exploit path traversal in MLeap's model loading to create arbitrary files, potentially leading to remote code execution.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Nov 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-897x-xvj8-42rq

## What is CVE-2023-5245?

CVE-2023-5245 is a high-severity path traversal vulnerability in combust:mleap, published on 15 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

FileUtil.extract() enumerates all zip file entries and extracts each file without validating whether file paths in the archive are outside the intended directory.

When creating an instance of TensorflowModel using the saved_model format and an exported tensorflow model, the apply() function invokes the vulnerable implementation of FileUtil.extract().

Arbitrary file creation can directly lead to code execution

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

2 open source packages ship an affected version, including ml.combust.mleap:mleap-runtime_2.12. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ml.combust.mleap:mleap-runtime_2.12` | Maven | All versions | 0.23.1 |
| `ml.combust.mleap:mleap-runtime_2.12` | Maven | All versions | 0.23.1 |

Products: Combust Mleap.

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

Upgrade ml.combust.mleap:mleap-runtime_2.12 to 0.23.1 or later.

## Is CVE-2023-5245 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-5245 is a high-severity path traversal vulnerability in combust:mleap, published on 15 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-5245 in the wild and no public exploit code.

Affected packages and fixed versions:
- ml.combust.mleap:mleap-runtime_2.12 (Maven): affected all versions; fixed in 0.23.1
- ml.combust.mleap:mleap-runtime_2.12 (Maven): affected all versions; fixed in 0.23.1

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

## Sources

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

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