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

> A reachable assertion in TinyXML2 allows attackers to cause application exit via crafted XML input, leading to denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Oct 2024
- **Updated:** 30 Oct 2024
- **Also known as:** AZL-51871, AZL-51884, AZL-51888, AZL-51999, AZL-52020, DEBIAN-CVE-2024-50615, GHSA-884x-p7qm-gq3f, UBUNTU-CVE-2024-50615, openSUSE-SU-2025:14866-1

## What is CVE-2024-50615?

CVE-2024-50615 is a medium-severity denial of service vulnerability in n/a, published on 27 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

TinyXML2 through 10.0.0 has a reachable assertion for UINT_MAX/digit, that may lead to application exit, in tinyxml2.cpp XMLUtil::GetCharacterRef.

Weakness: CWE-617 (Reachable Assertion)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tinyxml2` | openSUSE:Tumbleweed | All versions | 10.1.0-1.1 |

Products: Tinyxml2 Project Tinyxml2.

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

Upgrade to a fixed version.

## Is CVE-2024-50615 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-50615 exists.

## Other vulnerabilities in n/a

- [CVE-2018-11210](https://insights.sbomify.com/CVE-2018-11210/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-50614](https://insights.sbomify.com/CVE-2024-50614/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-50615 is a medium-severity denial of service vulnerability in n/a, published on 27 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-50615 exists.

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

## Sources

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

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