CVE-2021-41159
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFreeRDP 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceFreeRDP clients prior to version 2.4.1 fail to validate input data when using gateway connections with the RPC transport (/gt:rpc). A malicious gateway can exploit this to write client memory out of bounds, leading to potential memory corruption and arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 35< 2.4.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed FreeRDP versionRun 'xfreerdp --version' or 'freerdp --version' from the command line, or query your package manager (e.g., 'rpm -q freerdp' on Fedora/RHEL, 'dpkg -l freerdp' on Debian/Ubuntu)Affected if The version returned is less than 2.4.1 or not shown (indicating an older unpatched build)
-
Locate FreeRDP connection commands or configsSearch for saved RDP connection files (commonly .rdp files in ~/.config/freerdp/ or user home directories) or check shell history for freerdp/xfreerdp commandsAffected if You find .rdp configuration files or saved connection commands that specify /gt:rpc or GatewayTransport:=RPC
-
Check active gateway connectionsReview any scripts, automation, or documentation that launch FreeRDP with the /gt:rpc gateway transport flag (for example: 'xfreerdp /v:server /g:gateway /gt:rpc ...')Affected if The gateway transport is explicitly set to RPC (/gt:rpc) in any connection configuration or command line
-
Verify client is exposed to gatewayConfirm whether the FreeRDP client is routinely used to connect through Remote Desktop Gateway (RD Gateway) using the RPC transportAffected if You connect through a Remote Desktop Gateway using /gt:rpc and the gateway could be controlled by an untrusted party
You are affected if FreeRDP version is below 2.4.1 AND you use /gt:rpc gateway transport connections; without the RPC gateway transport, this specific flaw does not apply.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.4.1
Update FreeRDP to version 2.4.1 or later. If immediate updating is not possible, use /gt:http instead of /gt:rpc for gateway connections, or bypass the gateway entirely with a direct connection.
FreeRDP 2.4.1 or later
- Upgrade FreeRDP to version 2.4.1 or later to remediate the out-of-bounds write vulnerability
- Alternatively, if upgrading is not possible, configure the client to use /gt:http gateway type instead of /gt:rpc, or use a direct connection without a gateway
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-41159 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-41159 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data