Bug 1661640 (CVE-2018-1000852) - CVE-2018-1000852 freerdp: out of bounds read in drdynvc_process_capability_request
Summary: CVE-2018-1000852 freerdp: out of bounds read in drdynvc_process_capability_re...
Alias: CVE-2018-1000852
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1661641 1661642 1661643 1663085 1663086
Blocks: 1661644
TreeView+ depends on / blocked
Reported: 2018-12-21 20:31 UTC by Laura Pardo
Modified: 2019-09-29 15:04 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-08-06 13:21:14 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:2157 0 None None None 2019-08-06 12:22:36 UTC

Description Laura Pardo 2018-12-21 20:31:53 UTC
FreeRDP 2.0.0-rc3 contains an out of bounds read vulnerability in drdynvc_process_capability_request function in channels/drdynvc/client/drdynvc_main.c file. To exploit this RDPClient must connect to the rdp server with the echo option. This can lead to a two-byte outbound reading from the client memory.


Upstream Patch:

Comment 1 Laura Pardo 2018-12-21 20:32:24 UTC
Created freerdp tracking bugs for this issue:

Affects: epel-6 [bug 1661641]
Affects: fedora-28 [bug 1661642]

Created freerdp1.2 tracking bugs for this issue:

Affects: fedora-all [bug 1661643]

Comment 2 Doran Moppert 2019-01-03 05:04:09 UTC
The same memory disclosure seems to be present in freerdp-1.0.2, though it's contained entirely in the drdynvc_process_capability_request function.  There does not seem to be any Availability impact, as it's a small read beyond the end of a heap buffer.

Comment 5 errata-xmlrpc 2019-08-06 12:22:36 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2019:2157 https://access.redhat.com/errata/RHSA-2019:2157

Comment 6 Product Security DevOps Team 2019-08-06 13:21:14 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):


Note You need to log in before you can comment on or make changes to this bug.