freerdp2 - Debian Package Tracker

general

source: freerdp2 (main)
version: 2.7.0+dfsg1-1
maintainer: Debian Remote Maintainers (archive) (DMD)
uploaders: Mike Gabriel [DMD] – Bernhard Miklautz [DMD]
arch: any
std-ver: 4.6.0
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-bpo: 2.0.0~git20190204.1.2693389a+dfsg1-1~bpo9+1
oldstable: 2.0.0~git20190204.1.2693389a+dfsg1-1+deb10u2
old-bpo: 2.3.0+dfsg1-1~bpo10+1
stable: 2.3.0+dfsg1-2
stable-bpo: 2.7.0+dfsg1-1~bpo11+1
testing: 2.7.0+dfsg1-1
unstable: 2.7.0+dfsg1-1

versioned links

2.0.0~git20190204.1.2693389a+dfsg1-1~bpo9+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.0.0~git20190204.1.2693389a+dfsg1-1+deb10u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.3.0+dfsg1-1~bpo10+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.3.0+dfsg1-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.7.0+dfsg1-1~bpo11+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.7.0+dfsg1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

freerdp2-dev
freerdp2-shadow-x11
freerdp2-wayland (4 bugs: 0, 4, 0, 0)
freerdp2-x11
libfreerdp-client2-2
libfreerdp-server2-2
libfreerdp-shadow-subsystem2-2
libfreerdp-shadow2-2
libfreerdp2-2
libuwac0-0
libuwac0-dev
libwinpr-tools2-2
libwinpr2-2
libwinpr2-dev
winpr-utils

action needed

lintian reports 1 warning high

Lintian reports 1 warning about this package. You should make the package lintian clean getting rid of them.

Created: 2020-07-29 Last update: 2022-01-01 04:32

Does not build reproducibly during testing normal

A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!

Created: 2022-05-03 Last update: 2022-06-29 20:11

Depends on packages which need a new maintainer normal

The packages that freerdp2 depends on which need a new maintainer are:

