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

> Attackers can render Iglu Server unresponsive via malicious payloads, halting event processing in the pipeline.

- **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-qcwf-jj36-gr7m

## What is CVE-2024-47214?

CVE-2024-47214 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 Iglu Server 0.13.0 and below. It is similar to CVE-2024-47212, but involves a different kind of malicious payload. As above, it can render Iglu Server completely unresponsive. If the operation of Iglu Server is not restored, event processing in the pipeline would eventually halt.

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

It affects 1 product.


Products: Snowplow Iglu Server.

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

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

## Is CVE-2024-47214 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-47212](https://insights.sbomify.com/CVE-2024-47212/): Denial of service in n/a (high 7.5)
- [CVE-2024-47217](https://insights.sbomify.com/CVE-2024-47217/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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