RHSA-2026:98598
Vulnerability from csaf_redhat - Published: 2026-11-11 13:48 - Updated: 2026-11-13 03:54A flaw was found in FreeRDP. This vulnerability allows a remote attacker with low privileges to disclose sensitive information from the server or proxy process memory to a downstream client. This occurs because certain functions responsible for writing Save Session Info Protocol Data Units (PDUs) use Stream_Seek instead of Stream_Zero for reserved padding fields, leading to the transmission of uninitialized heap memory that may contain cleartext credentials from previous sessions.
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: AppStream-10.3.Z:freerdp-2:3.32.2-1.el10_3.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-2:3.32.2-1.el10_3.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-2:3.32.2-1.el10_3.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-2:3.32.2-1.el10_3.src | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-2:3.32.2-1.el10_3.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-debuginfo-2:3.32.2-1.el10_3.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-debuginfo-2:3.32.2-1.el10_3.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-debuginfo-2:3.32.2-1.el10_3.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-debuginfo-2:3.32.2-1.el10_3.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-debugsource-2:3.32.2-1.el10_3.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-debugsource-2:3.32.2-1.el10_3.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-debugsource-2:3.32.2-1.el10_3.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-debugsource-2:3.32.2-1.el10_3.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-libs-2:3.32.2-1.el10_3.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-libs-2:3.32.2-1.el10_3.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-libs-2:3.32.2-1.el10_3.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-libs-2:3.32.2-1.el10_3.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-libs-debuginfo-2:3.32.2-1.el10_3.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-libs-debuginfo-2:3.32.2-1.el10_3.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-libs-debuginfo-2:3.32.2-1.el10_3.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-libs-debuginfo-2:3.32.2-1.el10_3.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-server-debuginfo-2:3.32.2-1.el10_3.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-server-debuginfo-2:3.32.2-1.el10_3.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-server-debuginfo-2:3.32.2-1.el10_3.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:freerdp-server-debuginfo-2:3.32.2-1.el10_3.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:libwinpr-2:3.32.2-1.el10_3.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:libwinpr-2:3.32.2-1.el10_3.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:libwinpr-2:3.32.2-1.el10_3.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:libwinpr-2:3.32.2-1.el10_3.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:libwinpr-debuginfo-2:3.32.2-1.el10_3.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:libwinpr-debuginfo-2:3.32.2-1.el10_3.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:libwinpr-debuginfo-2:3.32.2-1.el10_3.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.3.Z:libwinpr-debuginfo-2:3.32.2-1.el10_3.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-debuginfo-2:3.32.2-1.el10_3.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-debuginfo-2:3.32.2-1.el10_3.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-debuginfo-2:3.32.2-1.el10_3.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-debuginfo-2:3.32.2-1.el10_3.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-debugsource-2:3.32.2-1.el10_3.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-debugsource-2:3.32.2-1.el10_3.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-debugsource-2:3.32.2-1.el10_3.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-debugsource-2:3.32.2-1.el10_3.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-devel-2:3.32.2-1.el10_3.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-devel-2:3.32.2-1.el10_3.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-devel-2:3.32.2-1.el10_3.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-devel-2:3.32.2-1.el10_3.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-libs-debuginfo-2:3.32.2-1.el10_3.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-libs-debuginfo-2:3.32.2-1.el10_3.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-libs-debuginfo-2:3.32.2-1.el10_3.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-libs-debuginfo-2:3.32.2-1.el10_3.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-server-2:3.32.2-1.el10_3.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-server-2:3.32.2-1.el10_3.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-server-2:3.32.2-1.el10_3.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-server-2:3.32.2-1.el10_3.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-server-debuginfo-2:3.32.2-1.el10_3.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-server-debuginfo-2:3.32.2-1.el10_3.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-server-debuginfo-2:3.32.2-1.el10_3.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:freerdp-server-debuginfo-2:3.32.2-1.el10_3.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:libwinpr-debuginfo-2:3.32.2-1.el10_3.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:libwinpr-debuginfo-2:3.32.2-1.el10_3.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:libwinpr-debuginfo-2:3.32.2-1.el10_3.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:libwinpr-debuginfo-2:3.32.2-1.el10_3.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:libwinpr-devel-2:3.32.2-1.el10_3.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:libwinpr-devel-2:3.32.2-1.el10_3.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:libwinpr-devel-2:3.32.2-1.el10_3.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.3.Z:libwinpr-devel-2:3.32.2-1.el10_3.x86_64 | — |
Vendor Fix
fix
Workaround
|
A flaw was found in FreeRDP. Authenticated RDP clients can exploit an out-of-bounds read vulnerability in smartcard response decoders. This occurs because the decoders fail to validate the length of Answer to Reset (ATR) fields against fixed inline arrays. By sending oversized ATR lengths, an attacker can trigger reads past memory objects, leading to process termination and a denial of service.
A flaw was found in FreeRDP. This information disclosure vulnerability exists in the RDPGFX server's ResetGraphics Protocol Data Unit (PDU) serializer. It fails to properly initialize padding bytes, allowing a remote attacker to receive uninitialized heap memory. This can lead to the disclosure of sensitive data, including live pointers and GLib function addresses, which could defeat Address Space Layout Randomization (ASLR) and reveal the GLib module's base address.
A flaw was found in FreeRDP server. This use-after-free vulnerability exists in the DRDYNVC parser, where a channel pointer is dereferenced after its synchronization lock has been released. An authenticated client can exploit this by racing AUDIN channel closure messages against DRDYNVC data parsing, leading to memory corruption. This could potentially result in arbitrary code execution or a denial of service.
A flaw was found in FreeRDP. An authenticated client can send specially crafted, oversized messages to the server when the CHANNEL_OPTION_SHOW_PROTOCOL feature is active. This can cause a buffer underflow, leading to corruption of memory and potentially allowing an attacker to execute malicious code on the server.
A flaw was found in FreeRDP server. This vulnerability allows unauthenticated attackers to bypass server policies that disable Remote Desktop Services over Transport Layer Security (RDSTLS) connections. By sending incompatible protocol requests and then completing a TLS handshake, attackers can establish RDSTLS connections, thereby circumventing pre-authentication transport restrictions.
A flaw was found in FreeRDP, where an out-of-bounds read vulnerability exists in the rdpdr_dump_packet function. This is due to a 32-bit unsigned integer wraparound during buffer bounds validation. A malicious RDP server can send a specially crafted RDPDR packet, bypassing security checks and causing the client to read memory beyond the intended buffer. This can result in client crashes, leading to a denial of service, or the disclosure of sensitive heap memory information in logs. Exploitation requires the client to have WLOG_TRACE-level logging enabled.
A flaw was found in FreeRDP. A malicious Remote Desktop Protocol (RDP) server can send a specially crafted USB redirection message to the urbdrc client channel. This can trigger an out-of-bounds write, leading to a denial of service (DoS) for the client when verbose asserts are enabled.
A flaw was found in FreeRDP. A malicious RDP (Remote Desktop Protocol) server or a man-in-the-middle attacker could exploit a heap buffer overflow vulnerability during connection negotiation, prior to authentication. By sending a specially crafted Server Redirection PDU (Protocol Data Unit) with an oversized LB_LOAD_BALANCE_INFO field, an attacker could cause a denial of service or heap corruption on the client system.
A flaw was found in FreeRDP. A malicious Remote Desktop Protocol (RDP) server can trigger a null pointer dereference in the `gdi_surface_bits` function by sending a specially crafted Surface Bits command that claims to use the NSCodec codec ID. This vulnerability exists even when the NSCodec is disabled in the client. Successful exploitation allows a remote attacker to cause a FreeRDP client to crash, leading to a denial of service.
A flaw was found in FreeRDP. A malicious Remote Desktop Protocol (RDP) server can exploit an out-of-bounds read vulnerability in the URBDRC (USB device redirection) channel. By sending a specially crafted message, the server can cause the FreeRDP client to read beyond its allocated memory, leading to a client crash and a denial of service.
A flaw was found in FreeRDP. A remote attacker can exploit a buffer over-read vulnerability within the RPC (Remote Procedure Call) gateway transport parser by sending a malicious BIND_ACK Protocol Data Unit (PDU) with a truncated result entry. This can lead to a process abort, resulting in a Denial of Service (DoS).
A flaw was found in FreeRDP. A remote attacker, specifically a malicious RD Gateway peer, could send a crafted WebSocket Ping frame with an extended payload length. This action triggers an an integer overflow in the `Stream_EnsureRemainingCapacity` function, leading to an integer wraparound and a double free vulnerability. Successful exploitation results in a denial of service, causing the FreeRDP client to crash during connection.
A flaw was found in FreeRDP. An uninitialized heap memory disclosure vulnerability exists in the urbdrc USB redirection channel. A malicious Remote Desktop Protocol (RDP) server can exploit this by inducing failing USB transfers, allowing it to read uninitialized heap memory from the client. This information disclosure can defeat Address Space Layout Randomization (ASLR), potentially enabling remote code execution when chained with other memory corruption vulnerabilities.
A flaw was found in FreeRDP. A malicious Remote Desktop Protocol (RDP) server can exploit a heap-based buffer overflow vulnerability in the `nego_send_negotiation_request` function. By sending a specially crafted Server Redirection PDU message with an attacker-controlled `LoadBalanceInfo` field, the server can write an arbitrary-length field into a fixed-size buffer without proper validation. This can lead to a denial of service (client crash) or, when chained with a memory disclosure vulnerability, potentially remote code execution on the client system.
A flaw was found in FreeRDP. A malicious Remote Desktop Protocol (RDP) server can exploit this vulnerability by sending a crafted sequence of progressive display tile updates to a connecting client. Because decompression buffers are allocated without being initialized, processing these updates can trigger an internal assertion failure that terminates the client application or causes uninitialized heap memory to be rendered directly onto the screen. This allows an attacker to cause a Denial of Service (DoS) or disclose sensitive information.
A flaw was found in FreeRDP. When a user connects to a malicious Remote Desktop Protocol (RDP) server, the server can trigger an invalid smartcard connect operation, leading to a use-after-free vulnerability where previously released memory is accessed. A remote attacker can exploit this issue to cause memory corruption, potentially leading to arbitrary code execution or a Denial of Service (DoS) through an application crash.
A flaw was found in FreeRDP. A malicious Remote Desktop Protocol (RDP) server can trigger a Denial of Service (DoS) by sending repeated serial device creation requests when serial port redirection is enabled. Because FreeRDP fails to release previous communication handles before allocating new ones, the client application exhausts available file descriptors and terminates unexpectedly.
A flaw was found in FreeRDP. The proxy component fails to enforce cumulative or absolute size limits when reassembling Remote Desktop Protocol Device Redirection (RDPDR) channel fragments. A remote attacker can exploit this vulnerability by transmitting an initial fragment followed by continuous data fragments without a termination marker, causing unbounded memory retention in the proxy session. This excessive memory consumption can ultimately lead to a Denial of Service (DoS).
A flaw was found in FreeRDP. A malicious Remote Desktop Protocol (RDP) server can exploit this vulnerability by sending specially crafted MP3 audio data to a connected client. Due to an incorrect buffer size calculation during audio decoding, decoded audio data can be written beyond allocated memory limits, resulting in a heap-based buffer overflow. This flaw allows an attacker to crash the client application, leading to a Denial of Service (DoS).
A flaw was found in FreeRDP. A remote, unauthenticated attacker can exploit this issue by connecting to the shadow server and transmitting input data before authentication is completed. This allows the attacker to inject synthetic keystrokes directly into the host user's active session, potentially performing unauthorized actions on the host system.
A flaw was found in FreeRDP. This vulnerability allows a malicious Remote Desktop Protocol (RDP) server to cause client memory corruption and a Denial of Service (DoS) by offering a specially crafted grayscale JPEG image through clipboard redirection. When the client converts the image into bitmap data during a paste operation, an incorrect buffer size calculation causes data to be written beyond the allocated heap boundaries, crashing the application.
A flaw was found in FreeRDP. An unauthenticated remote attacker can cause a Denial of Service (DoS) by exhausting server memory. When processing Network Level Authentication (NLA) connections over Transport Layer Security (TLS), the server misinterprets invalid protocol bytes as an incomplete packet rather than rejecting them. This triggers unbounded receive buffer growth as incoming data is streamed, consuming server memory until the service becomes unresponsive or crashes.
A flaw was found in FreeRDP. This vulnerability allows a local attacker to execute arbitrary code or cause a denial of service (DoS) by supplying a specially crafted persistent cache file. When processing the malformed cache file, an arithmetic calculation error causes an undersized memory buffer to be allocated, leading to a heap-based buffer overflow during data read operations.
A flaw was found in FreeRDP. This flaw allows arbitrary code execution or a Denial of Service (DoS) when parsing persistent cache files. A local attacker can trigger this vulnerability by tricking a user into loading a maliciously crafted cache file containing oversized image dimensions. This manipulation leads to an integer calculation error and a heap-based buffer overflow, causing memory corruption.
A flaw was found in FreeRDP. A malicious Remote Desktop Protocol (RDP) server can exploit a heap-based out-of-bounds write vulnerability by sending specially crafted display frames to a client during video stream processing. This flaw allows client memory to be corrupted, potentially resulting in arbitrary code execution or a denial of service (DoS) on the client system.
A flaw was found in FreeRDP. An out-of-bounds write vulnerability in the server-side NT LAN Manager (NTLM) authentication path can result in a Denial of Service (DoS). When processing authentication messages with hash callbacks enabled, FreeRDP fails to properly validate the Message Integrity Check (MIC) offset. A remote, unauthenticated attacker can exploit this issue by sending a specially crafted authentication message, corrupting heap memory and causing the server to crash.
A flaw was found in FreeRDP. An integer wraparound in rdpsnd_server_select_format() DVI_ADPCM block-alignment arithmetic bypasses validation in the server-side rdpsnd channel. A malicious RDP client can send crafted SNDC_FORMATS PDUs, causing an unbounded heap write during server audio playback that may enable code execution. This issue affects FreeRDP before 3.32.1.
A flaw was found in FreeRDP. A malicious Remote Desktop Protocol (RDP) server or a man-in-the-middle network attacker can cause a Denial of Service (DoS) by sending malformed PNG or JPEG image data during clipboard synchronization. Due to missing error handling in the image parsing routines, processing the invalid image buffer causes the client application to abruptly abort or exit.
A flaw was found in FreeRDP. A malicious Remote Desktop Protocol (RDP) server can trigger excessive memory allocation on the connecting client by specifying an arbitrarily large length in dynamic virtual channel messages. Because the application reserves memory before validating incoming message data, an attacker can exhaust client system memory, resulting in an application crash and a Denial of Service (DoS).
A flaw was found in FreeRDP. This vulnerability allows a malicious Remote Desktop Protocol (RDP) server to cause a Denial of Service (DoS) by crashing the connected client. When a user connects to an attacker-controlled server with RemoteFX decoding enabled, the server can transmit a specially crafted graphics stream. This triggers an internal assertion failure in the decoder, causing the client application to terminate abruptly.
A flaw was found in FreeRDP. A malicious Remote Desktop Protocol (RDP) server can cause a Denial of Service (DoS) by sending a graphics reset packet with a width of zero, followed by a standard display update. Because the client fails to properly handle the zero-width dimension, it releases its primary display buffer without closing the connection, leading to an unhandled crash when attempting to render the subsequent update.
A flaw was found in FreeRDP. An authenticated remote attacker can cause a Denial of Service (DoS) by sending zero-length dynamic virtual channel data messages to the shadow server over an established Remote Desktop Protocol (RDP) session. Because the server fails to properly consume these empty messages, receiving server threads enter an infinite loop. This behavior exhausts system CPU resources and degrades performance until the client disconnects.
A flaw was found in FreeRDP. A malicious Remote Desktop Protocol (RDP) server can cause a denial of service (DoS) or memory corruption on a connecting client. This issue occurs because FreeRDP does not properly validate graphical surface dimensions, resulting in an integer overflow during memory allocation calculations. By sending a specially crafted surface creation message, a rogue server can trigger excessive memory consumption or a heap-based buffer overflow, causing the client application to crash.
A flaw was found in FreeRDP. In server-side input parsing, the application skips the body of an unknown input event without verifying that the data remains within the declared packet length. A remote attacker with an active session can send a crafted, truncated input event, triggering an internal assertion failure that terminates the server process and causes a Denial of Service (DoS).
A flaw was found in FreeRDP. An out-of-bounds write vulnerability exists in freerdp-proxy when processing Bitmap Cache v2 capability sets. The proxy accepts a client-declared numCellCaches value below five and later indexes the bitmap cache cell array at fixed positions 0 through 4. A client that connects to the proxy and completes capability exchange can cause heap corruption, disclosure of adjacent heap contents to the backend server, or a crash of the proxy process.
A flaw was found in FreeRDP. A use-after-free vulnerability exists in the client's Remote Desktop Protocol Graphics (RDPGFX) dynamic virtual channel handling. A malicious RDP server can open a second dynamic virtual channel that reuses an already registered channel name with a different ChannelId, overwriting the listener's single callback slot. When that second channel is closed, the callback is freed without clearing the slot. A subsequent PDU on the original channel then dereferences freed memory, which can crash the client or potentially lead to arbitrary code execution.
A flaw was found in FreeRDP. A malicious Remote Desktop Protocol (RDP) server can cause a Denial of Service (DoS) and heap memory corruption on the connecting client. This issue occurs in the planar graphics codec because new display dimensions are applied before memory buffer reallocation succeeds. When reallocation fails, the context is not rolled back, allowing subsequent planar drawing commands to write beyond the allocated buffer boundaries and crash the client.
A flaw was found in FreeRDP. A use-after-free vulnerability exists in the smartcard emulation feature where a smartcard context is released before its background worker thread is properly terminated. A malicious server can exploit this by sending a crafted sequence of smartcard I/O Request Packets (IRPs) to a client with smartcard redirection enabled. Successful exploitation can corrupt memory or cause the client application to crash, leading to a Denial of Service (DoS).
A flaw was found in FreeRDP. A double-free memory vulnerability in the Kerberos authentication component allows an unauthenticated remote attacker to cause a Denial of Service (DoS). By sending a specially crafted Network Level Authentication (NLA) request, an attacker can corrupt server memory and cause the application process to crash.
A flaw was found in FreeRDP. A malicious Remote Desktop Protocol (RDP) server can trigger a race condition in the client by concurrently transmitting graphics reset commands alongside compressed bitmap data. This flaw leads to a use-after-free condition or out-of-bounds memory access on shared graphics decoding buffers. Consequently, an attacker can corrupt client memory, potentially causing the client application to crash resulting in a Denial of Service (DoS) or exposing sensitive memory contents.
A flaw was found in FreeRDP. This vulnerability allows a remote attacker to cause a Denial of Service (DoS) or potentially execute arbitrary code on the client system. An attacker operating a malicious Remote Desktop Protocol (RDP) server, or acting in a man-in-the-middle position, can exploit this issue by sending specially crafted graphics pipeline commands. This occurs due to improper surface key truncation, causing an internal table to become inconsistent and triggering a heap-based buffer overflow when data is written past allocated memory boundaries.
A flaw was found in FreeRDP. A malicious Remote Desktop (RD) Gateway or network attacker can cause a Denial of Service (DoS) by sending a truncated WebSocket data frame followed by a Transport Layer Security (TLS) connection shutdown. Due to improper handling of the incomplete payload when the connection closes, the client enters an infinite loop, consuming excessive Central Processing Unit (CPU) resources until the application is terminated.
A flaw was found in FreeRDP. An unauthenticated remote attacker could cause a Denial of Service (DoS) by sending a specially crafted Credential Security Support Provider (CredSSP) request that omits negotiation tokens. When processing this malformed request with Network Level Authentication (NLA) enabled, the server triggers an internal assertion failure that abruptly terminates the server process and drops active client sessions.
A flaw was found in FreeRDP. A malicious or compromised Remote Desktop Protocol (RDP) server can trigger a race condition by repeatedly requesting the creation of an already active dynamic virtual channel while client data is concurrently processed. This issue leads to a use-after-free condition, allowing the server to crash the proxy process and result in a Denial of Service (DoS).
A flaw was found in FreeRDP. This vulnerability allows a malicious Remote Desktop Protocol (RDP) server to cause a Denial of Service (DoS) or memory corruption by sending fragmented responses during Early User Authorization (EUA) authentication. Because FreeRDP fails to properly track remaining buffer space across partial network reads, incoming data advances past the allocated memory boundaries. An attacker who successfully exploits this issue triggers an out-of-bounds memory write, crashing the client application.
A flaw was found in FreeRDP. This vulnerability allows a malicious Remote Desktop Protocol (RDP) server to cause a Denial of Service (DoS) by crashing the client application. By sending audio data packets over a dynamic virtual channel and immediately closing the connection, the server triggers a use-after-free condition where the client's audio playback thread accesses already released memory.
A flaw was found in FreeRDP. A compromised or malicious Remote Desktop (RD) Gateway server can send specially crafted Remote Procedure Call (RPC) network messages to a connecting client. Because the client verifies total buffer capacity instead of remaining buffer space before writing incoming data, client heap memory can be overwritten. An attacker can exploit this flaw to potentially execute arbitrary code or crash the client application, resulting in a Denial of Service (DoS).
Loading 1.1 MB of JSON…
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.