libgsm (#1009975)
- Build-Depends: libgsm1-dev

Created: 2022-04-21 Last update: 2022-06-29 18:07

38 low-priority security issues in buster low

There are 38 open security issues in buster.

38 issues left for the package maintainer to handle:

CVE-2020-4030: (needs triaging) In FreeRDP before version 2.1.2, there is an out of bounds read in TrioParse. Logging might bypass string length checks due to an integer overflow. This is fixed in version 2.1.2.
CVE-2020-4031: (needs triaging) In FreeRDP before version 2.1.2, there is a use-after-free in gdi_SelectObject. All FreeRDP clients using compatibility mode with /relax-order-checks are affected. This is fixed in version 2.1.2.
CVE-2020-4032: (needs triaging) In FreeRDP before version 2.1.2, there is an integer casting vulnerability in update_recv_secondary_order. All clients with +glyph-cache /relax-order-checks are affected. This is fixed in version 2.1.2.
CVE-2020-4033: (needs triaging) In FreeRDP before version 2.1.2, there is an out of bounds read in RLEDECOMPRESS. All FreeRDP based clients with sessions with color depth < 32 are affected. This is fixed in version 2.1.2.
CVE-2020-11017: (needs triaging) In FreeRDP less than or equal to 2.0.0, by providing manipulated input a malicious client can create a double free condition and crash the server. This is fixed in version 2.1.0.
CVE-2020-11018: (needs triaging) In FreeRDP less than or equal to 2.0.0, a possible resource exhaustion vulnerability can be performed. Malicious clients could trigger out of bound reads causing memory allocation with random size. This has been fixed in 2.1.0.
CVE-2020-11019: (needs triaging) In FreeRDP less than or equal to 2.0.0, when running with logger set to "WLOG_TRACE", a possible crash of application could occur due to a read of an invalid array index. Data could be printed as string to local terminal. This has been fixed in 2.1.0.
CVE-2020-11038: (needs triaging) In FreeRDP less than or equal to 2.0.0, an Integer Overflow to Buffer Overflow exists. When using /video redirection, a manipulated server can instruct the client to allocate a buffer with a smaller size than requested due to an integer overflow in size calculation. With later messages, the server can manipulate the client to write data out of bound to the previously allocated buffer. This has been patched in 2.1.0.
CVE-2020-11039: (needs triaging) In FreeRDP less than or equal to 2.0.0, when using a manipulated server with USB redirection enabled (nearly) arbitrary memory can be read and written due to integer overflows in length checks. This has been patched in 2.1.0.
CVE-2020-11040: (needs triaging) In FreeRDP less than or equal to 2.0.0, there is an out-of-bound data read from memory in clear_decompress_subcode_rlex, visualized on screen as color. This has been patched in 2.1.0.
CVE-2020-11041: (needs triaging) In FreeRDP less than or equal to 2.0.0, an outside controlled array index is used unchecked for data used as configuration for sound backend (alsa, oss, pulse, ...). The most likely outcome is a crash of the client instance followed by no or distorted sound or a session disconnect. If a user cannot upgrade to the patched version, a workaround is to disable sound for the session. This has been patched in 2.1.0.
CVE-2020-11042: (needs triaging) 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-11043: (needs triaging) In FreeRDP less than or equal to 2.0.0, there is an out-of-bounds read in rfx_process_message_tileset. Invalid data fed to RFX decoder results in garbage on screen (as colors). This has been patched in 2.1.0.
CVE-2020-11044: (needs triaging) 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-11045: (needs triaging) 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-11046: (needs triaging) In FreeRDP after 1.0 and before 2.0.0, there is a stream out-of-bounds seek in update_read_synchronize that could lead to a later out-of-bounds read.
CVE-2020-11047: (needs triaging) In FreeRDP after 1.1 and before 2.0.0, there is an out-of-bounds read in autodetect_recv_bandwidth_measure_results. A malicious server can extract up to 8 bytes of client memory with a manipulated message by providing a short input and reading the measurement result data. This has been patched in 2.0.0.
CVE-2020-11048: (needs triaging) In FreeRDP after 1.0 and before 2.0.0, there is an out-of-bounds read. It only allows to abort a session. No data extraction is possible. This has been fixed in 2.0.0.
CVE-2020-11049: (needs triaging) In FreeRDP after 1.1 and before 2.0.0, there is an out-of-bound read of client memory that is then passed on to the protocol parser. This has been patched in 2.0.0.
CVE-2020-11058: (needs triaging) In FreeRDP after 1.1 and before 2.0.0, a stream out-of-bounds seek in rdp_read_font_capability_set could lead to a later out-of-bounds read. As a result, a manipulated client or server might force a disconnect due to an invalid data read. This has been fixed in 2.0.0.
CVE-2020-11085: (needs triaging) In FreeRDP before 2.1.0, there is an out-of-bounds read in cliprdr_read_format_list. Clipboard format data read (by client or server) might read data out-of-bounds. This has been fixed in 2.1.0.
CVE-2020-11086: (needs triaging) In FreeRDP less than or equal to 2.0.0, there is an out-of-bound read in ntlm_read_ntlm_v2_client_challenge that reads up to 28 bytes out-of-bound to an internal structure. This has been fixed in 2.1.0.
CVE-2020-11087: (needs triaging) In FreeRDP less than or equal to 2.0.0, there is an out-of-bound read in ntlm_read_AuthenticateMessage. This has been fixed in 2.1.0.
CVE-2020-11088: (needs triaging) In FreeRDP less than or equal to 2.0.0, there is an out-of-bound read in ntlm_read_NegotiateMessage. This has been fixed in 2.1.0.
CVE-2020-11089: (needs triaging) In FreeRDP before 2.1.0, there is an out-of-bound read in irp functions (parallel_process_irp_create, serial_process_irp_create, drive_process_irp_write, printer_process_irp_write, rdpei_recv_pdu, serial_process_irp_write). This has been fixed in 2.1.0.
CVE-2020-11095: (needs triaging) 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-11096: (needs triaging) In FreeRDP before version 2.1.2, there is a global OOB read in update_read_cache_bitmap_v3_order. As a workaround, one can disable bitmap cache with -bitmap-cache (default). This is fixed in version 2.1.2.
CVE-2020-11097: (needs triaging) In FreeRDP before version 2.1.2, an out of bounds read 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-11098: (needs triaging) In FreeRDP before version 2.1.2, there is an out-of-bound read in glyph_cache_put. This affects all FreeRDP clients with `+glyph-cache` option enabled This is fixed in version 2.1.2.
CVE-2020-11099: (needs triaging) In FreeRDP before version 2.1.2, there is an out of bounds read in license_read_new_or_upgrade_license_packet. A manipulated license packet can lead to out of bound reads to an internal buffer. This is fixed in version 2.1.2.
CVE-2020-13396: (needs triaging) An issue was discovered in FreeRDP before 2.1.1. An out-of-bounds (OOB) read vulnerability has been detected in ntlm_read_ChallengeMessage in winpr/libwinpr/sspi/NTLM/ntlm_message.c.
CVE-2020-13397: (needs triaging) An issue was discovered in FreeRDP before 2.1.1. An out-of-bounds (OOB) read vulnerability has been detected in security_fips_decrypt in libfreerdp/core/security.c due to an uninitialized value.
CVE-2020-13398: (needs triaging) An issue was discovered in FreeRDP before 2.1.1. An out-of-bounds (OOB) write vulnerability has been detected in crypto_rsa_common in libfreerdp/crypto/crypto.c.
CVE-2020-15103: (needs triaging) In FreeRDP less than or equal to 2.1.2, an integer overflow exists due to missing input sanitation in rdpegfx channel. All FreeRDP clients are affected. The input rectangles from the server are not checked against local surface coordinates and blindly accepted. A malicious server can send data that will crash the client later on (invalid length arguments to a `memcpy`) This has been fixed in 2.2.0. As a workaround, stop using command line arguments /gfx, /gfx-h264 and /network:auto
CVE-2021-41159: (needs triaging) FreeRDP is a free implementation of the Remote Desktop Protocol (RDP), released under the Apache license. All FreeRDP clients prior to version 2.4.1 using gateway connections (`/gt:rpc`) fail to validate input data. A malicious gateway might allow client memory to be written out of bounds. This issue has been resolved in version 2.4.1. If you are unable to update then use `/gt:http` rather than /gt:rdp connections if possible or use a direct connection without a gateway.
CVE-2021-41160: (needs triaging) FreeRDP is a free implementation of the Remote Desktop Protocol (RDP), released under the Apache license. In affected versions a malicious server might trigger out of bound writes in a connected client. Connections using GDI or SurfaceCommands to send graphics updates to the client might send `0` width/height or out of bound rectangles to trigger out of bound writes. With `0` width or heigth the memory allocation will be `0` but the missing bounds checks allow writing to the pointer at this (not allocated) region. This issue has been patched in FreeRDP 2.4.1.
CVE-2022-24882: (needs triaging) FreeRDP is a free implementation of the Remote Desktop Protocol (RDP). In versions prior to 2.7.0, NT LAN Manager (NTLM) authentication does not properly abort when someone provides and empty password value. This issue affects FreeRDP based RDP Server implementations. RDP clients are not affected. The vulnerability is patched in FreeRDP 2.7.0. There are currently no known workarounds.
CVE-2022-24883: (needs triaging) FreeRDP is a free implementation of the Remote Desktop Protocol (RDP). Prior to version 2.7.0, server side authentication against a `SAM` file might be successful for invalid credentials if the server has configured an invalid `SAM` file path. FreeRDP based clients are not affected. RDP server implementations using FreeRDP to authenticate against a `SAM` file are affected. Version 2.7.0 contains a fix for this issue. As a workaround, use custom authentication via `HashCallback` and/or ensure the `SAM` database path configured is valid and the application has file handles left.

You can find information about how to handle these issues in the security team's documentation.

Created: 2021-02-19 Last update: 2022-05-30 18:05

4 low-priority security issues in bullseye low

There are 4 open security issues in bullseye.

4 issues left for the package maintainer to handle:

CVE-2021-41159: (needs triaging) FreeRDP is a free implementation of the Remote Desktop Protocol (RDP), released under the Apache license. All FreeRDP clients prior to version 2.4.1 using gateway connections (`/gt:rpc`) fail to validate input data. A malicious gateway might allow client memory to be written out of bounds. This issue has been resolved in version 2.4.1. If you are unable to update then use `/gt:http` rather than /gt:rdp connections if possible or use a direct connection without a gateway.
CVE-2021-41160: (needs triaging) FreeRDP is a free implementation of the Remote Desktop Protocol (RDP), released under the Apache license. In affected versions a malicious server might trigger out of bound writes in a connected client. Connections using GDI or SurfaceCommands to send graphics updates to the client might send `0` width/height or out of bound rectangles to trigger out of bound writes. With `0` width or heigth the memory allocation will be `0` but the missing bounds checks allow writing to the pointer at this (not allocated) region. This issue has been patched in FreeRDP 2.4.1.
CVE-2022-24882: (needs triaging) FreeRDP is a free implementation of the Remote Desktop Protocol (RDP). In versions prior to 2.7.0, NT LAN Manager (NTLM) authentication does not properly abort when someone provides and empty password value. This issue affects FreeRDP based RDP Server implementations. RDP clients are not affected. The vulnerability is patched in FreeRDP 2.7.0. There are currently no known workarounds.
CVE-2022-24883: (needs triaging) FreeRDP is a free implementation of the Remote Desktop Protocol (RDP). Prior to version 2.7.0, server side authentication against a `SAM` file might be successful for invalid credentials if the server has configured an invalid `SAM` file path. FreeRDP based clients are not affected. RDP server implementations using FreeRDP to authenticate against a `SAM` file are affected. Version 2.7.0 contains a fix for this issue. As a workaround, use custom authentication via `HashCallback` and/or ensure the `SAM` database path configured is valid and the application has file handles left.

You can find information about how to handle these issues in the security team's documentation.

Created: 2021-10-21 Last update: 2022-05-30 18:05

Build log checks report 2 warnings low

Build log checks report 2 warnings

Created: 2017-10-26 Last update: 2020-08-25 10:38

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.6.1 instead of 4.6.0).

