# CVE-2024-2169: Implementations of UDP application protocols are susceptible to network loops and denial of service

> Unauthenticated attackers can cause denial of service and resource abuse in UDP protocol implementations via malicious packets.

- **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:** Yes
- **Published:** 19 Mar 2024
- **Updated:** 4 Sep 2024
- **Also known as:** GHSA-324p-3f7r-2rf5, MGASA-2024-0290

## What is CVE-2024-2169?

CVE-2024-2169 is a high-severity denial of service vulnerability in Microsoft RouterOS-TFTP, published on 19 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Implementations of UDP application protocol are vulnerable to network loops.   An unauthenticated attacker can use maliciously-crafted packets against a vulnerable implementation that can lead to Denial of Service (DOS) and/or abuse of resources.

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


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

Apply the vendor's patch.

## Is CVE-2024-2169 being exploited?

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

Public exploit code:

- This Python script automates the process of scanning for systems potentially vulnerable to the Loop DoS attack and the hypothetical CVE-2024-2169 vulnerability. It focuses on scanning ports associated with protocols susceptible to denial-of-service (DoS) attacks. The script can be used for educational purposes or authorized penetration testing. (github_poc): https://github.com/renancesarr/G3-Loop-DoS

## Fix prompt for AI coding agents

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

What it is: CVE-2024-2169 is a high-severity denial of service vulnerability in Microsoft RouterOS-TFTP, published on 19 Mar 2024. 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-2169 in the wild and no public exploit code.

Affected product: Microsoft RouterOS-TFTP. 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-2169/ (Markdown: https://insights.sbomify.com/CVE-2024-2169/index.md)
```

## Sources

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

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