Vulnerability in freerdp2 (DEBIAN-CVE-2021-41159)
Summary
Vulnerability in freerdp2 (DEBIAN-CVE-2021-41159). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.4.1+dfsg1-1 or later.
Original description
The description as published by the source.
FreeRDP 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.
Source: OSV.dev (Open Source Vulnerabilities) OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as DEBIAN-CVE-2021-41159 has been found in freerdp2.
Successful exploitation can lead to full system takeover.
What to do: upgrade freerdp2 to 2.4.1+dfsg1-1 or later.
If unsure, ask your IT team or search "freerdp2 DEBIAN-CVE-2021-41159" on the vendor's site.
DEBIAN-CVE-2021-41159 (freerdp2)
Attack vector: remote (network-reachable) / unauthenticated
Patched: 2.4.1+dfsg1-1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in freerdp2.
Check the vendor advisory for the affected versions of freerdp2.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 2.4.1+dfsg1-1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'freerdp2' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'freerdp2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
freerdp2を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade freerdp2 to 2.4.1+dfsg1-1ステージング環境で 2.4.1+dfsg1-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory security-tracker.debian.org