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. References: https://github.com/FreeRDP/FreeRDP/issues/6006 https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-hx48-wmmm-mr5q Upstream commit: https://github.com/FreeRDP/FreeRDP/commit/ed53cd148f43cbab905eaa0f5308c2bf3c48cc37
Created freerdp tracking bugs for this issue: Affects: epel-all [bug 1835406] Affects: fedora-all [bug 1835404] Created freerdp1.2 tracking bugs for this issue: Affects: fedora-all [bug 1835405]
Technical Summary: update_read_synchronize() does a fixed seek of +2 bytes in the stream buffer. It does this seek without first checking whether it will overflow past the end of the stream buffer. Due to this, calling update_read_synchronize() at the end of the buffer will seek the stream buffer pointer to a position such that the next read of the stream buffer will be out-of-bounds.
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2020:4031 https://access.redhat.com/errata/RHSA-2020:4031
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2020-11046
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2020:4647 https://access.redhat.com/errata/RHSA-2020:4647