# CVE-2024-21875: DoS attack when broadcasting billboard messages

> Attackers can cause a denial of service on Hacker Hotel Badge 2024 devices by flooding billboard messages due to lack of resource limits.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2024
- **Updated:** 11 Mar 2025
- **Also known as:** GHSA-jmph-rxrw-5rrh

## What is CVE-2024-21875?

CVE-2024-21875 is a medium-severity denial of service vulnerability in Badge.team Hacker Hotel Badge 2024, published on 11 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Allocation of Resources Without Limits or Throttling vulnerability in Badge leading to a denial of service attack.Team Hacker Hotel Badge 2024 on risc-v (billboard modules) allows Flooding.This issue affects Hacker Hotel Badge 2024: from 0.1.0 through 0.1.3.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 1 product.


Products: Badge.team Hacker Hotel Badge 2024.

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

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

## Is CVE-2024-21875 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-21875 is a medium-severity denial of service vulnerability in Badge.team Hacker Hotel Badge 2024, published on 11 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-21875 in the wild and no public exploit code.

Affected product: Badge.team Hacker Hotel Badge 2024. 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-21875/ (Markdown: https://insights.sbomify.com/CVE-2024-21875/index.md)
```

## Sources

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

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