CVE-2024-30161

What it actually does

Use-after-free condition where QNetworkReply header data is accessed through a dangling pointer in Qt WebAssembly builds.

Why it matters to the business

Web applications built with affected Qt versions for WebAssembly may experience crashes or memory corruption, potentially disrupting services or allowing remote code execution in browser environments.

How an attack unfolds

An attacker sends crafted network responses to a Qt WebAssembly application that trigger header processing after the underlying pointer has been freed, leading to memory corruption.

How to fix it

Upgrade Qt to a version outside 6.5.4, 6.5.5, and 6.6.2; rebuild and redeploy affected WebAssembly applications.

How to confirm the fix worked

Confirm Qt version in use is not 6.5.4, 6.5.5, or 6.6.2; test WebAssembly builds for absence of the dangling pointer access pattern in QNetworkReply handling.

Typical attack path

1. Deliver malicious network response to WebAssembly target
2. Trigger QNetworkReply header access path
3. Exploit dangling pointer for memory corruption or control flow hijack

How to detect it

Review application logs and browser console output for crashes or memory errors during network reply handling in Qt WebAssembly contexts; look for unexpected terminations tied to QNetworkReply usage.

What your security team should do

• Identify all Qt WebAssembly deployments and their exact versions
• Prioritize upgrade of any instances running 6.5.4, 6.5.5, or 6.6.2
• Monitor for memory corruption indicators in WebAssembly applications