{"vuid":"VU#865833","idnumber":"865833","name":"Microsoft Windows Remote Desktop Protocol (RDP) uses weak algorithm for encrypting packets","keywords":["Microsoft","Windows","Remote Desktop Protocol","RDP","weak encryption algorithm","HMAC","RC4","MS02-051","Q324380"],"overview":"Microsoft Windows Remote Desktop Protocol (RDP) uses a weak algorithm for encrypting packets.","clean_desc":"Microsoft describes RDP as follows. RDP is based on, and is an extension of, the T.120 protocol family standards. It is a multichannel-capable protocol that allows for separate virtual channels for carrying device communication and presentation data from the server, as well as encrypted client mouse and keyboard data. Microsoft's implementation of RDP does not encrypt the checksums of the session data. Therefore, a determined attacker could apply cryptanalytic techniques to recover encrypted session traffic. Note that Microsoft has listed the following mitigating factors: An attacker would need the ability to capture an RDP session in order to exploit this vulnerability. In most cases, this would require that the attacker have physical access to the network media. Because encryption keys are negotiated on a per-session basis, a successful attack would allow an attacker to decrypt only a single session and not multiple sessions. Thus, the attacker would need to conduct a separate cryptanalytic attack against each session he or she wished to compromise.","impact":"A remote attacker could apply cryptanalytic techniques to recover encrypted session traffic.","resolution":"Apply a patch.","workarounds":"","sysaffected":"","thanks":"Ben Cohen & Pete Chown of \nSkygate Technology Ltd. discovered this vulnerability.","author":"This document was written by Ian A Finlay.","public":["http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/bulletin/MS02-051.asp","http://msdn.microsoft.com/library/en-us/termserv/termserv/using_terminal_services_virtual_channels.asp","http://www.microsoft.com/windows2000/techinfo/howitworks/terminal/rdpfandp.asp","http://link.springer.de/link/service/series/0558/bibs/2139/21390310.htm","http://www.ietf.org/rfc/rfc2104.txt"],"cveids":["CVE-2002-0863"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2002-09-18T14:36:15Z","publicdate":"2002-09-18T00:00:00Z","datefirstpublished":"2002-12-06T18:55:46Z","dateupdated":"2002-12-06T18:57:18Z","revision":16,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"18","cam_exploitation":"0","cam_internetinfrastructure":"10","cam_population":"10","cam_impact":"15","cam_easeofexploitation":"8","cam_attackeraccessrequired":"10","cam_scorecurrent":"6.3","cam_scorecurrentwidelyknown":"6.75","cam_scorecurrentwidelyknownexploited":"11.25","ipprotocol":"","cvss_accessvector":"","cvss_accesscomplexity":"","cvss_authentication":null,"cvss_confidentialityimpact":"","cvss_integrityimpact":"","cvss_availabilityimpact":"","cvss_exploitablity":null,"cvss_remediationlevel":"","cvss_reportconfidence":"","cvss_collateraldamagepotential":"","cvss_targetdistribution":"","cvss_securityrequirementscr":"","cvss_securityrequirementsir":"","cvss_securityrequirementsar":"","cvss_basescore":"","cvss_basevector":"","cvss_temporalscore":"","cvss_environmentalscore":"","cvss_environmentalvector":"","metric":6.3,"vulnote":null}