# CVE-2024-1961: Path Traversal leading to Arbitrary File Write and RCE in vertaai/modeldb

> Attackers can write arbitrary files via path traversal in ModelDB, potentially achieving remote code execution by overwriting configuration files.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/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:** No
- **Published:** 16 Apr 2024
- **Updated:** 29 Aug 2024
- **Also known as:** GHSA-j9q5-gh3m-3cf9

## What is CVE-2024-1961?

CVE-2024-1961 is a high-severity path traversal vulnerability in vertaai/modeldb, published on 16 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

vertaai/modeldb is vulnerable to a path traversal attack due to improper sanitization of user-supplied file paths in its file upload functionality. Attackers can exploit this vulnerability to write arbitrary files anywhere in the file system by manipulating the 'artifact_path' parameter. This flaw can lead to Remote Code Execution (RCE) by overwriting critical files, such as the application's configuration file, especially when the application is run outside of Docker. The vulnerability is present in the NFSController.java and NFSService.java components of the application.

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

## Which versions are affected by CVE-2024-1961?


## How do I fix CVE-2024-1961?

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

## Is CVE-2024-1961 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1961 and fix it if it is affected.

What it is: CVE-2024-1961 is a high-severity path traversal vulnerability in vertaai/modeldb, published on 16 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-1961 in the wild and no public exploit code.

Affected product: vertaai/modeldb. 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-2024-1961/ (Markdown: https://insights.sbomify.com/CVE-2024-1961/index.md)
```

## Sources

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

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