Client crash via unchecked secondary-order length
Published May 15, 2020 · Updated Aug 4, 2024
Out-of-bounds read in FreeRDP after 1.1 through 2.0.0-rc4 allows remote authenticated users to crash the client with a crafted order. The update_recv_secondary_order parser advances the stream pointer using orderLength without verifying that the declared secondary-order span remains inside the received buffer. A malicious RDP server must supply the order during a session; the bounded reported consequence is a client crash.
Summary
What happened
Out-of-bounds read in FreeRDP after 1.1 through 2.0.0-rc4 allows remote authenticated users to crash the client with a crafted order. The update_recv_secondary_order parser advances the stream pointer using orderLength without verifying that the declared secondary-order span remains inside the received buffer. A malicious RDP server must supply the order during a session; the bounded reported consequence is a client crash.
The record
- CVE
- CVE-2020-11526
- Published
- May 15, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190, CWE-125
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 15, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- FreeRDP proof-of-concept analysisproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo