# CVE-2024-53982: Arbitrary file download in Zoo-Project Echo Example

> Attackers can download arbitrary files from the server via path traversal in the default Echo example of Zoo-Project WPS.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2024
- **Updated:** 5 Dec 2024
- **Also known as:** GHSA-93rv-45r8-h5j4

## What is CVE-2024-53982?

CVE-2024-53982 is a high-severity path traversal vulnerability in ZOO-Project, published on 4 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ZOO-Project is a C-based WPS (Web Processing Service) implementation. A path traversal vulnerability was discovered in Zoo-Project Echo example. The Echo example available by default in Zoo installs implements file caching, which can be controlled by user-given parameters. No input validation is performed in this parameter, which allows an attacker to fully control the file which is returned in the response. Patch was committed in November 22nd, 2024.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2024-53982 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-53982 is a high-severity path traversal vulnerability in ZOO-Project, published on 4 Dec 2024. 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-2024-53982 in the wild and no public exploit code.

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

## Sources

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

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