CVE-2024-32039: FreeRDP Integer overflow & OutOfBound Write in clear_decompress_residual_data
FreeRDP is a free implementation of the Remote Desktop Protocol. FreeRDP based clients using a version of FreeRDP prior to 3.5.0 or 2.11.6 are vulnerable to integer overflow and out-of-bounds write. Versions 3.5.0 and 2.11.6 patch the issue. As a workaround, do not use /gfx options (e.g. deactivate with /bpp:32 or /rfx as it is on by default).
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/FreeRDPto a version that resolves this vulnerability.Fixed in 3.5.0 - Upgrade
Upgrade
redhat/FreeRDPto a version that resolves this vulnerability.Fixed in 2.11.6 - Upgrade
Upgrade
debian/freerdp2to a version that resolves this vulnerability.Fixed in 2.11.7+dfsg1-6~deb12u1 - Upgrade
Upgrade
debian/freerdp3to a version that resolves this vulnerability.Fixed in 3.15.0+dfsg-2.1+deb13u3Fixed in 3.32.2+dfsg-1Fixed in 3.33.0+dfsg-1 - Upgrade
Upgrade
FreeRDPto a version that resolves this vulnerability.Fixed in 2.11.6 - Upgrade
Upgrade
FreeRDPto a version that resolves this vulnerability.Fixed in 3.5.0 - Configuration
As a workaround, do not use /gfx options; deactivate /gfx with /bpp:32 or /rfx.
FreeRDP-based clients /gfx = disabled
Event History
Frequently Asked Questions
What is the severity of CVE-2024-32039?
CVE-2024-32039 has been classified as a high severity vulnerability due to its potential for exploitation through integer overflow and out-of-bounds write.
How do I fix CVE-2024-32039?
To fix CVE-2024-32039, upgrade your FreeRDP version to 3.5.0 or 2.11.6 or later.
Which FreeRDP versions are affected by CVE-2024-32039?
FreeRDP versions prior to 3.5.0 and 2.11.6 are impacted by CVE-2024-32039.
What are the workarounds for CVE-2024-32039 if I cannot upgrade?
As a temporary workaround for CVE-2024-32039, avoid using the '/gfx' options in FreeRDP.
Can CVE-2024-32039 lead to remote code execution?
Yes, CVE-2024-32039 can potentially lead to remote code execution due to memory corruption caused by the vulnerability.