Bug 1223347 (CVE-2024-32660)

Summary: VUL-0: CVE-2024-32660: freerdp: client crash via invalid huge allocation size
Product: [Novell Products] SUSE Security Incidents Reporter: SMASH SMASH <smash_bz>
Component: IncidentsAssignee: Security Team bot <security-team>
Status: NEW --- QA Contact: Security Team bot <security-team>
Severity: Normal    
Priority: P3 - Medium CC: carlos.lopez, ecsos, jweberhofer
Version: unspecified   
Target Milestone: ---   
Hardware: Other   
OS: Other   
URL: https://smash.suse.de/issue/402955/
Whiteboard: CVSSv3.1:SUSE:CVE-2024-32660:6.5:(AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H)
Found By: Security Response Team Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description SMASH SMASH 2024-04-24 11:58:33 UTC
FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.5.1, a malicious server can crash the FreeRDP client by sending invalid huge allocation size. Version 3.5.1 contains a patch for the issue. No known workarounds are available.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-32660
https://www.cve.org/CVERecord?id=CVE-2024-32660
https://github.com/FreeRDP/FreeRDP/commit/5e5d27cf310e4c10b854be7667bfb7a5d774eb47
https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-mxv6-2cw6-m3mx
https://oss-fuzz.com/testcase-detail/5559242514825216
Comment 2 Maintenance Automation 2024-05-29 16:30:12 UTC
SUSE-SU-2024:1835-1: An update that solves four vulnerabilities can now be installed.

Category: security (important)
Bug References: 1223346, 1223347, 1223348, 1223353
CVE References: CVE-2024-32658, CVE-2024-32659, CVE-2024-32660, CVE-2024-32661
Maintenance Incident: [SUSE:Maintenance:34025](https://smelt.suse.de/incident/34025/)
Sources used:
SUSE Linux Enterprise Software Development Kit 12 SP5 (src):
 freerdp-2.1.2-12.47.1
SUSE Linux Enterprise Workstation Extension 12 12-SP5 (src):
 freerdp-2.1.2-12.47.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.