An out-of-bounds read vulnerability exists in FreeRDP before version 2.1.2 due to improper bounds checking when accessing the static array PRIMARY_DRAWING_ORDER_FIELD_BYTES. This flaw allows the software to read memory outside the intended buffer, potentially exposing sensitive information or causing a crash.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept (PoC) exploit for CVE-2020-11097, a vulnerability in FreeRDP. The main file, 'test.py', is a Python script that implements a malicious NTLM authentication server. When run, it listens on TCP port 3389 (the standard RDP port) and waits for incoming connections from RDP clients. Upon receiving an NTLM negotiation from a client, the script responds with a specially crafted NTLM Type 2 Challenge message containing a malformed AV_PAIR section designed to trigger an out-of-bounds read in the FreeRDP client, causing it to crash. The README provides instructions for running the server and connecting to it using the 'xfreerdp' client. The exploit demonstrates the vulnerability but does not provide a weaponized or post-exploitation payload. The repository is structured simply, with a single exploit script and a README file.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.