CVE-2024-2613

What it actually does

Improper sanitization of data in QUIC ACK frame decoding leads to unbounded memory allocation resulting in resource exhaustion and process crash.

Why it matters to the business

Successful exploitation can cause denial-of-service outages on systems running the affected weldr-client package, interrupting update and management workflows with low likelihood given the age of the issue, static low EPSS, and absence from KEV.

How an attack unfolds

An attacker sends a crafted QUIC ACK frame over the network to a process using the vulnerable decoding logic; the missing sanitization triggers repeated memory allocations until the process exhausts resources and terminates.

How to fix it

Upgrade weldr-client on AlmaLinux 8 to version 35.5-1.el8 or later; apply vendor updates as soon as practical given the 939 days since disclosure.

How to confirm the fix worked

Confirm package version is at or above 35.5-1.el8 using package manager queries; monitor process memory usage and stability under QUIC traffic loads.

Typical attack path

1. Identify reachable instance of affected weldr-client component
2. Craft and transmit malicious QUIC ACK frame
3. Trigger repeated allocation during frame decoding
4. Exhaust memory leading to crash

How to detect it

Search application and system logs for unexpected process terminations or memory-related errors around QUIC traffic handling; correlate with network flows containing QUIC ACK frames preceding crashes.

What your security team should do

• Prioritize patching weldr-client to 35.5-1.el8 on all AlmaLinux 8 systems
• Review network exposure of any QUIC-dependent services
• Add the fixed version to standard update automation and vulnerability scanning policies