JVN Info.

Id
67518  
Name
JVNDB-2017-003815  
Title
複数の Apple 製品の AVEVideoEncoder コンポーネントにおける特権付きコンテキスト内で任意のコードを実行される脆弱性  
Summary
Apple iOS、tvOS、および watchOS の AVEVideoEncoder コンポーネントには、特権付きコンテキスト内で任意のコードを実行される、またはサービス運用妨害 (メモリ破損) 状態にされる脆弱性が存在します。  
Nvdinfo
CVE-2017-6999  
Cvssv2
9.3  
Jvnurl
http://jvndb.jvn.jp/ja/contents/2017/JVNDB-2017-003815.html  
Published Date
2017-05-15  
Registered Date
2017-06-08  
Last Updated Date
2017-06-08  

Actions

Related Nessuslogs

Id Log ID Jvninfo Id Plugin ID CVE CVSS Risk Host Protocol Port Name Synopsis Description Solution See Also Plugin Output Actions
2316 H28-MOJ-Online-Nara-11-Seg-1-20161126-Endo_oxa90g.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.132.45 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
2558 H28-MOJ-Online-Nara-11-Seg-1-20161126-Endo_oxa90g.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.132.57 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
3289 H28-MOJ-Online-Nara-11-Seg-2-20161126-Endo_rsvx6u.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.132.46 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
3531 H28-MOJ-Online-Nara-11-Seg-2-20161126-Endo_rsvx6u.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.132.58 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
5012 H28-MOJ-Online-Nara-13-Seg-1-20161126-Endo_9whfs5.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.134.53 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
5231 H28-MOJ-Online-Nara-13-Seg-2-20161126-Endo_0pcahr.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.134.54 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
6503 H28-MOJ-Online-Nara-16-seg-1-20161126-soga_ubl064.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.137.45 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
6664 H28-MOJ-Online-Nara-16-seg-1-20161126-soga_ubl064.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.137.53 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
6827 H28-MOJ-Online-Nara-16-seg-1-20161126-soga_ubl064.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.137.57 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
7399 H28-MOJ-Online-Nara-16-seg-1-20161126-soga_ubl064.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.137.65 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
7605 H28-MOJ-Online-Nara-16-seg-1-20161126-soga_ubl064.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.137.68 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
7760 H28-MOJ-Online-Nara-16-seg-1-20161126-soga_ubl064.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.137.69 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
7956 H28-MOJ-Online-Nara-16-seg-1-20161126-soga_ubl064.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.137.70 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
9305 H28-MOJ-Online-Nara-16-seg-2-20161126-soga_e6g03u.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.137.46 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
9465 H28-MOJ-Online-Nara-16-seg-2-20161126-soga_e6g03u.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.137.54 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
9629 H28-MOJ-Online-Nara-16-seg-2-20161126-soga_e6g03u.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.137.58 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
16818 H28-MOJ-Teikyo-Nara-15-Seg-1-20161128-Endo_gheygl.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.30.199.62 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
19038 H28-MOJ-Teikyo-Nara-17-seg-1-20161128-w510.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.30.201.63 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
20052 H28-MOJ-Teikyo-Nara-17-seg-2-20161128-w510.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.30.201.64 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
20247 H28-MOJ-Teikyo-Nara-17-seg-2-20161128-w510.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.30.201.65 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
20698 H28-MOJ-Teikyo-Nara-17-seg-2-20161128-w510.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.30.201.69 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
20923 H28-MOJ-Teikyo-Nara-17-seg-2-20161128-w510.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.30.201.70 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
21323 H28-MOJ-Teikyo-Nara-17-seg-4-20161128-w510.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.30.201.62 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
21480 H28-MOJ-Teikyo-Nara-17-seg-4-20161128-w510.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.30.201.71 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
25875 H28-MOJ-Online-Funa-7-Seg-1-161103.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.4.45 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
26090 H28-MOJ-Online-Funa-7-Seg-1-161103.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.4.48 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
26304 H28-MOJ-Online-Funa-7-Seg-1-161103.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.4.57 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
27176 H28-MOJ-Online-Funa-7-Seg-2-161103.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.4.46 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
27391 H28-MOJ-Online-Funa-7-Seg-2-161103.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.4.47 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
27605 H28-MOJ-Online-Funa-7-Seg-2-161103.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.4.58 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
28962 H28-MOJ-Online-Funa-9-Seg-1-161103.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.6.53 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
29119 H28-MOJ-Online-Funa-9-Seg-1-161103.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.6.55 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
29311 H28-MOJ-Online-Funa-9-Seg-2-161103.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.6.54 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
30010 H28-MOJ-Online-Funa-12-seg-v1-161103.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.9.45 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
30144 H28-MOJ-Online-Funa-12-seg-v1-161103.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.9.53 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
30282 H28-MOJ-Online-Funa-12-seg-v1-161103.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.9.57 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
30776 H28-MOJ-Online-Funa-12-seg-v1-161103.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.9.65 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
30961 H28-MOJ-Online-Funa-12-seg-v1-161103.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.9.68 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
31116 H28-MOJ-Online-Funa-12-seg-v1-161103.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.9.69 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
31311 H28-MOJ-Online-Funa-12-seg-v1-161103.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.9.70 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
32424 H28-MOJ-Online-Funa-12-seg-v2-161103.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.9.46 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
32558 H28-MOJ-Online-Funa-12-seg-v2-161103.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.9.54 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
32696 H28-MOJ-Online-Funa-12-seg-v2-161103.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.9.58 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
33508 H28-MOJ-Online-Funa-12-seg-v3-161103.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.9.47 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
33657 H28-MOJ-Online-Funa-12-seg-v3-161103.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.9.48 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
33790 H28-MOJ-Online-Funa-12-seg-v3-161103.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.27.9.55 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
41013 H28-MOJ-Teikyo-Yokohama-16-seg-01-21161121-abe_4l6tzo.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.30.135.62 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
42878 H28-MOJ-Teikyo-Yokohama-18-seg-01-21161121-abe_ubh1mj.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.30.138.62 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
43062 H28-MOJ-Teikyo-Yokohama-18-seg-01-21161121-abe_ubh1mj.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.30.138.63 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
43258 H28-MOJ-Teikyo-Yokohama-18-seg-01-21161121-abe_ubh1mj.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.30.138.65 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
43780 H28-MOJ-Teikyo-Yokohama-18-seg-01-21161121-abe_ubh1mj.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.30.138.69 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
44008 H28-MOJ-Teikyo-Yokohama-18-seg-01-21161121-abe_ubh1mj.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.30.138.70 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
44162 H28-MOJ-Teikyo-Yokohama-18-seg-01-21161121-abe_ubh1mj.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.30.138.71 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
45670 H28-MOJ-Teikyo-Yokohama-18-seg-02-21161121-abe_vilnov.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.30.138.64 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
48267 H28-MOJ-Teikyo-Makuhari-3-Seg-1-161124-w510.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.30.161.62 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
48699 H28-MOJ-Teikyo-Makuhari-4-Seg-1-161124-w510.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.30.162.62 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
49140 H28-MOJ-Teikyo-Shinkawa-3-Seg-1-161122-w510.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.30.151.62 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
49589 H28-MOJ-Teikyo-Shinkawa-4-Seg-1-161122-w510.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.30.152.62 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
49892 H28_MUN_DWEB_Q4_172_16_20_seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.20.126 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
50171 H28_MUN_DWEB_Q4_172_16_20_seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.20.160 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
50252 H28_MUN_DWEB_Q4_172_16_20_seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.20.17 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
50328 H28_MUN_DWEB_Q4_172_16_20_seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.20.18 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
50441 H28_MUN_DWEB_Q4_172_16_20_seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.20.21 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
50530 H28_MUN_DWEB_Q4_172_16_20_seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.20.22 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
50654 H28_MUN_DWEB_Q4_172_16_20_seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.20.39 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
50706 H28_MUN_DWEB_Q4_172_16_20_seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.20.63 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
50795 H28_MUN_DWEB_Q4_172_16_21_seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.21.226 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
50873 H28_MUN_DWEB_Q4_172_16_21_seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.21.242 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
51008 H28_MUN_DWEB_Q4_172_16_212_seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.212.1 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
52286 H28_MUN_DWEB_Q4_192_168_242_Part1.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.130 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
52377 H28_MUN_DWEB_Q4_192_168_242_Part1.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.141 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
52466 H28_MUN_DWEB_Q4_192_168_242_Part1.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.15 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
52550 H28_MUN_DWEB_Q4_192_168_242_Part1.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.181 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
52636 H28_MUN_DWEB_Q4_192_168_242_Part1.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.183 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
52719 H28_MUN_DWEB_Q4_192_168_242_Part1.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.19 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
52813 H28_MUN_DWEB_Q4_192_168_242_Part1.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.24 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
53014 H28_MUN_DWEB_Q4_192_168_242_Part1.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.62 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
53097 H28_MUN_DWEB_Q4_192_168_242_Part1.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.71 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
53182 H28_MUN_DWEB_Q4_192_168_242_Part1.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.88 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
53270 H28_MUN_DWEB_Q4_192_168_242_Part1.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.9 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
53427 H28_MUN_DWEB_Q4_192_168_243_Part1.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.243.123 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
53505 H28_MUN_DWEB_Q4_192_168_243_Part1.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.243.153 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
53668 H28_MUN_DWEB_Q4_192_168_243_Part1.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.243.18 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
53761 H28_MUN_DWEB_Q4_192_168_243_Part1.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.243.20 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
53846 H28_MUN_DWEB_Q4_192_168_243_Part1.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.243.63 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
53926 H28_MUN_DWEB_Q4_192_168_243_Part1.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.243.65 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
54010 H28_MUN_DWEB_Q4_192_168_243_Part1.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.243.90 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
55274 H28_DWEB_NW_Scan_Q1_172_16_20_Seg_20160518_w9z1nf.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.20.126 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
55521 H28_DWEB_NW_Scan_Q1_172_16_20_Seg_20160518_w9z1nf.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.20.160 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
55597 H28_DWEB_NW_Scan_Q1_172_16_20_Seg_20160518_w9z1nf.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.20.17 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
55669 H28_DWEB_NW_Scan_Q1_172_16_20_Seg_20160518_w9z1nf.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.20.18 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
55751 H28_DWEB_NW_Scan_Q1_172_16_20_Seg_20160518_w9z1nf.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.20.200 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
55812 H28_DWEB_NW_Scan_Q1_172_16_20_Seg_20160518_w9z1nf.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.20.21 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
55889 H28_DWEB_NW_Scan_Q1_172_16_20_Seg_20160518_w9z1nf.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.20.22 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
56008 H28_DWEB_NW_Scan_Q1_172_16_20_Seg_20160518_w9z1nf.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.20.39 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
56055 H28_DWEB_NW_Scan_Q1_172_16_20_Seg_20160518_w9z1nf.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.20.63 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
56174 H28_DWEB_NW_Scan_Q1_172_16_212_Seg_20160518_24dedy.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.212.1 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
56356 H28_DWEB_NW_Scan_Q1_172_16_240_Seg_20160518_hepxqa.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.240.100 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
57900 H28_DWeb_NWScan_Q1_172_16_21_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.21.226 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
57972 H28_DWeb_NWScan_Q1_172_16_21_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 172.16.21.242 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
58148 H28_DWeb_NWScan_Q1_192_168_242_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.112 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
58265 H28_DWeb_NWScan_Q1_192_168_242_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.130 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
58331 H28_DWeb_NWScan_Q1_192_168_242_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.141 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
58419 H28_DWeb_NWScan_Q1_192_168_242_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.15 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
58492 H28_DWeb_NWScan_Q1_192_168_242_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.181 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
58569 H28_DWeb_NWScan_Q1_192_168_242_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.183 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
58644 H28_DWeb_NWScan_Q1_192_168_242_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.19 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
58727 H28_DWeb_NWScan_Q1_192_168_242_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.24 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
58913 H28_DWeb_NWScan_Q1_192_168_242_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.62 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
59072 H28_DWeb_NWScan_Q1_192_168_242_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.71 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
59201 H28_DWeb_NWScan_Q1_192_168_242_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.88 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
59284 H28_DWeb_NWScan_Q1_192_168_242_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.242.9 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
59362 H28_DWeb_NWScan_Q1_192_168_243_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.243.123 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
59440 H28_DWeb_NWScan_Q1_192_168_243_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.243.124 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
59504 H28_DWeb_NWScan_Q1_192_168_243_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.243.153 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
59663 H28_DWeb_NWScan_Q1_192_168_243_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.243.18 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
59749 H28_DWeb_NWScan_Q1_192_168_243_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.243.20 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
59835 H28_DWeb_NWScan_Q1_192_168_243_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.243.216 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
60017 H28_DWeb_NWScan_Q1_192_168_243_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.243.63 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
60090 H28_DWeb_NWScan_Q1_192_168_243_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.243.65 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx
60165 H28_DWeb_NWScan_Q1_192_168_243_Seg.csv 67518 18405 CVE-2005-1794 5.1 Medium 192.168.243.90 tcp 3389 Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness It may be possible to get access to the remote host. The remote version of the Remote Desktop Protocol Server (Terminal Service) is vulnerable to a man-in-the-middle (MiTM) attack. The RDP client makes no effort to validate the identity of the server when setting up encryption. An attacker with the ability to intercept traffic from the RDP server can establish encryption with the client and server without being detected. A MiTM attack of this nature would allow the attacker to obtain any sensitive information transmitted, including authentication credentials. This flaw exists because the RDP server stores a hard-coded RSA private key in the mstlsapi.dll library. Any local user with access to this file (on any Windows system) can retrieve the key and use it for this attack. - Force the use of SSL as a transport layer for this service if supported, or/and - Select the "Allow connections only from computers running Remote Desktop with Network Level Authentication" setting if it is available. http://www.oxid.it/downloads/rdp-gbu.pdf http://www.nessus.org/u?e2628096 http://technet.microsoft.com/en-us/library/cc782610.aspx