Vulnerability in freerdp2 (DEBIAN-CVE-2026-67300)

Summary

Vulnerability in freerdp2 (DEBIAN-CVE-2026-67300). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.29.0+dfsg-1 or later.

Original description

The description as published by the source.

FreeRDP before 3.29.0 contains client-side heap use-after-free vulnerabilities in the async update message proxy for RAIL WINDOW_STATE_ORDER and NOTIFY_ICON_STATE_ORDER when AsyncUpdate is enabled. When a malicious or compromised RDP server sends crafted update orders, the message proxy shallow-copies structures containing nested parser-owned pointers (e.g., titleInfo.string, windowRects, visibilityRects, icon buffers). The parser frees those nested buffers after the callback returns, so the queued async message later dispatches stale pointers, potentially causing memory corruption or a client crash.

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-2026-67300 has been found in freerdp2.
Risk of unauthorized operations or information disclosure.
What to do: upgrade freerdp2 to 3.29.0+dfsg-1 or later.
If unsure, ask your IT team or search "freerdp2 DEBIAN-CVE-2026-67300" on the vendor's site.

DEBIAN-CVE-2026-67300 (freerdp2)
Patched: 3.29.0+dfsg-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.

❓ What is the problem

A vulnerability (unclassified) exists in freerdp2.

📍 Affected scope

Check the vendor advisory for the affected versions of freerdp2.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.29.0+dfsg-1.

🛡️ 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. 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

1
Identify exposure identify
```
grep -r 'freerdp2' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で freerdp2 を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade freerdp2 to 3.29.0+dfsg-1
```
ステージング環境で 3.29.0+dfsg-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:12 freerdp2

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Debian:13 freerdp3

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Debian:14 freerdp3

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.29.0+dfsg-1"}]}]

References

advisory security-tracker.debian.org