CVE-2019-17177

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-11522)\r\n\r\n libfreerdp/codec/interleaved.c in FreeRDP versions > 1.0 through 2.0.0-rc4 has an Out-of-bounds Write.(CVE-2020-11524)\r\n\r\n libfreerdp/codec/planar.c in FreeRDP version > 1.0 through 2.0.0-rc4 has an Out-of-bounds Write.(CVE-2020-11521)\r\n\r\n libfreerdp/cache/bitmap.c in FreeRDP versions > 1.0 through 2.0.0-rc4 has an Out of bounds read.(CVE-2020-11525)\r\n\r\n libfreerdp/codec/planar.c in FreeRDP version > 1.0 through 2.0.0-rc4 has an Out-of-bounds Write.(CVE-2020-11521)\r\n\r\n libfreerdp/codec/region.c in FreeRDP through 1.1.x and 2.x through 2.0.0-rc4 has memory leaks because a supplied realloc pointer (i.e., the first argument to realloc) is also used for a realloc return value.(CVE-2019-17177)\r\n\r\n

libfreerdp/codec/region.c in FreeRDP through 1.1.x and 2.x through 2.0.0-rc4 has memory leaks because a supplied realloc pointer (i.e., the first argument to realloc) is also used for a realloc return value.

Updated freerdp packages fix security vulnerabilities:

Multiple memory leaks in libfreerdp/codec/region.c (CVE-2019-17177).

Memory leak in HuffmanTree_makeFromFrequencies (CVE-2019-17178).

This update for freerdp fixes the following issues:

• CVE-2019-17177: Fixed multiple memory leaks in libfreerdp/codec/region.c (bsc#1153163).
• CVE-2019-17178: Fixed a memory leak in HuffmanTree_makeFromFrequencies (bsc#1153164).

This update was imported from the SUSE:SLE-15:Update update project.

This update for freerdp fixes the following issues:

• CVE-2019-17177: Fixed multiple memory leaks in libfreerdp/codec/region.c (bsc#1153163).
• CVE-2019-17178: Fixed a memory leak in HuffmanTree_makeFromFrequencies (bsc#1153164).

This update was imported from the SUSE:SLE-15-SP1:Update update project.

These are all security issues fixed in the freerdp-2.4.0-2.1 package on the GA media of openSUSE Tumbleweed.

This update for freerdp fixes the following issues:

• CVE-2019-17177: Fixed multiple memory leaks in libfreerdp/codec/region.c (bsc#1153163).
• CVE-2019-17178: Fixed a memory leak in HuffmanTree_makeFromFrequencies (bsc#1153164).

This update for freerdp fixes the following issues:

• CVE-2019-17177: Fixed multiple memory leaks in libfreerdp/codec/region.c (bsc#1153163).
• CVE-2019-17178: Fixed a memory leak in HuffmanTree_makeFromFrequencies (bsc#1153164).

This update for freerdp fixes the following issues:

• CVE-2019-17177: Fixed multiple memory leaks in libfreerdp/codec/region.c (bsc#1153163).
• CVE-2019-17178: Fixed a memory leak in HuffmanTree_makeFromFrequencies (bsc#1153164).

It was discovered that FreeRDP incorrectly handled certain memory operations. A remote attacker could use this issue to cause FreeRDP to crash, resulting in a denial of service, or possibly exeucte arbitrary code.