نسخههای متأثر
- نسخههای متأثر
- نامشخص
- نسخهٔ اصلاحشده
- اعلام نشده
بهرهبرداری
شرح آسیبپذیری
FreeRDP 3.0.0 before 3.32.0 allows HTTP header injection in its proxy because a lone LF in the target portion of a routing token (Cookie: msts=) is not rejected and is written by http_proxy_connect into the CONNECT request line and Host header. A remote unauthenticated RDP client connecting to a proxy using FixedTarget=false and an upstream HTTP proxy can alter HTTP request/header framing at that upstream proxy.
A flaw was found in FreeRDP. A remote, unauthenticated attacker can perform HTTP header injection by submitting a routing token containing an unvalidated line feed character to a FreeRDP proxy configured with dynamic targets and an upstream Hypertext Transfer Protocol (HTTP) proxy. This vulnerability allows the attacker to alter HTTP request framing and inject custom headers into outbound proxy requests, potentially compromising the integrity of communications handled by the upstream proxy.

