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

> Attackers can cause denial of service in Snowplow Collector by sending large payloads, potentially leading to data loss.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2025
- **Updated:** 7 Apr 2025
- **Also known as:** GHSA-qg7f-449v-85xg

## What is CVE-2024-56528?

CVE-2024-56528 is a high-severity denial of service vulnerability in n/a, published on 3 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This vulnerability affects Snowplow Collector 3.x before 3.3.0 (unless it’s set up behind a reverse proxy that establishes payload limits). It involves sending very large payloads to the Collector and can render it unresponsive to the rest of the requests. As a result, data would not enter the pipeline and would be potentially lost.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Snowplow Stream Collector.

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

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

## Is CVE-2024-56528 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-56528 is a high-severity denial of service vulnerability in n/a, published on 3 Apr 2025. 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-56528 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-56528/ (Markdown: https://insights.sbomify.com/CVE-2024-56528/index.md)
```

## Sources

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

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