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

> Attackers can degrade event forwarding performance to Google Tag Manager Server Side by triggering infinite retries via invalid headers.

- **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-3wrm-64r6-6q6c

## What is CVE-2024-47215?

CVE-2024-47215 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

An issue was discovered in Snowbridge setups sending data to Google Tag Manager Server Side. It involves attaching an invalid GTM SS preview header to events, causing them to be retried indefinitely. As a result, the performance of forwarding events to GTM SS overall can be affected (latency, throughput).

Weakness: CWE-703 (Improper Check or Handling of Exceptional Conditions)

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

It affects 1 product.


Products: Snowplow Snowbridge.

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

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

## Is CVE-2024-47215 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-47215 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-47215 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-47215/ (Markdown: https://insights.sbomify.com/CVE-2024-47215/index.md)
```

## Sources

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

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