Created: 2022-05-11 Last update: 2022-05-11 23:25

news

[rss feed]

[2022-06-22] Accepted freerdp2 2.7.0+dfsg1-1~bpo11+1 (source) into bullseye-backports (Michael Tokarev)
[2022-05-03] freerdp2 2.7.0+dfsg1-1 MIGRATED to testing (Debian testing watch)
[2022-04-27] Accepted freerdp2 2.7.0+dfsg1-1 (source) into unstable (Mike Gabriel)
[2022-04-13] Accepted freerdp2 2.6.1+dfsg1-3~bpo11+1 (source amd64) into bullseye-backports, bullseye-backports (Debian FTP Masters) (signed by: Mike Gabriel)
[2022-03-14] Accepted freerdp2 2.3.0+dfsg1-2+deb11u1 (source) into proposed-updates->stable-new, proposed-updates (Debian FTP Masters) (signed by: Mike Gabriel)
[2022-03-13] freerdp2 2.6.1+dfsg1-3 MIGRATED to testing (Debian testing watch)
[2022-03-08] Accepted freerdp2 2.6.1+dfsg1-3 (source) into unstable (Mike Gabriel)
[2022-03-08] Accepted freerdp2 2.6.1+dfsg1-2 (source) into unstable (Mike Gabriel)
[2022-03-08] Accepted freerdp2 2.6.1+dfsg1-1 (source) into unstable (Mike Gabriel)
[2022-03-04] freerdp2 2.6.0+dfsg1-1 MIGRATED to testing (Debian testing watch)
[2022-02-26] Accepted freerdp2 2.6.0+dfsg1-1 (source) into unstable (Mike Gabriel)
[2022-02-19] freerdp2 2.5.0+dfsg1-1 MIGRATED to testing (Debian testing watch)
[2022-02-14] Accepted freerdp2 2.5.0+dfsg1-1 (source) into unstable (Mike Gabriel)
[2021-12-15] freerdp2 2.4.1+dfsg1-1 MIGRATED to testing (Debian testing watch)
[2021-12-09] Accepted freerdp2 2.4.1+dfsg1-1 (source) into unstable (Mike Gabriel)
[2021-05-24] freerdp2 2.3.0+dfsg1-2 MIGRATED to testing (Debian testing watch)
[2021-05-16] Accepted freerdp2 2.3.0+dfsg1-2 (source) into unstable (Mike Gabriel)
[2021-04-20] Accepted freerdp2 2.3.0+dfsg1-1~bpo10+1 (source) into buster-backports->backports-policy, buster-backports (Debian FTP Masters) (signed by: Christoph Martin)
[2021-03-08] freerdp2 2.3.0+dfsg1-1 MIGRATED to testing (Debian testing watch)
[2021-02-25] Accepted freerdp2 2.3.0+dfsg1-1 (source) into unstable (Mike Gabriel)
[2020-08-31] Accepted freerdp2 2.2.0+dfsg1-1~bpo10+1 (source) into buster-backports (Christoph Martin)
[2020-08-30] freerdp2 2.2.0+dfsg1-1 MIGRATED to testing (Debian testing watch)
[2020-08-25] Accepted freerdp2 2.2.0+dfsg1-1 (source) into unstable (Mike Gabriel)
[2020-07-07] freerdp2 2.1.2+dfsg1-2 MIGRATED to testing (Debian testing watch)
[2020-07-02] Accepted freerdp2 2.1.2+dfsg1-2 (source) into unstable (Mike Gabriel)
[2020-06-29] Accepted freerdp2 2.1.2+dfsg1-1 (source) into unstable (Mike Gabriel)
[2020-06-13] Accepted freerdp2 2.0.0~git20190204.1.2693389a+dfsg1-1+deb10u2 (source) into proposed-updates->stable-new, proposed-updates (Debian FTP Masters) (signed by: Mike Gabriel)
[2020-06-02] freerdp2 2.1.1+dfsg1-1 MIGRATED to testing (Debian testing watch)
[2020-05-27] Accepted freerdp2 2.1.1+dfsg1-1 (source) into unstable (Mike Gabriel)
[2020-04-14] Accepted freerdp2 2.0.0~git20190204.1.2693389a+dfsg1-2~bpo10+1 (source amd64) into buster-backports, buster-backports (Debian FTP Masters) (signed by: Christoph Martin)

bugs [bug history graph]

all: 5
RC: 0
I&N: 4
M&W: 0
F&P: 1
patch: 0

links

homepage
lintian (0, 1)
buildd: logs, checks, clang, reproducibility, cross
popcon
browse source code
edit tags
other distros
security tracker

ubuntu

[Information about Ubuntu for Debian Developers]

version: 2.7.0+dfsg1-1ubuntu1
13 bugs
patches for 2.7.0+dfsg1-1ubuntu1