# CVE-2024-6583: Path Traversal in stangirard/quivr

> Attackers can upload files to arbitrary paths in an S3 bucket by manipulating file paths in upload requests within the Quivr application.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **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:** 20 Mar 2025
- **Updated:** 20 Mar 2025
- **Also known as:** GHSA-332g-rf22-2vcg

## What is CVE-2024-6583?

CVE-2024-6583 is a medium-severity path traversal vulnerability in stangirard/quivr, published on 20 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A path traversal vulnerability exists in the latest version of stangirard/quivr. This vulnerability allows an attacker to upload files to arbitrary paths in an S3 bucket by manipulating the file path in the upload request.

Weakness: CWE-23 (Relative Path Traversal)

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

It affects 1 product.


Products: Quivr Quivr.

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

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

## Is CVE-2024-6583 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6583 exists.

## Other vulnerabilities in stangirard/quivr

- [CVE-2024-5885](https://insights.sbomify.com/CVE-2024-5885/): Server-Side Request Forgery (SSRF) in stangirard/quivr (high 8.6)
- [CVE-2024-4851](https://insights.sbomify.com/CVE-2024-4851/): SSRF Vulnerability in stangirard/quivr (high 7.7)
- [CVE-2024-6229](https://insights.sbomify.com/CVE-2024-6229/): Stored XSS in stangirard/quivr (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6583 is a medium-severity path traversal vulnerability in stangirard/quivr, published on 20 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6583 exists.

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

## Sources

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

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