# CVE-2024-57782: Denial of service in n/a

> Attackers can cause a denial of service in Docker-proxy, disrupting container networking services.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Feb 2025
- **Updated:** 17 Mar 2025
- **Also known as:** GHSA-5p75-8vmp-h6xw

## What is CVE-2024-57782?

CVE-2024-57782 is a medium-severity denial of service vulnerability in n/a, published on 13 Feb 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

An issue in Docker-proxy v18.09.0 allows attackers to cause a denial of service.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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


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

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

## Is CVE-2024-57782 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-57782 is a medium-severity denial of service vulnerability in n/a, published on 13 Feb 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-57782 in the wild and no public exploit code.

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

## Sources

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

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