Vulnerability in FreeRDP greater than (CVE-2020-11042)

Summary

Vulnerability in FreeRDP greater than (CVE-2020-11042). Confidential information can be exposed externally. Mitigation: upgrade to 2.0.0 or later.

Original description

The description as published by the source.

In FreeRDP greater than 1.1 and before 2.0.0, there is an out-of-bounds read in update_read_icon_info. It allows reading a attacker-defined amount of client memory (32bit unsigned -> 4GB) to an intermediate buffer. This can be used to crash the client or store information for later retrieval. This has been patched in 2.0.0.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory 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 CVE-2020-11042 has been found in FreeRDP greater than.
Confidential information can be exposed externally.
What to do: upgrade FreeRDP greater than to 2.0.0 or later.
If unsure, ask your IT team or search "FreeRDP greater than CVE-2020-11042" on the vendor's site.

CVE-2020-11042 (FreeRDP greater than)
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.0.0 — 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.

❓ What is the problem

A vulnerability (unclassified) exists in FreeRDP greater than.

📍 Affected scope

Check the vendor advisory for the affected versions of FreeRDP greater than.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 2.0.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで FreeRDP greater than を使っているサービスとバージョンを洗い出す。
2
Apply patch patch
```
Upgrade FreeRDP greater than to 2.0.0
```
ステージング環境で 2.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2020-11042 freerdp2 Fixed in: 2.1.1+dfsg1-1

References

advisory github.com
advisory lists.debian.org
advisory usn.ubuntu.com
advisory usn.ubuntu.com
patch github.com
report github.com
web lists.debian.org