CVE-2024-50614

What it actually does

Reachable assertion in TinyXML2's XMLUtil::GetCharacterRef when processing a character reference near UINT_MAX/16 causes the application to terminate.

Why it matters to the business

Attackers can trigger repeated crashes in applications that parse untrusted XML, leading to loss of service availability and potential disruption of dependent systems until mitigated.

How an attack unfolds

An attacker supplies a specially crafted XML document containing a character reference crafted to trigger the assertion in GetCharacterRef; the parser reaches the assert and the process exits.

How to fix it

Upgrade affected packages to the fixed versions: tomcat10 on SUSE Linux Enterprise Module for Web and Scripting 15 SP5 to 10.1.18-150200.5.8.1 and on openSUSE Leap 15.5 to 10.1.18-150200.5.8.1. Rebuild or redeploy any applications statically linking TinyXML2 after updating the library.

How to confirm the fix worked

Verify package versions match or exceed the listed fixed releases, recompile with updated TinyXML2 source if vendored, and confirm the assertion no longer triggers on test payloads containing large character references.

Typical attack path

1. Identify an endpoint or service that accepts and parses XML using an affected TinyXML2 version.
2. Craft an XML payload with a character reference value near UINT_MAX/16.
3. Submit the payload via the input channel (file upload, API request, or document processing).
4. Observe application termination and service unavailability.

How to detect it

Review application and system logs for abrupt process terminations or assertion failures during XML parsing; correlate with incoming XML requests around the time of the crash.

What your security team should do

• Prioritize patching Tomcat packages on SUSE and openSUSE systems within standard change windows given low EPSS and absence from KEV.
• Add XML input validation or size limits as a defense-in-depth measure until upgrades complete.
• Monitor for application crashes correlated with XML processing workloads.