Affected: AlmaLinux:8: freerdp-devel, AlmaLinux:8: vinagre

FreeRDP is a free implementation of the Remote Desktop Protocol (RDP), released under the Apache license. The xfreerdp client can connect to RDP servers such as Microsoft Windows machines, xrdp, and VirtualBox.

The vinagre packages provide the Vinagre remote desktop viewer for the GNOME desktop.

The following packages have been upgraded to a later upstream version: freerdp (2.1.1). (BZ#1834287)

Security Fix(es):

* freerdp: Out of bound read in cliprdr_server_receive_capabilities (CVE-2020-11018)

* freerdp: Out of bound read/write in usb redirection channel (CVE-2020-11039)

* freerdp: out-of-bounds read in update_read_icon_info function (CVE-2020-11042)

* freerdp: out-of-bounds read in autodetect_recv_bandwidth_measure_results function (CVE-2020-11047)

* freerdp: Out-of-bounds read in ntlm_read_ChallengeMessage in winpr/libwinpr/sspi/NTLM/ntlm_message.c. (CVE-2020-13396)

* freerdp: Out-of-bounds read in security_fips_decrypt in libfreerdp/core/security.c (CVE-2020-13397)

* freerdp: Out of bound read in update_recv could result in a crash (CVE-2020-11019)

* freerdp: Integer overflow in VIDEO channel (CVE-2020-11038)

* freerdp: Out of bound access in clear_decompress_subcode_rlex (CVE-2020-11040)

* freerdp: Unchecked read of array offset in rdpsnd_recv_wave2_pdu (CVE-2020-11041)

* freerdp: out of bound read in rfx_process_message_tileset (CVE-2020-11043)

* freerdp: double free in update_read_cache_bitmap_v3_order function (CVE-2020-11044)

* freerdp: out of bound…

In FreeRDP greater than 1.1 and before 2.0.0, there is an out-of-bounds read in update_read_icon_info. It allows reading a attacker-defined amount of client memory (32bit unsigned -> 4GB) to an intermediate buffer. This can be used to crash the client or store information for later retrieval. This has been patched in 2.0.0.

Affected: openEuler:20.03-LTS: freerdp, openEuler:20.03-LTS-SP1: freerdp

FreeRDP is a client implementation of the Remote Desktop Protocol (RDP) that follows Microsoft's open specifications. This package provides the client applications xfreerdp and wlfreerdp.\r\n\r\n Security Fix(es):\r\n\r\n libfreerdp/core/update.c in FreeRDP versions > 1.1 through 2.0.0-rc4 has an Out-of-bounds Read.(CVE-2020-11526)\r\n\r\n In FreeRDP greater than 1.2 and before 2.0.0, a double free in update_read_cache_bitmap_v3_order crashes the client application if corrupted data from a manipulated server is parsed. This has been patched in 2.0.0.(CVE-2020-11044)\r\n\r\n In FreeRDP greater than 1.1 and before 2.0.0, there is an out-of-bounds read in update_read_icon_info. It allows reading a attacker-defined amount of client memory (32bit unsigned -> 4GB) to an intermediate buffer. This can be used to crash the client or store information for later retrieval. This has been patched in 2.0.0.(CVE-2020-11042)\r\n\r\n In FreeRDP before version 2.1.2, an out of bound reads occurs resulting in accessing a memory location that is outside of the boundaries of the static array PRIMARY_DRAWING_ORDER_FIELD_BYTES. This is fixed in version 2.1.2.(CVE-2020-11095)\r\n\r\n In FreeRDP after 1.0 and before 2.0.0, there is an out-of-bound read in in update_read_bitmap_data that allows client memory to be read to an image buffer. The result displayed on screen as colour.(CVE-2020-11045)\r\n\r\n libfreerdp/gdi/gdi.c in FreeRDP > 1.0 through 2.0.0-rc4 has an Out-of-bounds Read.(CVE-2020-…

freerdp: Out of bound read in cliprdr_server_receive_capabilities freerdp: Out of bound read in update_recv could result in a crash freerdp: Integer overflow in VIDEO channel freerdp: Out of bound read/write in usb redirection channel freerdp: Out of bound access in clear_decompress_subcode_rlex freerdp: Unchecked read of array offset in rdpsnd_recv_wave2_pdu freerdp: out-of-bounds read in update_read_icon_info function freerdp: out of bound read in rfx_process_message_tileset freerdp: double free in update_read_cache_bitmap_v3_order function freerdp: out of bounds read in update_read_bitmap_data function freerdp: out of bounds seek in update_read_synchronize function could lead out of bounds read freerdp: out-of-bounds read in autodetect_recv_bandwidth_measure_results function freerdp: out-of-bounds read could result in aborting the session freerdp: out-of-bound read of client memory that is then passed on to the protocol parser freerdp: stream out-of-bounds seek in rdp_read_font_capability_set could lead to out-of-bounds read freerdp: out-of-bounds read in cliprdr_read_format_list function freerdp: out-of-bounds read in ntlm_read_ntlm_v2_client_challenge function freerdp: out-of-bounds read in ntlm_read_AuthenticateMessage freerdp: out-of-bounds read in ntlm_read_NegotiateMessage freerdp: out-of-bounds read in irp functions freerdp: out-of-bounds read in gdi.c freerdp: out-of-bounds read in bitmap.c freerdp: Stream pointer out of bounds in update_recv_secondary_order could…

Affected: Ubuntu:16.04:LTS: freerdp, Ubuntu:18.04:LTS: freerdp, Ubuntu:18.04:LTS: freerdp2, Ubuntu:20.04:LTS: freerdp2

In FreeRDP greater than 1.1 and before 2.0.0, there is an out-of-bounds read in update_read_icon_info. It allows reading a attacker-defined amount of client memory (32bit unsigned -> 4GB) to an intermediate buffer. This can be used to crash the client or store information for later retrieval. This has been patched in 2.0.0.