{
	"id": "583120c7-c618-40ce-9ba5-dcc991c052b3",
	"created_at": "2026-04-06T00:11:07.658296Z",
	"updated_at": "2026-04-10T13:13:09.367824Z",
	"deleted_at": null,
	"sha1_hash": "f3bd58ccf426dbf0677935331339583a2bebfa8b",
	"title": "Remote Desktop Protocol",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 207097,
	"plain_text": "Remote Desktop Protocol\r\nBy Contributors to Wikimedia projects\r\nPublished: 2004-05-13 · Archived: 2026-04-05 13:06:12 UTC\r\nFrom Wikipedia, the free encyclopedia\r\nRemote Desktop Protocol (RDP) is a proprietary protocol developed by Microsoft Corporation which provides a\r\nuser with a graphical interface to connect to another computer over a network connection.[1] The user employs\r\nRDP client software for this purpose, while the other computer must run RDP server software.\r\nSeveral clients exist for most versions of Microsoft Windows (including Windows Mobile but the support has\r\nended), Linux (for example FreeRDP, Krdc, Remmina, Vinagre or rdesktop), Unix, macOS, iOS, Android, and\r\nother operating systems. RDP servers are built into the server and professional editions of Windows operating\r\nsystems but not home editions; an RDP server for Unix and OS X also exists (for example xrdp). By default, the\r\nserver listens on TCP port 3389[2] and UDP port 3389.[3]\r\nMicrosoft currently refers to their official RDP client software as Remote Desktop Connection, formerly\r\n\"Terminal Services Client\".\r\nThe protocol is an extension of the ITU-T T.128 application sharing protocol. Microsoft makes some\r\nspecifications public on their website.[4]\r\nEvery server and professional version of Microsoft Windows from Windows XP onward[5] includes an installed\r\nRemote Desktop Connection (RDC) (\"Terminal Services\") client (mstsc.exe) whose version is determined by that\r\nof the operating system or by the last applied Windows Service Pack. The Terminal Services server is supported as\r\nan official feature on Windows NT 4.0 Terminal Server Edition, released in 1998, Windows 2000 Server, all\r\neditions of Windows XP except Windows XP Home Edition, Windows Server 2003, Windows Home Server, on\r\nWindows Fundamentals for Legacy PCs, in Windows Vista Ultimate, Enterprise and Business editions, Windows\r\nServer 2008 and Windows Server 2008 R2 and on Windows 7 Professional and above. The home versions of\r\nWindows do not support RDP.\r\nMicrosoft provides the client required for connecting to newer RDP versions for downlevel operating systems.\r\nSince the server improvements are not available downlevel, the features introduced with each newer RDP version\r\nonly work on downlevel operating systems when connecting to a higher version RDP server from these older\r\noperating systems, and not when using the RDP server in the older operating system.[clarification needed]\r\nBased on the ITU-T T.128 application sharing protocol (during draft also known as \"T.share\") from the T.120\r\nrecommendation series, the first version of RDP (named version 4.0) was introduced by Microsoft with \"Terminal\r\nServices\", as a part of their product Windows NT 4.0 Server, Terminal Server Edition.[1] The Terminal Services\r\nEdition of NT 4.0 relied on Citrix's MultiWin technology, previously provided as a part of Citrix WinFrame atop\r\nWindows NT 3.51, in order to support multiple users and login sessions simultaneously. Microsoft required Citrix\r\nhttps://en.wikipedia.org/wiki/Remote_Desktop_Protocol\r\nPage 1 of 9\n\nto license their MultiWin technology to Microsoft in order to be allowed to continue offering their own terminal-services product, then named Citrix MetaFrame, atop Windows NT 4.0. The Citrix-provided DLLs included in\r\nWindows NT 4.0 Terminal Services Edition still carry a Citrix copyright rather than a Microsoft copyright. Later\r\nversions of Windows integrated the necessary support directly. The T.128 application sharing technology was\r\nacquired by Microsoft from UK software developer Data Connection Limited.\r\n[6]\r\nThis version was introduced with Windows 2000 Server, added support for a number of features, including\r\nprinting to local printers, and aimed to improve network bandwidth usage. The RDP clients available through the\r\nWindows 2000 Terminal Server Disk Creation Tool is tested and working on even 16 bit Windows 3.1 using 3rd\r\nparty TCP/IP libraries such as Trumpet WinSock.\r\nThis version was introduced with Windows XP Professional and included support for 24-bit color and sound. It is\r\nsupported on Windows 2000, Windows 9x, and Windows NT 4.0.\r\n[7]\r\n With this version, the name of the client was\r\nchanged from Terminal Services Client to Remote Desktop Connection; the heritage remains to this day, however,\r\nas the underlying executable is still named mstsc.exe.\r\nThis version was introduced with Windows Server 2003, included support for console mode connections, a\r\nsession directory, and local resource mapping. It also introduces Transport Layer Security (TLS) 1.0 for server\r\nauthentication, and to encrypt terminal server communications.[8] This version is built into Windows XP\r\nProfessional x64 Edition and Windows Server 2003 x64 \u0026 x86 Editions, and also available for Windows XP as a\r\ndownload.\r\nThis version was introduced with Windows Vista and incorporated support for Windows Presentation Foundation\r\napplications, Network Level Authentication, multi-monitor spanning and large desktop support, and TLS 1.0\r\nconnections.[9] The RDP 6.0 client is available on Windows XP SP2, Windows Server 2003 SP1/SP2 (x86 and\r\nx64 editions) and Windows XP Professional x64 Edition through KB925876. Microsoft Remote Desktop\r\nConnection Client for Macintosh OS X is also available with support for Intel and PowerPC Mac OS versions\r\n10.4.9 and greater.\r\nThis version was released in February 2008 and is first included with Windows Server 2008 and Windows Vista\r\nwith Service Pack 1 and later backported to Windows XP with Service Pack 3. The RDP 6.1 client is available on\r\nWindows XP SP2, Windows Server 2003 SP1/SP2 (x86 and x64 editions) and Windows XP Professional x64\r\nEdition through KB952155.[10] In addition to changes related to how a remote administrator connects to the\r\n\"console\",[11] this version has new functionality introduced in Windows Server 2008, such as connecting remotely\r\nto individual programs and a new client-side printer redirection system that makes the client's print capabilities\r\navailable to applications running on the server, without having to install print drivers on the server[12][13] also on\r\nthe other hand, remote administrator can freely install, add/remove any software or setting at the client's end.\r\nHowever, to start a remote administration session, one must be a member of the Administrators group on the\r\nserver to which one is trying to get connected.[14]\r\nThis version was released to manufacturing in July 2009 and is included with Windows Server 2008 R2, as well as\r\nwith Windows 7.\r\n[15]\r\n With this release, also changed from Terminal Services to Remote Desktop Services. This\r\nversion has new functions such as Windows Media Player redirection, bidirectional audio, multi-monitor support,\r\nhttps://en.wikipedia.org/wiki/Remote_Desktop_Protocol\r\nPage 2 of 9\n\nAero glass support, enhanced bitmap acceleration, Easy Print redirection,[16]\r\n Language Bar docking. The RDP 7.0\r\nclient is available on Windows XP SP3 and Windows Vista SP1/SP2 through KB969084,[17] and is not officially\r\nsupported on Windows Server 2003 x86 and Windows Server 2003 / Windows XP Professional x64 editions. It is\r\nalso not officially supported on Windows Server 2008.\r\nMost RDP 7.0 features like Aero glass remote use, bidirectional audio, Windows Media Player redirection,\r\nmultiple monitor support and Remote Desktop Easy Print are only available in Windows 7 Enterprise or Ultimate\r\neditions.[18][19]\r\nRelease 7.1 of RDP was included with Windows 7 Service Pack 1 and Windows Server 2008 R2 SP1 in 2010. It\r\nintroduced RemoteFX, which provides virtualized GPU support and host-side encoding.\r\nThis version was released in Windows 8 and Windows Server 2012. This version has new functions such as\r\nAdaptive Graphics (progressive rendering and related techniques), automatic selection of TCP or UDP as transport\r\nprotocol, multi touch support, DirectX 11 support for vGPU, USB redirection supported independently of vGPU\r\nsupport, etc.[20][21] A \"connection quality\" button is displayed in the RDP client connection bar for RDP 8.0\r\nconnections; clicking on it provides further information about connection, including whether UDP is in use or not.\r\n[22]\r\nThe RDP 8.0 client and server components are available on Windows 7 SP1 and Windows Server 2008 R2 SP1\r\nthrough KB2592687. The RDP 8.0 client is also available for Windows Server 2008 R2 SP1, but the server\r\ncomponents are not. The RDC 8.0 client includes support for session encryption using the TLS 1.2 standard.[23]\r\nThe add-on requires the DTLS protocol to be installed as prerequisite.[22] After installing the updates, for the RDP\r\n8.0 protocol to be enabled between Windows 7 machines, an extra configuration step is needed using the Group\r\nPolicy editor.\r\n[24]\r\nA new feature in RDP 8.0 is limited support for RDP session nesting; it only works for Windows 8 and Server\r\n2012 though, Windows 7 and Server 2008 R2 (even with the RDP 8.0 update) do not support this feature.[25]\r\nThe \"shadow\" feature from RDP 7, which allowed an administrator to monitor (snoop) on a RDP connection has\r\nbeen removed in RDP 8. The Aero Glass remoting feature (applicable to Windows 7 machines connecting to each\r\nother) has also been removed in RDP 8.[21][22]\r\nThis version was released with Windows 8.1 and Windows Server 2012 R2. The RDP 8.1 client, like the RDP 8.0\r\nclient, is available on Windows 7 SP1 and Windows Server 2008 R2 SP1 through KB2923545 but unlike the RDP\r\n8.0 update for Windows 7, it does not add a RDP 8.1 server component to Windows 7. Furthermore, if RDP 8.0\r\nserver function is desired on Windows 7, the KB 2592687 (RDP 8.0 client and server components) update must be\r\ninstalled before installing the RDP 8.1 update.[26][27]\r\nSupport for session shadowing was added back in RDP version 8.1. This version also fixes some visual glitches\r\nwith Microsoft Office 2013 when running as a RemoteApp.\r\n[26]\r\nVersion 8.1 of the RDP also enables a \"restricted admin\" mode. Logging into this mode only requires knowledge\r\nof the hashed password, rather than of its plaintext, therefore making a pass the hash attack possible.[28] Microsoft\r\nhttps://en.wikipedia.org/wiki/Remote_Desktop_Protocol\r\nPage 3 of 9\n\nhas released an 82-page document explaining how to mitigate this type of attack.[29]\r\nVersion 10.0 of the RDP was introduced with Windows 10 and includes the following new features: AutoSize\r\nzoom (useful for HiDPI clients). In addition graphics compression improvements were included utilizing\r\nH.264/AVC.[30]\r\n32-bit color support. 8-, 15-, 16-, and 24-bit color are also supported.\r\nEncryption: option of legacy 56-bit or 128-bit RC4 and modern MITM-resistant TLS since version 5.2[8]\r\nAudio Redirection allows users to process audio on a remote desktop and have the sound redirected to their\r\nlocal computer.\r\nFile System Redirection allows users to use their local files on a remote desktop within the terminal\r\nsession.\r\nPrinter Redirection allows users to use their local printer within the terminal session as they would with a\r\nlocally- or network-shared printer.\r\nPort Redirection allows applications running within the terminal session to access local serial and parallel\r\nports directly.\r\nThe remote computer and the local computer can share the clipboard.\r\nCompression goes beyond a framebuffer and takes advantage of font knowledge and tracking of window\r\nstates (inherited from T.128); later extensions add more content-aware features (e.g MS-RDPCR2).\r\nMicrosoft introduced the following features with the release of RDP 6.0 in 2006:\r\nSeamless Windows: remote applications can run on a client machine that is served by a Remote Desktop\r\nconnection. It is available since RDP 6.[31]\r\nRemote Programs: application publishing with client-side file-type associations.\r\nTerminal Services Gateway: enables the ability to use a front-end IIS server to accept connections (over\r\nport 443) for back-end Terminal Services servers via an https connection, similar to how RPC over https\r\nallows Outlook clients to connect to a back-end Exchange 2003 server. Requires Windows Server 2008.\r\nNetwork Level Authentication\r\nSupport for remoting the Aero Glass Theme (or Composed Desktop), including ClearType font-smoothing\r\ntechnology.\r\nSupport for remoting Windows Presentation Foundation applications: compatible clients that have .NET\r\nFramework 3.0 support can display full Windows Presentation Foundation effects on a local machine.\r\nRewrite of device redirection to be more general-purpose, allowing a greater variety of devices to be\r\naccessed.\r\nFully configurable and scriptable via Windows Management Instrumentation.\r\nImproved bandwidth tuning for RDP clients.[citation needed]\r\nSupport for Transport Layer Security (TLS) 1.0 on both server and client ends (can be negotiated if both\r\nparties agree, but not mandatory in a default configuration of any version of Windows).\r\nMultiple monitor support for allowing one session to use multiple monitors on the client (disables desktop\r\ncomposition)\r\nRelease 7.1 of RDP in 2010 introduced the following feature:\r\nhttps://en.wikipedia.org/wiki/Remote_Desktop_Protocol\r\nPage 4 of 9\n\nRemoteFX: RemoteFX provides virtualized GPU support and host-side encoding; it ships as part of\r\nWindows Server 2008 R2 SP1.\r\nThe latest version of RDP supports Transport Layer Security (TLS) version 1.1, 1.2 and 1.3 to protect RDP traffic.\r\n[32]\r\nVersion 5.2 of the RDP in its default configuration is vulnerable to a man-in-the-middle attack. Administrators can\r\nenable transport layer encryption to mitigate this risk.[33][34]\r\nRDP sessions are also susceptible to in-memory credential harvesting, which can be used to launch pass the hash\r\nattacks.[35]\r\nIn March 2012, Microsoft released an update for a critical security vulnerability in the RDP. The vulnerability\r\nallowed a Windows computer to be compromised by unauthenticated clients and computer worms.\r\n[36]\r\nRDP client version 6.1 can be used to reveal the names and pictures of all users on the RDP Server (no matter\r\nwhich Windows version) in order to pick one, if no username is specified for the RDP connection.[citation needed]\r\nIn March 2018 Microsoft released a patch for CVE-2018-0886, a remote code execution vulnerability in CredSSP,\r\nwhich is a Security Support Provider involved in the Microsoft Remote Desktop and Windows Remote\r\nManagement, discovered by Preempt.[37][38]\r\nIn May 2019 Microsoft issued a security patch for CVE-2019-0708 (\"BlueKeep\"), a vulnerability which allows\r\nfor the possibility of remote code execution and which Microsoft warned was \"wormable\", with the potential to\r\ncause widespread disruption. Unusually, patches were also made available for several versions of Windows that\r\nhad reached their end-of-life, such as Windows XP. No immediate malicious exploitation followed, but experts\r\nwere unanimous that this was likely, and could cause widespread harm based on the number of systems that\r\nappeared to have remained exposed and unpatched.[39][40][41]\r\nIn July 2019, Microsoft issued a security patch for CVE-2019-0887, a RDP vulnerability that affects Hyper-V.\r\n[42]\r\nIn April 2025, a security researcher discovered that it is possible to log into accounts through RDP using\r\npasswords that have already been revoked. According to Microsoft, this was by design, and not a bug or\r\nvulnerability.\r\n[43]\r\nSince the release of Remote Desktop Connection, there have been several additional Remote Desktop Protocol\r\nclients created by both Microsoft and other parties including Microsoft Remote Desktop, rdesktop, and FreeRDP.\r\nIn addition to the Microsoft-created Remote Desktop Services, open-source RDP servers on Unix include\r\nFreeRDP (see above), ogon project and xrdp. The Windows Remote Desktop Connection client can be used to\r\nconnect to such a server. There is also Azure Virtual Desktop which makes use of RDP and is a part of the\r\nMicrosoft Azure platform.\r\nThere is also a VirtualBox Remote Display Protocol (VRDP) used in the VirtualBox virtual machine\r\nimplementation by Oracle.\r\n[44]\r\n This protocol is compatible with all RDP clients, such as that provided with\r\nWindows but, unlike the original RDP, can be configured to accept unencrypted and password unprotected\r\nhttps://en.wikipedia.org/wiki/Remote_Desktop_Protocol\r\nPage 5 of 9\n\nconnections, which may be useful in secure and trusted networks, such as home or office LANs. By default,\r\nMicrosoft's RDP server refuses connections to user accounts with empty passwords (but this can be changed with\r\nthe Group Policy Editor[45]). External and guest authorization options are provided by VRDP as well. It does not\r\nmatter which operating system is installed as a guest because VRDP is implemented on the virtual machine (host)\r\nlevel, not in the guest system. The proprietary VirtualBox Extension Pack is required.\r\nMicrosoft requires third-party implementations to license the relevant RDP patents.[46] As of February 2014, the\r\nextent to which open-source clients meet this requirement remains unknown.\r\nSecurity researchers reported in 2016-17 that cybercriminals were selling compromised RDP servers on\r\nunderground forums as well as specialized illicit RDP shops.[47][48] These compromised RDPs may be used as a\r\n\"staging ground\" for conducting other types of fraud or to access sensitive personal or corporate data.[49]\r\nResearchers further report instances of cybercriminals using RDPs to directly drop malware on computers.[50]\r\nComparison of remote desktop software\r\nDesktop virtualization\r\nSecure Shell\r\nSPICE and RFB protocol\r\nVirtual private server\r\n1. ^ Jump up to: a\r\n \r\nb\r\n Deland-Han. \"Understanding Remote Desktop Protocol (RDP) – Windows Server\".\r\ndocs.microsoft.com. Archived from the original on October 17, 2020. Retrieved October 12, 2020.\r\n2. ^ \"How to change the listening port for Remote Desktop\". Microsoft. January 31, 2007. Archived from the\r\noriginal on November 4, 2007. Retrieved November 2, 2007. Microsoft KB article 306759, revision 2.2.\r\n3. ^ \"Service Name and Transport Protocol Port Number Registry\". Internet Assigned Numbers Authority.\r\nJanuary 9, 2015. Retrieved January 13, 2015.\r\n4. ^ \"rdesktop: A Remote Desktop Protocol Client\". www.rdesktop.org. Archived from the original on\r\nDecember 1, 2008. Retrieved November 29, 2008.\r\n5. ^ Microsoft. \"Connecting to another computer Remote Desktop Connection\". Archived from the original on\r\nJanuary 16, 2013. Retrieved December 22, 2012.\r\n6. ^ Implementing Collaboration Technologies in Industry, Bjørn Erik Munkvold, 2003; Chapter 7\r\n7. ^ \"Windows XP Remote Desktop Connection software [XPSP2 5.1.2600.2180]\". Microsoft.com. August 27,\r\n2012. Archived from the original on September 8, 2010. Retrieved March 11, 2014.\r\n8. ^ Jump up to: a\r\n \r\nb\r\n \"Configuring authentication and encryption\". January 21, 2005. Archived from the\r\noriginal on March 18, 2009. Retrieved March 30, 2009. Microsoft Technet article\r\n9. ^ \"Remote Desktop Connection (Terminal Services Client 6.0)\". June 8, 2007. Archived from the original\r\non July 17, 2007. Retrieved June 20, 2007. Microsoft KB article 925876, revision 7.0.\r\n10. ^ \"Description of the Remote Desktop Connection 6.1 client update for Terminal Services in Windows XP\r\nService Pack 2\". microsoft. Archived from the original on August 29, 2008. Retrieved March 11, 2014.\r\n11. ^ \"Changes to Remote Administration in Windows Server 2008\". Terminal Services Team Blog. Microsoft.\r\nDecember 17, 2007. Archived from the original on March 5, 2009. Retrieved February 10, 2008.\r\n12. ^ \"Terminal Services Printing\". TechNet – Windows Server 2008 Technical Library. Agozik-Microsoft.\r\nJanuary 10, 2008. Archived from the original on January 21, 2014. Retrieved February 10, 2008.\r\nhttps://en.wikipedia.org/wiki/Remote_Desktop_Protocol\r\nPage 6 of 9\n\n13. ^ \"Introducing Terminal Services Easy Print: Part 1 – Remote Desktop Services (Terminal Services) Team\r\nBlog – Site Home – MSDN Blogs\". Blogs.msdn.com. Archived from the original on February 13, 2014.\r\nRetrieved February 13, 2014.\r\n14. ^ \"Securing Remote Desktop (RDP) for System Administrators | Information Security Office\".\r\nsecurity.berkeley.edu. Archived from the original on October 12, 2020. Retrieved October 12, 2020.\r\n15. ^ \"Remote Desktop Connection 7 for Windows 7, Windows XP \u0026 Windows Vista\". Terminal Services Team\r\nBlog. Microsoft. August 21, 2009. Archived from the original on August 27, 2009. Retrieved August 21,\r\n2009.\r\n16. ^ \"Using Remote Desktop Easy Print in Windows 7 and Windows Server 2008 R2\". Blogs.msdn.com.\r\nArchived from the original on May 8, 2010. Retrieved March 11, 2014.\r\n17. ^ \"Announcing the availability of Remote Desktop Connection 7.0 for Windows XP SP3, Windows Vista\r\nSP1, and Windows Vista SP2\". Blogs.msdn.com. Archived from the original on March 8, 2010. Retrieved\r\nMarch 11, 2014.\r\n18. ^ \"Aero Glass Remoting in Windows Server 2008 R2\". Blogs.msdn.com. Archived from the original on\r\nJune 27, 2009. Retrieved March 11, 2014.\r\n19. ^ \"Remote Desktop Connection 7 for Windows 7, Windows XP \u0026 Windows Vista\". Blogs.msdn.com.\r\nArchived from the original on August 27, 2009. Retrieved March 11, 2014.\r\n20. ^ \"Windows Server 2012 Remote Desktop Services (RDS) – Windows Server Blog – Site Home – TechNet\r\nBlogs\". Blogs.technet.com. May 8, 2012. Archived from the original on October 5, 2013. Retrieved\r\nFebruary 13, 2014.\r\n21. ^ Jump up to: a\r\n \r\nb\r\n \"How Microsoft RDP 8.0 addresses WAN, graphics shortcomings\".\r\nSearchvirtualdesktop.techtarget.com. Archived from the original on February 9, 2014. Retrieved February\r\n13, 2014.\r\n22. ^ Jump up to: a\r\n \r\nb\r\n \r\nc\r\n \"Remote Desktop Protocol (RDP) 8.0 update for Windows 7 and Windows Server 2008\r\nR2\". Support.microsoft.com. Archived from the original on October 25, 2012. Retrieved February 13,\r\n2014.\r\n23. ^ \"Incorrect TLS is displayed - Windows Server\". June 5, 2024.\r\n24. ^ \"Get the best RDP 8.0 experience when connecting to Windows 7: What you need to know – Remote\r\nDesktop Services (Terminal Services) Team Blog – Site Home – MSDN Blogs\". Blogs.msdn.com. Archived\r\nfrom the original on February 12, 2014. Retrieved February 13, 2014.\r\n25. ^ \"Running a Remote Desktop Connection session within another Remote Desktop Connection session is\r\nsupported with Remote Desktop Protocol 8.0 for specific scenarios\". Support.microsoft.com. November 2,\r\n2012. Archived from the original on January 17, 2014. Retrieved February 13, 2014.\r\n26. ^ Jump up to: a\r\n \r\nb\r\n \"Update for RemoteApp and Desktop Connections feature is available for Windows\".\r\nSupport.microsoft.com. February 11, 2014. Archived from the original on February 9, 2014. Retrieved\r\nMarch 11, 2014.\r\n27. ^ \"Remote Desktop Protocol 8.1 Update for Windows 7 SP1 released to web – Remote Desktop Services\r\n(Terminal Services) Team Blog – Site Home – MSDN Blogs\". Blogs.msdn.com. Archived from the original\r\non February 22, 2014. Retrieved February 13, 2014.\r\n28. ^ \"New \"Restricted Admin\" feature of RDP 8.1 allows pass-the-hash\". Labs.portcullis.co.uk. October 20,\r\n2013. Archived from the original on February 10, 2014. Retrieved March 11, 2014.\r\nhttps://en.wikipedia.org/wiki/Remote_Desktop_Protocol\r\nPage 7 of 9\n\n29. ^ \"Mitigating Pass-the-Hash (PtH) Attacks and Other Credential Theft Techniques\". Microsoft.com.\r\nArchived from the original on April 21, 2014. Retrieved March 11, 2014.\r\n30. ^ \"Remote Desktop Protocol (RDP) 10 AVC/H.264 improvements in Windows 10 and Windows Server\r\n2016 Technical Preview\". Microsoft.com. Archived from the original on August 17, 2016. Retrieved\r\nJanuary 12, 2016.\r\n31. ^ \"[MS-RDPERP]: Remote Desktop Protocol: Remote Programs Virtual Channel Extension\".\r\nMsdn.microsoft.com. Archived from the original on April 14, 2012. Retrieved February 13, 2014.\r\n32. ^ \"[MS-RDPBCGR]: Enhanced RDP Security\". April 23, 2024.\r\n33. ^ \"National Vulnerability Database (NVD) National Vulnerability Database (CVE-2005-1794)\".\r\nWeb.nvd.nist.gov. July 19, 2011. Archived from the original on September 14, 2011. Retrieved February 13,\r\n2014.\r\n34. ^ \"Configuring Terminal Servers for Server Authentication to Prevent \"Man in the Middle\" Attacks\".\r\nMicrosoft. July 12, 2008. Archived from the original on November 6, 2011. Retrieved November 9, 2011.\r\n35. ^ \"Mimikatz and Windows RDP: An Attack Case Study\". SentinelOne. June 6, 2019. Archived from the\r\noriginal on October 16, 2020. Retrieved October 12, 2020.\r\n36. ^ \"Microsoft Security Bulletin MS12-020 – Critical\". Microsoft. March 13, 2012. Archived from the\r\noriginal on February 13, 2014. Retrieved March 16, 2012.\r\n37. ^ \"CVE-2018-0886 – CredSSP Remote Code Execution Vulnerability\". microsoft.com. Archived from the\r\noriginal on March 23, 2018. Retrieved March 23, 2018.\r\n38. ^ Karni, Eyal. \"From Public Key to Exploitation: How We Exploited the Authentication in MS-RDP\".\r\nArchived from the original on March 23, 2018. Retrieved March 23, 2018.\r\n39. ^ Cimpanu, Catalin. \"Even the NSA is urging Windows users to patch BlueKeep (CVE-2019-0708)\".\r\nZDNet. Archived from the original on September 6, 2019. Retrieved June 20, 2019.\r\n40. ^ Goodin, Dan (May 31, 2019). \"Microsoft practically begs Windows users to fix wormable BlueKeep\r\nflaw\". Ars Technica. Archived from the original on July 22, 2019. Retrieved May 31, 2019.\r\n41. ^ Warren, Tom (May 14, 2019). \"Microsoft warns of major WannaCry-like Windows security exploit,\r\nreleases XP patches\". The Verge. Archived from the original on September 2, 2019. Retrieved June 20,\r\n2019.\r\n42. ^ Ilascu, Ionut (7 August 2019). \"Microsoft Ignored RDP Vulnerability Until it Affected Hyper-V\".\r\nBleeping Computer. Archived from the original on 8 August 2019. Retrieved 8 August 2019.\r\n43. ^ Goodin, Dan (April 30, 2025). \"Windows RDP lets you log in using revoked passwords. Microsoft is OK\r\nwith that\". Ars Technica. Retrieved May 13, 2025.\r\n44. ^ \"VirtualBox Manual: 7.1. Remote Display (VRDP Support)\". VirtualBox. Archived from the original on\r\nNovember 21, 2019. Retrieved February 27, 2020.\r\n45. ^ Bens, Jelle (January 31, 2010). \"Jelle Bens: Windows 7 RDP with blank password\".\r\nJellebens.blogspot.ru. Archived from the original on May 8, 2013. Retrieved March 11, 2014.\r\n46. ^ \"Remote Desktop Protocol Licensing Available for RDP 8\". Blogs.msdn.com. December 11, 2014.\r\nArchived from the original on February 8, 2018. Retrieved February 8, 2018.\r\n47. ^ GReAT (June 15, 2016). \"xDedic – the shady world of hacked servers for sale\". SecureList. Archived\r\nfrom the original on December 15, 2018. Retrieved December 15, 2018.\r\n48. ^ Kremez, Vitali; Rowley, Liv (October 24, 2017). \"\"Ultimate Anonymity Services\" Shop Offers\r\nCybercriminals International RDP Servers\". Archived from the original on December 15, 2018. Retrieved\r\nhttps://en.wikipedia.org/wiki/Remote_Desktop_Protocol\r\nPage 8 of 9\n\nDecember 15, 2018.\r\n49. ^ Bisson, David (July 19, 2018). \"Dark Web 'RDP Shops' Offer Access to Vulnerable Systems for as Little\r\nas $3\". Security Intelligence. Archived from the original on December 15, 2018. Retrieved December 15,\r\n2018.\r\n50. ^ Ragan, Steve (July 19, 2018). \"Samsam infected thousands of LabCorp systems via brute force RDP\".\r\nCSO Online. Archived from the original on December 15, 2018. Retrieved December 15, 2018.\r\nRemote Desktop Protocol – from Microsoft's Developer Network\r\nUnderstanding the Remote Desktop Protocol – from support.microsoft.com\r\nMS-RDPBCGR: Remote Desktop Protocol: Basic Connectivity and Graphics Remoting Specification –\r\nfrom Microsoft's Developer Network\r\nSource: https://en.wikipedia.org/wiki/Remote_Desktop_Protocol\r\nhttps://en.wikipedia.org/wiki/Remote_Desktop_Protocol\r\nPage 9 of 9",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"ETDA"
	],
	"origins": [
		"web"
	],
	"references": [
		"https://en.wikipedia.org/wiki/Remote_Desktop_Protocol"
	],
	"report_names": [
		"Remote_Desktop_Protocol"
	],
	"threat_actors": [],
	"ts_created_at": 1775434267,
	"ts_updated_at": 1775826789,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/f3bd58ccf426dbf0677935331339583a2bebfa8b.pdf",
		"text": "https://archive.orkl.eu/f3bd58ccf426dbf0677935331339583a2bebfa8b.txt",
		"img": "https://archive.orkl.eu/f3bd58ccf426dbf0677935331339583a2bebfa8b.jpg"
	}
}