Documente Academic
Documente Profesional
Documente Cultură
Table Of Contents
Hosts Summary (Executive).................................................................................................3
172.29.1.19.................................................................................................................................................................. 4
172.29.1.62.................................................................................................................................................................. 5
Vulnerabilities By Host......................................................................................................... 7
172.29.1.19.................................................................................................................................................................. 8
172.29.1.62................................................................................................................................................................ 21
Vulnerabilities By Plugin.....................................................................................................37
18405 (2) - Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness............................ 38
57608 (2) - SMB Signing Required.......................................................................................................................... 39
57690 (2) - Terminal Services Encryption Level is Medium or Low......................................................................... 40
58453 (2) - Terminal Services Doesn't Use Network Level Authentication (NLA)....................................................41
51192 (1) - SSL Certificate Cannot Be Trusted....................................................................................................... 42
57582 (1) - SSL Self-Signed Certificate................................................................................................................... 43
30218 (2) - Terminal Services Encryption Level is not FIPS-140 Compliant........................................................... 44
11219 (7) - Nessus SYN scanner.............................................................................................................................45
11011 (3) - Microsoft Windows SMB Service Detection...........................................................................................46
10107 (2) - HTTP Server Type and Version............................................................................................................ 47
10114 (2) - ICMP Timestamp Request Remote Date Disclosure.............................................................................48
10287 (2) - Traceroute Information...........................................................................................................................49
10394 (2) - Microsoft Windows SMB Log In Possible..............................................................................................50
10785 (2) - Microsoft Windows SMB NativeLanManager Remote System Information Disclosure.......................... 51
11936 (2) - OS Identification.....................................................................................................................................52
19506 (2) - Nessus Scan Information.......................................................................................................................53
22964 (2) - Service Detection...................................................................................................................................55
24260 (2) - HyperText Transfer Protocol (HTTP) Information.................................................................................. 56
24786 (2) - Nessus Windows Scan Not Performed with Admin Privileges.............................................................. 57
25220 (2) - TCP/IP Timestamps Supported............................................................................................................. 58
26917 (2) - Microsoft Windows SMB Registry : Nessus Cannot Access the Windows Registry.............................. 59
42410 (2) - Microsoft Windows NTLMSSP Authentication Request Remote Network Name Disclosure................. 60
43111 (2) - HTTP Methods Allowed (per directory)................................................................................................. 61
45590 (2) - Common Platform Enumeration (CPE)..................................................................................................62
54615 (2) - Device Type........................................................................................................................................... 63
66334 (2) - Patch Report.......................................................................................................................................... 64
10863 (1) - SSL Certificate Information....................................................................................................................65
10940 (1) - Windows Terminal Services Enabled.................................................................................................... 66
45410 (1) - SSL Certificate commonName Mismatch.............................................................................................. 67
56984 (1) - SSL / TLS Versions Supported..............................................................................................................68
64814 (1) - Terminal Services Use SSL/TLS........................................................................................................... 69
66173 (1) - RDP Screenshot.................................................................................................................................... 70
172.29.1.19
Summary
Critical
High
Medium
Low
Info
Total
19
24
Details
Severity
Plugin Id
Name
Medium (5.1)
18405
Medium (5.0)
57608
Medium (4.3)
57690
Medium (4.3)
58453
Low (2.6)
30218
Info
10107
Info
10114
Info
10287
Traceroute Information
Info
10394
Info
10785
Info
11011
Info
11219
Info
11936
OS Identification
Info
19506
Info
22964
Service Detection
Info
24260
Info
24786
Info
25220
Info
26917
Info
42410
Info
43111
Info
45590
Info
54615
Device Type
Info
66334
Patch Report
172.29.1.62
Summary
Critical
High
Medium
Low
Info
Total
25
32
Details
Severity
Plugin Id
Name
Medium (6.4)
51192
Medium (6.4)
57582
Medium (5.1)
18405
Medium (5.0)
57608
Medium (4.3)
57690
Medium (4.3)
58453
Low (2.6)
30218
Info
10107
Info
10114
Info
10287
Traceroute Information
Info
10394
Info
10785
Info
10863
Info
10940
Info
11011
Info
11219
Info
11936
OS Identification
Info
19506
Info
22964
Service Detection
Info
24260
Info
24786
Info
25220
Info
26917
Info
42410
Info
43111
Info
45410
Info
45590
Info
54615
Device Type
Info
56984
Info
64814
Info
66173
RDP Screenshot
Info
66334
Patch Report
Vulnerabilities By Host
172.29.1.19
Scan Information
Start time:
End time:
Host Information
Netbios Name:
PEHERACOSQ
IP:
172.29.1.19
OS:
Results Summary
Critical
High
Medium
Low
Info
Total
23
28
Results Details
0/icmp
10114 - ICMP Timestamp Request Remote Date Disclosure
Synopsis
It is possible to determine the exact time set on the remote host.
Description
The remote host answers to an ICMP timestamp request. This allows an attacker to know the date that is set on
the targeted machine, which may assist an unauthenticated, remote attacker in defeating time-based authentication
protocols.
Timestamps returned from machines running Windows Vista / 7 / 2008 / 2008 R2 are deliberately incorrect, but
usually within 1000 seconds of the actual system time.
Solution
Filter out the ICMP timestamp requests (13), and the outgoing ICMP timestamp replies (14).
Risk Factor
None
References
CVE
CVE-1999-0524
XREF
OSVDB:94
XREF
CWE:200
Plugin Information:
Publication date: 1999/08/01, Modification date: 2012/06/18
Ports
icmp/0
The ICMP timestamps seem to be in little endian format (not in network format)
The difference between the local and remote clocks is 172 seconds.
0/tcp
24786 - Nessus Windows Scan Not Performed with Admin Privileges
Synopsis
The Nessus scan of this host may be incomplete due to insufficient privileges provided.
Description
The Nessus scanner testing the remote host has been given SMB credentials to log into the remote host, however
these credentials do not have administrative privileges.
Typically, when Nessus performs a patch audit, it logs into the remote host and reads the version of the DLLs on
the remote host to determine if a given patch has been applied or not. This is the method Microsoft recommends to
determine if a patch has been applied.
If your Nessus scanner does not have administrative privileges when doing a scan, then Nessus has to fall back to
perform a patch audit through the registry which may lead to false positives (especially when using third-party patch
auditing tools) or to false negatives (not all patches can be detected through the registry).
Solution
Reconfigure your scanner to use credentials with administrative privileges.
Risk Factor
None
Plugin Information:
Publication date: 2007/03/12, Modification date: 2013/01/07
Ports
tcp/0
It was not possible to connect to '\\PEHERACOSQ\ADMIN$' with the supplied credentials.
Description
The remote host implements TCP timestamps, as defined by RFC1323. A side effect of this feature is that the uptime
of the remote host can sometimes be computed.
See Also
http://www.ietf.org/rfc/rfc1323.txt
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2007/05/16, Modification date: 2011/03/20
Ports
tcp/0
11936 - OS Identification
Synopsis
It is possible to guess the remote operating system.
Description
Using a combination of remote probes (TCP/IP, SMB, HTTP, NTP, SNMP, etc...), it is possible to guess the name of
the remote operating system in use. It is also sometimes possible to guess the version of the operating system.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2003/12/09, Modification date: 2014/02/19
Ports
tcp/0
Remote operating system : Microsoft Windows Server 2008 R2
Confidence Level : 75
Method : HTTP
Description
Based on the remote operating system, it is possible to determine what the remote system type is (eg: a printer,
router, general-purpose computer, etc).
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2011/05/23, Modification date: 2011/05/23
Ports
tcp/0
Remote device type : general-purpose
Confidence level : 75
Description
By using information obtained from a Nessus scan, this plugin reports CPE (Common Platform Enumeration) matches
for various hardware and software products found on a host.
Note that if an official CPE is not available for the product, this plugin computes the best possible CPE based on the
information available from the scan.
See Also
http://cpe.mitre.org/
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2010/04/21, Modification date: 2014/09/19
Ports
tcp/0
The remote operating system matched the following CPE :
cpe:/o:microsoft:windows_server_2008:r2 -> Microsoft Windows Server 2008 R2
Following application CPE matched on the remote system :
cpe:/a:microsoft:iis:7.5 -> Microsoft Internet Information Services (IIS) 7.5
Description
The remote host is missing one or several security patches. This plugin lists the newest version of each patch to install
to make sure the remote host is up-to-date.
Solution
10
Risk Factor
None
Plugin Information:
Publication date: 2013/07/08, Modification date: 2014/09/09
Ports
tcp/0
Description
This script displays, for each tested host, information about the scan itself :
- The version of the plugin set
- The type of scanner (Nessus or Nessus Home)
- The version of the Nessus Engine
- The port scanner(s) used
- The port range scanned
- Whether credentialed or third-party patch management checks are possible
- The date of the scan
- The duration of the scan
- The number of hosts scanned in parallel
- The number of checks done in parallel
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2005/08/26, Modification date: 2014/07/29
Ports
tcp/0
Information about this scan :
Nessus version : 5.2.7
Plugin feed version : 201410070915
Scanner edition used : Nessus Home
Scan policy used : full_interna
Scanner IP : 10.240.5.21
Port scanner(s) : nessus_syn_scanner
Port range : default
Thorough tests : no
Experimental tests : no
Paranoia level : 1
Report Verbosity : 1
Safe checks : yes
Optimize the test : yes
Credentialed checks : no
Patch management checks : None
CGI scanning : disabled
11
0/udp
10287 - Traceroute Information
Synopsis
It was possible to obtain traceroute information.
Description
Makes a traceroute to the remote host.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 1999/11/27, Modification date: 2013/04/11
Ports
udp/0
For your information, here is the traceroute from 10.240.5.21 to 172.29.1.19 :
10.240.5.21
10.240.5.1
172.29.1.19
80/tcp
11219 - Nessus SYN scanner
Synopsis
It is possible to determine which TCP ports are open.
Description
This plugin is a SYN 'half-open' port scanner. It shall be reasonably quick even against a firewalled target.
Note that SYN scans are less intrusive than TCP (full connect) scans against broken services, but they might cause
problems for less robust firewalls and also leave unclosed connections on the remote target, if the network is loaded.
Solution
Protect your target with an IP filter.
Risk Factor
None
Plugin Information:
Publication date: 2009/02/04, Modification date: 2014/01/23
Ports
tcp/80
Port 80/tcp was found to be open
Description
It was possible to identify the remote service by its banner or by looking at the error message it sends when it receives
an HTTP request.
Solution
n/a
12
Risk Factor
None
Plugin Information:
Publication date: 2007/08/19, Modification date: 2014/07/24
Ports
tcp/80
A web server is running on this port.
Description
By calling the OPTIONS method, it is possible to determine which HTTP methods are allowed on each directory.
As this list may be incomplete, the plugin also tests - if 'Thorough tests' are enabled or 'Enable web applications tests'
is set to 'yes'
in the scan policy - various known HTTP methods on each directory and considers them as unsupported if it receives
a response code of 400, 403, 405, or 501.
Note that the plugin output is only informational and does not necessarily indicate the presence of any security
vulnerabilities.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2009/12/10, Modification date: 2013/05/09
Ports
tcp/80
Based on the response to an OPTIONS request :
- HTTP methods
GET
HEAD
POST
Description
This plugin attempts to determine the type and the version of the remote web server.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2000/01/04, Modification date: 2014/08/01
Ports
tcp/80
The remote web server type is :
Microsoft-IIS/7.5
13
Description
This test gives some information about the remote HTTP protocol - the version used, whether HTTP Keep-Alive and
HTTP pipelining are enabled, etc...
This test is informational only and does not denote any security problem.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2007/01/30, Modification date: 2011/05/31
Ports
tcp/80
Protocol version : HTTP/1.1
SSL : no
Keep-Alive : no
Options allowed : OPTIONS, TRACE, GET, HEAD, POST
Headers :
Server: Microsoft-IIS/7.5
Date: Thu, 16 Oct 2014 03:58:09 GMT
Content-Length: 0
139/tcp
11219 - Nessus SYN scanner
Synopsis
It is possible to determine which TCP ports are open.
Description
This plugin is a SYN 'half-open' port scanner. It shall be reasonably quick even against a firewalled target.
Note that SYN scans are less intrusive than TCP (full connect) scans against broken services, but they might cause
problems for less robust firewalls and also leave unclosed connections on the remote target, if the network is loaded.
Solution
Protect your target with an IP filter.
Risk Factor
None
Plugin Information:
Publication date: 2009/02/04, Modification date: 2014/01/23
Ports
tcp/139
Port 139/tcp was found to be open
Description
The remote service understands the CIFS (Common Internet File System) or Server Message Block (SMB) protocol,
used to provide shared access to files, printers, etc between nodes on a network.
Solution
n/a
Risk Factor
None
Plugin Information:
14
Ports
tcp/139
An SMB server is running on this port.
445/tcp
57608 - SMB Signing Required
Synopsis
Signing is not required on the remote SMB server.
Description
Signing is not required on the remote SMB server. This can allow man-in-the-middle attacks against the SMB server.
See Also
http://support.microsoft.com/kb/887429
http://technet.microsoft.com/en-us/library/cc731957.aspx
http://www.nessus.org/u?74b80723
http://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html
http://www.nessus.org/u?a3cac4ea
Solution
Enforce message signing in the host's configuration. On Windows, this is found in the policy setting 'Microsoft network
server:
Digitally sign communications (always)'. On Samba, the setting is called 'server signing'. See the 'see also' links for
further details.
Risk Factor
Medium
Plugin Information:
Publication date: 2012/01/19, Modification date: 2014/08/05
Ports
tcp/445
11219 - Nessus SYN scanner
Synopsis
It is possible to determine which TCP ports are open.
Description
This plugin is a SYN 'half-open' port scanner. It shall be reasonably quick even against a firewalled target.
Note that SYN scans are less intrusive than TCP (full connect) scans against broken services, but they might cause
problems for less robust firewalls and also leave unclosed connections on the remote target, if the network is loaded.
Solution
Protect your target with an IP filter.
Risk Factor
None
Plugin Information:
Publication date: 2009/02/04, Modification date: 2014/01/23
Ports
15
tcp/445
Port 445/tcp was found to be open
Description
The remote service understands the CIFS (Common Internet File System) or Server Message Block (SMB) protocol,
used to provide shared access to files, printers, etc between nodes on a network.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2002/06/05, Modification date: 2012/01/31
Ports
tcp/445
A CIFS server is running on this port.
42410 - Microsoft Windows NTLMSSP Authentication Request Remote Network Name Disclosure
Synopsis
It is possible to obtain the network name of the remote host.
Description
The remote host listens on tcp port 445 and replies to SMB requests.
By sending an NTLMSSP authentication request it is possible to obtain the name of the remote system and the name
of its domain.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2009/11/06, Modification date: 2011/03/27
Ports
tcp/445
The following 2 NetBIOS names have been gathered :
PEHERACOSQ
PERU
= Computer name
= Workgroup / Domain name
Description
It is possible to get the remote operating system name and version (Windows and/or Samba) by sending an
authentication request to port 139 or 445.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2001/10/17, Modification date: 2014/04/09
16
Ports
tcp/445
The remote Operating System is : Windows Server 2008 R2 Enterprise 7601 Service Pack 1
The remote native lan manager is : Windows Server 2008 R2 Enterprise 6.1
The remote SMB Domain Name is : PERU
Description
The remote host is running Microsoft Windows operating system or Samba, a CIFS/SMB server for Unix. It was
possible to log into it using one of the following accounts :
- NULL session
- Guest account
- Given Credentials
See Also
http://support.microsoft.com/kb/143474
http://support.microsoft.com/kb/246261
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2000/05/09, Modification date: 2014/10/06
Ports
tcp/445
- NULL sessions are enabled on the remote host
26917 - Microsoft Windows SMB Registry : Nessus Cannot Access the Windows Registry
Synopsis
Nessus is not able to access the remote Windows Registry.
Description
It was not possible to connect to PIPE\winreg on the remote host.
If you intend to use Nessus to perform registry-based checks, the registry checks will not work because the 'Remote
Registry Access'
service (winreg) has been disabled on the remote host or can not be connected to with the supplied credentials.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2007/10/04, Modification date: 2011/03/27
Ports
tcp/445
Could not connect to the registry because:
Could not connect to \winreg
3389/tcp
58453 - Terminal Services Doesn't Use Network Level Authentication (NLA)
Synopsis
The remote Terminal Services doesn't use Network Level Authentication.
Description
17
The remote Terminal Services is not configured to use Network Level Authentication (NLA). NLA uses the Credential
Security Support Provider (CredSSP) protocol to perform strong server authentication either through TLS/SSL or
Kerberos mechanisms, which protect against man-in-the-middle attacks. In addition to improving authentication, NLA
also helps protect the remote computer from malicious users and software by completing user authentication before a
full RDP connection is established.
See Also
http://technet.microsoft.com/en-us/library/cc732713.aspx
http://www.nessus.org/u?e2628096
Solution
Enable Network Level Authentication (NLA) on the remote RDP server. This is generally done on the 'Remote' tab of
the 'System' settings on Windows.
Risk Factor
Medium
Plugin Information:
Publication date: 2012/03/23, Modification date: 2013/08/05
Ports
tcp/3389
57690 - Terminal Services Encryption Level is Medium or Low
Synopsis
The remote host is using weak cryptography.
Description
The remote Terminal Services service is not configured to use strong cryptography.
Using weak cryptography with this service may allow an attacker to eavesdrop on the communications more easily
and obtain screenshots and/or keystrokes.
Solution
Change RDP encryption level to one of :
3. High
4. FIPS Compliant
Risk Factor
Medium
Plugin Information:
Publication date: 2012/01/25, Modification date: 2014/01/07
Ports
tcp/3389
The terminal services encryption level is set to :
2. Medium
Description
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.
18
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.
See Also
http://www.oxid.it/downloads/rdp-gbu.pdf
http://www.nessus.org/u?e2628096
http://technet.microsoft.com/en-us/library/cc782610.aspx
Solution
- 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.
Risk Factor
Medium
References
BID
13818
CVE
CVE-2005-1794
XREF
OSVDB:17131
Plugin Information:
Publication date: 2005/06/01, Modification date: 2014/03/04
Ports
tcp/3389
30218 - Terminal Services Encryption Level is not FIPS-140 Compliant
Synopsis
The remote host is not FIPS-140 compliant.
Description
The encryption setting used by the remote Terminal Services service is not FIPS-140 compliant.
Solution
Change RDP encryption level to :
4. FIPS Compliant
Risk Factor
Low
Plugin Information:
Publication date: 2008/02/11, Modification date: 2014/01/07
Ports
tcp/3389
The terminal services encryption level is set to :
2. Medium (Client Compatible)
19
Description
This plugin is a SYN 'half-open' port scanner. It shall be reasonably quick even against a firewalled target.
Note that SYN scans are less intrusive than TCP (full connect) scans against broken services, but they might cause
problems for less robust firewalls and also leave unclosed connections on the remote target, if the network is loaded.
Solution
Protect your target with an IP filter.
Risk Factor
None
Plugin Information:
Publication date: 2009/02/04, Modification date: 2014/01/23
Ports
tcp/3389
Port 3389/tcp was found to be open
20
172.29.1.62
Scan Information
Start time:
End time:
Host Information
Netbios Name:
PEHERACOSQ
IP:
172.29.1.62
OS:
Results Summary
Critical
High
Medium
Low
Info
Total
27
34
Results Details
0/icmp
10114 - ICMP Timestamp Request Remote Date Disclosure
Synopsis
It is possible to determine the exact time set on the remote host.
Description
The remote host answers to an ICMP timestamp request. This allows an attacker to know the date that is set on
the targeted machine, which may assist an unauthenticated, remote attacker in defeating time-based authentication
protocols.
Timestamps returned from machines running Windows Vista / 7 / 2008 / 2008 R2 are deliberately incorrect, but
usually within 1000 seconds of the actual system time.
Solution
Filter out the ICMP timestamp requests (13), and the outgoing ICMP timestamp replies (14).
Risk Factor
None
References
CVE
CVE-1999-0524
XREF
OSVDB:94
XREF
CWE:200
Plugin Information:
Publication date: 1999/08/01, Modification date: 2012/06/18
Ports
icmp/0
The ICMP timestamps seem to be in little endian format (not in network format)
The difference between the local and remote clocks is 141 seconds.
0/tcp
24786 - Nessus Windows Scan Not Performed with Admin Privileges
Synopsis
The Nessus scan of this host may be incomplete due to insufficient privileges provided.
Description
The Nessus scanner testing the remote host has been given SMB credentials to log into the remote host, however
these credentials do not have administrative privileges.
21
Typically, when Nessus performs a patch audit, it logs into the remote host and reads the version of the DLLs on
the remote host to determine if a given patch has been applied or not. This is the method Microsoft recommends to
determine if a patch has been applied.
If your Nessus scanner does not have administrative privileges when doing a scan, then Nessus has to fall back to
perform a patch audit through the registry which may lead to false positives (especially when using third-party patch
auditing tools) or to false negatives (not all patches can be detected through the registry).
Solution
Reconfigure your scanner to use credentials with administrative privileges.
Risk Factor
None
Plugin Information:
Publication date: 2007/03/12, Modification date: 2013/01/07
Ports
tcp/0
It was not possible to connect to '\\PEHERACOSQ\ADMIN$' with the supplied credentials.
Description
The remote host implements TCP timestamps, as defined by RFC1323. A side effect of this feature is that the uptime
of the remote host can sometimes be computed.
See Also
http://www.ietf.org/rfc/rfc1323.txt
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2007/05/16, Modification date: 2011/03/20
Ports
tcp/0
11936 - OS Identification
Synopsis
It is possible to guess the remote operating system.
Description
Using a combination of remote probes (TCP/IP, SMB, HTTP, NTP, SNMP, etc...), it is possible to guess the name of
the remote operating system in use. It is also sometimes possible to guess the version of the operating system.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2003/12/09, Modification date: 2014/02/19
Ports
tcp/0
Remote operating system : Microsoft Windows Server 2008 R2 Enterprise Service Pack 1
Confidence Level : 99
Method : MSRPC
22
The remote host is running Microsoft Windows Server 2008 R2 Enterprise Service Pack 1
Description
Based on the remote operating system, it is possible to determine what the remote system type is (eg: a printer,
router, general-purpose computer, etc).
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2011/05/23, Modification date: 2011/05/23
Ports
tcp/0
Remote device type : general-purpose
Confidence level : 99
Description
By using information obtained from a Nessus scan, this plugin reports CPE (Common Platform Enumeration) matches
for various hardware and software products found on a host.
Note that if an official CPE is not available for the product, this plugin computes the best possible CPE based on the
information available from the scan.
See Also
http://cpe.mitre.org/
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2010/04/21, Modification date: 2014/09/19
Ports
tcp/0
The remote operating system matched the following CPE :
cpe:/o:microsoft:windows_server_2008:r2:sp1:enterprise
Following application CPE matched on the remote system :
cpe:/a:microsoft:iis:7.5 -> Microsoft Internet Information Services (IIS) 7.5
Description
The remote host is missing one or several security patches. This plugin lists the newest version of each patch to install
to make sure the remote host is up-to-date.
Solution
23
Risk Factor
None
Plugin Information:
Publication date: 2013/07/08, Modification date: 2014/09/09
Ports
tcp/0
Description
This script displays, for each tested host, information about the scan itself :
- The version of the plugin set
- The type of scanner (Nessus or Nessus Home)
- The version of the Nessus Engine
- The port scanner(s) used
- The port range scanned
- Whether credentialed or third-party patch management checks are possible
- The date of the scan
- The duration of the scan
- The number of hosts scanned in parallel
- The number of checks done in parallel
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2005/08/26, Modification date: 2014/07/29
Ports
tcp/0
Information about this scan :
Nessus version : 5.2.7
Plugin feed version : 201410070915
Scanner edition used : Nessus Home
Scan policy used : full_interna
Scanner IP : 10.240.5.21
Port scanner(s) : nessus_syn_scanner
Port range : default
Thorough tests : no
Experimental tests : no
Paranoia level : 1
Report Verbosity : 1
Safe checks : yes
Optimize the test : yes
Credentialed checks : no
Patch management checks : None
CGI scanning : disabled
24
0/udp
10287 - Traceroute Information
Synopsis
It was possible to obtain traceroute information.
Description
Makes a traceroute to the remote host.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 1999/11/27, Modification date: 2013/04/11
Ports
udp/0
For your information, here is the traceroute from 10.240.5.21 to 172.29.1.62 :
10.240.5.21
10.240.5.1
172.29.1.62
80/tcp
11219 - Nessus SYN scanner
Synopsis
It is possible to determine which TCP ports are open.
Description
This plugin is a SYN 'half-open' port scanner. It shall be reasonably quick even against a firewalled target.
Note that SYN scans are less intrusive than TCP (full connect) scans against broken services, but they might cause
problems for less robust firewalls and also leave unclosed connections on the remote target, if the network is loaded.
Solution
Protect your target with an IP filter.
Risk Factor
None
Plugin Information:
Publication date: 2009/02/04, Modification date: 2014/01/23
Ports
tcp/80
Port 80/tcp was found to be open
Description
It was possible to identify the remote service by its banner or by looking at the error message it sends when it receives
an HTTP request.
Solution
n/a
25
Risk Factor
None
Plugin Information:
Publication date: 2007/08/19, Modification date: 2014/07/24
Ports
tcp/80
A web server is running on this port.
Description
By calling the OPTIONS method, it is possible to determine which HTTP methods are allowed on each directory.
As this list may be incomplete, the plugin also tests - if 'Thorough tests' are enabled or 'Enable web applications tests'
is set to 'yes'
in the scan policy - various known HTTP methods on each directory and considers them as unsupported if it receives
a response code of 400, 403, 405, or 501.
Note that the plugin output is only informational and does not necessarily indicate the presence of any security
vulnerabilities.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2009/12/10, Modification date: 2013/05/09
Ports
tcp/80
Based on the response to an OPTIONS request :
- HTTP methods
GET
HEAD
POST
Description
This plugin attempts to determine the type and the version of the remote web server.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2000/01/04, Modification date: 2014/08/01
Ports
tcp/80
The remote web server type is :
Microsoft-IIS/7.5
26
Description
This test gives some information about the remote HTTP protocol - the version used, whether HTTP Keep-Alive and
HTTP pipelining are enabled, etc...
This test is informational only and does not denote any security problem.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2007/01/30, Modification date: 2011/05/31
Ports
tcp/80
Protocol version : HTTP/1.1
SSL : no
Keep-Alive : no
Options allowed : OPTIONS, TRACE, GET, HEAD, POST
Headers :
Server: Microsoft-IIS/7.5
Date: Thu, 16 Oct 2014 03:58:29 GMT
Content-Length: 0
445/tcp
57608 - SMB Signing Required
Synopsis
Signing is not required on the remote SMB server.
Description
Signing is not required on the remote SMB server. This can allow man-in-the-middle attacks against the SMB server.
See Also
http://support.microsoft.com/kb/887429
http://technet.microsoft.com/en-us/library/cc731957.aspx
http://www.nessus.org/u?74b80723
http://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html
http://www.nessus.org/u?a3cac4ea
Solution
Enforce message signing in the host's configuration. On Windows, this is found in the policy setting 'Microsoft network
server:
Digitally sign communications (always)'. On Samba, the setting is called 'server signing'. See the 'see also' links for
further details.
Risk Factor
Medium
Plugin Information:
Publication date: 2012/01/19, Modification date: 2014/08/05
Ports
tcp/445
27
Description
This plugin is a SYN 'half-open' port scanner. It shall be reasonably quick even against a firewalled target.
Note that SYN scans are less intrusive than TCP (full connect) scans against broken services, but they might cause
problems for less robust firewalls and also leave unclosed connections on the remote target, if the network is loaded.
Solution
Protect your target with an IP filter.
Risk Factor
None
Plugin Information:
Publication date: 2009/02/04, Modification date: 2014/01/23
Ports
tcp/445
Port 445/tcp was found to be open
Description
The remote service understands the CIFS (Common Internet File System) or Server Message Block (SMB) protocol,
used to provide shared access to files, printers, etc between nodes on a network.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2002/06/05, Modification date: 2012/01/31
Ports
tcp/445
A CIFS server is running on this port.
42410 - Microsoft Windows NTLMSSP Authentication Request Remote Network Name Disclosure
Synopsis
It is possible to obtain the network name of the remote host.
Description
The remote host listens on tcp port 445 and replies to SMB requests.
By sending an NTLMSSP authentication request it is possible to obtain the name of the remote system and the name
of its domain.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2009/11/06, Modification date: 2011/03/27
Ports
tcp/445
The following 2 NetBIOS names have been gathered :
28
PEHERACOSQ
PERU
= Computer name
= Workgroup / Domain name
Description
It is possible to get the remote operating system name and version (Windows and/or Samba) by sending an
authentication request to port 139 or 445.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2001/10/17, Modification date: 2014/04/09
Ports
tcp/445
The remote Operating System is : Windows Server 2008 R2 Enterprise 7601 Service Pack 1
The remote native lan manager is : Windows Server 2008 R2 Enterprise 6.1
The remote SMB Domain Name is : PERU
Description
The remote host is running Microsoft Windows operating system or Samba, a CIFS/SMB server for Unix. It was
possible to log into it using one of the following accounts :
- NULL session
- Guest account
- Given Credentials
See Also
http://support.microsoft.com/kb/143474
http://support.microsoft.com/kb/246261
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2000/05/09, Modification date: 2014/10/06
Ports
tcp/445
- NULL sessions are enabled on the remote host
26917 - Microsoft Windows SMB Registry : Nessus Cannot Access the Windows Registry
Synopsis
Nessus is not able to access the remote Windows Registry.
Description
It was not possible to connect to PIPE\winreg on the remote host.
If you intend to use Nessus to perform registry-based checks, the registry checks will not work because the 'Remote
Registry Access'
service (winreg) has been disabled on the remote host or can not be connected to with the supplied credentials.
Solution
29
n/a
Risk Factor
None
Plugin Information:
Publication date: 2007/10/04, Modification date: 2011/03/27
Ports
tcp/445
Could not connect to the registry because:
Could not connect to IPC$
3389/tcp
51192 - SSL Certificate Cannot Be Trusted
Synopsis
The SSL certificate for this service cannot be trusted.
Description
The server's X.509 certificate does not have a signature from a known public certificate authority. This situation can
occur in three different ways, each of which results in a break in the chain below which certificates cannot be trusted.
First, the top of the certificate chain sent by the server might not be descended from a known public certificate
authority. This can occur either when the top of the chain is an unrecognized, self-signed certificate, or when
intermediate certificates are missing that would connect the top of the certificate chain to a known public certificate
authority.
Second, the certificate chain may contain a certificate that is not valid at the time of the scan. This can occur either
when the scan occurs before one of the certificate's 'notBefore' dates, or after one of the certificate's 'notAfter' dates.
Third, the certificate chain may contain a signature that either didn't match the certificate's information, or could not
be verified. Bad signatures can be fixed by getting the certificate with the bad signature to be re-signed by its issuer.
Signatures that could not be verified are the result of the certificate's issuer using a signing algorithm that Nessus
either does not support or does not recognize.
If the remote host is a public host in production, any break in the chain makes it more difficult for users to verify the
authenticity and identity of the web server. This could make it easier to carry out man-in-the-middle attacks against the
remote host.
Solution
Purchase or generate a proper certificate for this service.
Risk Factor
Medium
Plugin Information:
Publication date: 2010/12/15, Modification date: 2014/02/27
Ports
tcp/3389
The following certificate was at the top of the certificate
chain sent by the remote host, but is signed by an unknown
certificate authority :
|-Subject : CN=PEHERACOSQ.PERU.FSM.CORP
|-Issuer : CN=PEHERACOSQ.PERU.FSM.CORP
Description
The X.509 certificate chain for this service is not signed by a recognized certificate authority. If the remote host is a
public host in production, this nullifies the use of SSL as anyone could establish a man-in-the-middle attack against
the remote host.
30
Note that this plugin does not check for certificate chains that end in a certificate that is not self-signed, but is signed
by an unrecognized certificate authority.
Solution
Purchase or generate a proper certificate for this service.
Risk Factor
Medium
Plugin Information:
Publication date: 2012/01/17, Modification date: 2012/10/25
Ports
tcp/3389
The following certificate was found at the top of the certificate
chain sent by the remote host, but is self-signed and was not
found in the list of known certificate authorities :
|-Subject : CN=PEHERACOSQ.PERU.FSM.CORP
Description
The remote Terminal Services is not configured to use Network Level Authentication (NLA). NLA uses the Credential
Security Support Provider (CredSSP) protocol to perform strong server authentication either through TLS/SSL or
Kerberos mechanisms, which protect against man-in-the-middle attacks. In addition to improving authentication, NLA
also helps protect the remote computer from malicious users and software by completing user authentication before a
full RDP connection is established.
See Also
http://technet.microsoft.com/en-us/library/cc732713.aspx
http://www.nessus.org/u?e2628096
Solution
Enable Network Level Authentication (NLA) on the remote RDP server. This is generally done on the 'Remote' tab of
the 'System' settings on Windows.
Risk Factor
Medium
Plugin Information:
Publication date: 2012/03/23, Modification date: 2013/08/05
Ports
tcp/3389
57690 - Terminal Services Encryption Level is Medium or Low
Synopsis
The remote host is using weak cryptography.
Description
The remote Terminal Services service is not configured to use strong cryptography.
Using weak cryptography with this service may allow an attacker to eavesdrop on the communications more easily
and obtain screenshots and/or keystrokes.
Solution
Change RDP encryption level to one of :
31
3. High
4. FIPS Compliant
Risk Factor
Medium
Plugin Information:
Publication date: 2012/01/25, Modification date: 2014/01/07
Ports
tcp/3389
The terminal services encryption level is set to :
2. Medium
Description
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.
See Also
http://www.oxid.it/downloads/rdp-gbu.pdf
http://www.nessus.org/u?e2628096
http://technet.microsoft.com/en-us/library/cc782610.aspx
Solution
- 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.
Risk Factor
Medium
References
BID
13818
CVE
CVE-2005-1794
XREF
OSVDB:17131
Plugin Information:
Publication date: 2005/06/01, Modification date: 2014/03/04
Ports
tcp/3389
30218 - Terminal Services Encryption Level is not FIPS-140 Compliant
32
Synopsis
The remote host is not FIPS-140 compliant.
Description
The encryption setting used by the remote Terminal Services service is not FIPS-140 compliant.
Solution
Change RDP encryption level to :
4. FIPS Compliant
Risk Factor
Low
Plugin Information:
Publication date: 2008/02/11, Modification date: 2014/01/07
Ports
tcp/3389
The terminal services encryption level is set to :
2. Medium (Client Compatible)
Description
This plugin is a SYN 'half-open' port scanner. It shall be reasonably quick even against a firewalled target.
Note that SYN scans are less intrusive than TCP (full connect) scans against broken services, but they might cause
problems for less robust firewalls and also leave unclosed connections on the remote target, if the network is loaded.
Solution
Protect your target with an IP filter.
Risk Factor
None
Plugin Information:
Publication date: 2009/02/04, Modification date: 2014/01/23
Ports
tcp/3389
Port 3389/tcp was found to be open
Description
Terminal Services allows a Windows user to remotely obtain a graphical login (and therefore act as a local user on the
remote host).
If an attacker gains a valid login and password, this service could be used to gain further access on the remote host.
An attacker may also use this service to mount a dictionary attack against the remote host to try to log in remotely.
Note that RDP (the Remote Desktop Protocol) is vulnerable to Man-in-the-middle attacks, making it easy for attackers
to steal the credentials of legitimate users by impersonating the Windows server.
Solution
Disable Terminal Services if you do not use it, and do not allow this service to run across the Internet.
Risk Factor
None
33
Plugin Information:
Publication date: 2002/04/20, Modification date: 2014/06/06
Ports
tcp/3389
66173 - RDP Screenshot
Synopsis
It is possible to take a screenshot of the remote login screen.
Description
This script attempts to connect to the remote host via RDP (Remote Desktop Protocol) and attempts to take a
screenshot of the login screen.
While this is not a vulnerability by itself, some versions of Windows display the names of the users who can connect
and which ones are connected already.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2013/04/22, Modification date: 2014/01/07
Ports
tcp/3389
It was possible to gather the following screenshot of the remote login screen.
Description
The remote Terminal Services is configured to use SSL/TLS.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2013/02/22, Modification date: 2013/08/28
Ports
tcp/3389
Subject Name:
Common Name: PEHERACOSQ.PERU.FSM.CORP
Issuer Name:
Common Name: PEHERACOSQ.PERU.FSM.CORP
Serial Number: 52 33 A3 A9 BD 58 B5 A0 42 D2 EA 6C 80 78 16 EC
Version: 3
Signature Algorithm: SHA-1 With RSA Encryption
Not Valid Before: Jul 18 17:48:29 2014 GMT
Not Valid After: Jan 17 17:48:29 2015 GMT
Public Key Info:
Algorithm: RSA Encryption
Key Length: 2048 bits
Public Key: 00 B6 4A D1 D6 B5 C1 1B EE 15 B1 D3 2F 21 24 8B 04 07 0E 2D
34
58 29 52
26 E9 64
E0 83 56
5B C9 A6
F8 BF 88
99 D5 DD
D2 AC 0E
2F 80 71
DB 73 DA
89 66 23
FA C9 16
4D 24 43
Exponent: 01 00 01
E5
47
36
BA
31
5E
F3
1E
0C
A5
DB
0B
EE
C3
26
1A
61
49
64
4F
A7
36
26
65
D1
2D
6F
4D
F8
35
A8
64
C5
C3
BD
0E
0E
6B
7A
AA
AC
89
14
7D
48
CE
24
07
3A
B7
48
BE
64
66
53
E8
D2
88
65
79
46
A9
25
83
90
E0
FA
2A
E6
4F
79
FC
AA
E9
44
09
1C
B3
A1
D8
45
D4
72
BE
bits
1F 36
1C 24
2F 04
8C C1
DE 65
F5 75
47 8C
85 51
99 A9
7E
14
47
31
18
17
86
CC
BD
00
32
24
42
AB
2A
F5
BD
FB
C4
54
C1
BA
55
1E
86
BE
C0
23
6B
F6
E9
2F
25
75
D3
AE
87
14
44
D8
C5
03
BC
41
5D
B6
AE
7F
CA
9A
F0
C0
70
2C
0E
27
A9
CE
56
EF
37
91
F6
8D
AE
E9
1D
1E
BE
ED
26
42
92
3A
26
70
B8
00
1D
24
2F
52
C7
88
4D
1C
4B
12
8C
6D
7E
C9
31
99
25
FF
0C
5E
1D
48
83
AE
C9
55
99
D8
ED
E9
60
11
BB
FB
B7
06
EE
96
1A
37
32
E3
29
C5
6F
F3
55
D3
39
A9
93
0B
5F
E4
7F
21
F1
B0
C3
27
A0
AB
95
8E
F3
ED
EE
FE
9D
52
96
C0
4D
15
87
32
09
B3
5D
54
FD
4D
2B
A6
36
04
F1
28
77
10
CD
F3
FB
E8
85
B3
3C
05
AB
D6
CE
C8
ED
82
84
7B
2D
74
2A
4C
E2
DD
FD
69
E0
F0
F0
2D
56
F2
64
6D
72
64
B0
D9
54
52
30
Description
This script detects which SSL and TLS versions are supported by the remote service for encrypting communications.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2011/12/01, Modification date: 2014/04/14
Ports
tcp/3389
This port supports TLSv1.0.
Description
This plugin connects to every SSL-related port and attempts to extract and dump the X.509 certificate.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2008/05/19, Modification date: 2012/04/02
Ports
tcp/3389
Subject Name:
Common Name: PEHERACOSQ.PERU.FSM.CORP
Issuer Name:
35
B5
D1
2D
6F
4D
F8
35
A8
64
C5
C3
BD
0E
C1
0E
6B
7A
AA
AC
89
14
7D
48
CE
24
07
1B
3A
B7
48
BE
64
66
53
E8
D2
88
65
79
EE
46
A9
25
83
90
E0
FA
2A
E6
4F
79
FC
15
AA
E9
44
09
1C
B3
A1
D8
45
D4
72
BE
bits
1F 36
1C 24
2F 04
8C C1
DE 65
F5 75
47 8C
85 51
99 A9
B1
7E
14
47
31
18
17
86
CC
BD
00
32
24
42
AB
2A
F5
BD
FB
C4
54
C1
D3
BA
55
1E
86
BE
C0
23
6B
F6
E9
2F
25
75
D3
AE
87
14
44
D8
C5
03
2F
BC
41
5D
B6
AE
7F
CA
9A
F0
C0
70
2C
0E
27
A9
CE
56
EF
37
91
F6
21
8D
AE
E9
1D
1E
BE
ED
26
42
92
3A
26
70
B8
00
1D
24
2F
52
C7
88
24
4D
1C
4B
12
8C
6D
7E
C9
31
99
25
FF
0C
5E
1D
48
83
AE
C9
55
99
8B
D8
ED
E9
60
11
BB
FB
B7
06
EE
96
1A
37
32
E3
29
C5
6F
F3
55
D3
04
39
A9
93
0B
5F
E4
7F
21
F1
B0
C3
27
A0
AB
95
8E
F3
ED
EE
FE
9D
07
52
96
C0
4D
15
87
32
09
B3
5D
54
FD
4D
2B
A6
36
04
F1
28
77
0E
10
CD
F3
FB
E8
85
B3
3C
05
AB
D6
CE
C8
ED
82
84
7B
2D
74
2A
2D
4C
E2
DD
FD
69
E0
F0
F0
2D
56
F2
64
6D
72
64
B0
D9
54
52
30
Description
This service presents an SSL certificate for which the 'commonName'
(CN) does not match the host name on which the service listens.
Solution
If the machine has several names, make sure that users connect to the service through the DNS host name that
matches the common name in the certificate.
Risk Factor
None
Plugin Information:
Publication date: 2010/04/03, Modification date: 2012/09/30
Ports
tcp/3389
The host name known by Nessus is :
peheracosq
The Common Name in the certificate is :
peheracosq.peru.fsm.corp
36
Vulnerabilities By Plugin
18405 (2) - Microsoft Windows Remote Desktop Protocol Server Man-in-the-Middle Weakness
Synopsis
It may be possible to get access to the remote host.
Description
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.
See Also
http://www.oxid.it/downloads/rdp-gbu.pdf
http://www.nessus.org/u?e2628096
http://technet.microsoft.com/en-us/library/cc782610.aspx
Solution
- 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.
Risk Factor
Medium
References
BID
13818
CVE
CVE-2005-1794
XREF
OSVDB:17131
Plugin Information:
Publication date: 2005/06/01, Modification date: 2014/03/04
Hosts
172.29.1.19 (tcp/3389)
172.29.1.62 (tcp/3389)
38
Description
Signing is not required on the remote SMB server. This can allow man-in-the-middle attacks against the SMB server.
See Also
http://support.microsoft.com/kb/887429
http://technet.microsoft.com/en-us/library/cc731957.aspx
http://www.nessus.org/u?74b80723
http://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html
http://www.nessus.org/u?a3cac4ea
Solution
Enforce message signing in the host's configuration. On Windows, this is found in the policy setting 'Microsoft network
server:
Digitally sign communications (always)'. On Samba, the setting is called 'server signing'. See the 'see also' links for
further details.
Risk Factor
Medium
Plugin Information:
Publication date: 2012/01/19, Modification date: 2014/08/05
Hosts
172.29.1.19 (tcp/445)
172.29.1.62 (tcp/445)
39
Description
The remote Terminal Services service is not configured to use strong cryptography.
Using weak cryptography with this service may allow an attacker to eavesdrop on the communications more easily
and obtain screenshots and/or keystrokes.
Solution
Change RDP encryption level to one of :
3. High
4. FIPS Compliant
Risk Factor
Medium
Plugin Information:
Publication date: 2012/01/25, Modification date: 2014/01/07
Hosts
172.29.1.19 (tcp/3389)
The terminal services encryption level is set to :
2. Medium
172.29.1.62 (tcp/3389)
The terminal services encryption level is set to :
2. Medium
40
58453 (2) - Terminal Services Doesn't Use Network Level Authentication (NLA)
Synopsis
The remote Terminal Services doesn't use Network Level Authentication.
Description
The remote Terminal Services is not configured to use Network Level Authentication (NLA). NLA uses the Credential
Security Support Provider (CredSSP) protocol to perform strong server authentication either through TLS/SSL or
Kerberos mechanisms, which protect against man-in-the-middle attacks. In addition to improving authentication, NLA
also helps protect the remote computer from malicious users and software by completing user authentication before a
full RDP connection is established.
See Also
http://technet.microsoft.com/en-us/library/cc732713.aspx
http://www.nessus.org/u?e2628096
Solution
Enable Network Level Authentication (NLA) on the remote RDP server. This is generally done on the 'Remote' tab of
the 'System' settings on Windows.
Risk Factor
Medium
Plugin Information:
Publication date: 2012/03/23, Modification date: 2013/08/05
Hosts
172.29.1.19 (tcp/3389)
172.29.1.62 (tcp/3389)
41
Description
The server's X.509 certificate does not have a signature from a known public certificate authority. This situation can
occur in three different ways, each of which results in a break in the chain below which certificates cannot be trusted.
First, the top of the certificate chain sent by the server might not be descended from a known public certificate
authority. This can occur either when the top of the chain is an unrecognized, self-signed certificate, or when
intermediate certificates are missing that would connect the top of the certificate chain to a known public certificate
authority.
Second, the certificate chain may contain a certificate that is not valid at the time of the scan. This can occur either
when the scan occurs before one of the certificate's 'notBefore' dates, or after one of the certificate's 'notAfter' dates.
Third, the certificate chain may contain a signature that either didn't match the certificate's information, or could not
be verified. Bad signatures can be fixed by getting the certificate with the bad signature to be re-signed by its issuer.
Signatures that could not be verified are the result of the certificate's issuer using a signing algorithm that Nessus
either does not support or does not recognize.
If the remote host is a public host in production, any break in the chain makes it more difficult for users to verify the
authenticity and identity of the web server. This could make it easier to carry out man-in-the-middle attacks against the
remote host.
Solution
Purchase or generate a proper certificate for this service.
Risk Factor
Medium
Plugin Information:
Publication date: 2010/12/15, Modification date: 2014/02/27
Hosts
172.29.1.62 (tcp/3389)
The following certificate was at the top of the certificate
chain sent by the remote host, but is signed by an unknown
certificate authority :
|-Subject : CN=PEHERACOSQ.PERU.FSM.CORP
|-Issuer : CN=PEHERACOSQ.PERU.FSM.CORP
42
Description
The X.509 certificate chain for this service is not signed by a recognized certificate authority. If the remote host is a
public host in production, this nullifies the use of SSL as anyone could establish a man-in-the-middle attack against
the remote host.
Note that this plugin does not check for certificate chains that end in a certificate that is not self-signed, but is signed
by an unrecognized certificate authority.
Solution
Purchase or generate a proper certificate for this service.
Risk Factor
Medium
Plugin Information:
Publication date: 2012/01/17, Modification date: 2012/10/25
Hosts
172.29.1.62 (tcp/3389)
The following certificate was found at the top of the certificate
chain sent by the remote host, but is self-signed and was not
found in the list of known certificate authorities :
|-Subject : CN=PEHERACOSQ.PERU.FSM.CORP
43
Description
The encryption setting used by the remote Terminal Services service is not FIPS-140 compliant.
Solution
Change RDP encryption level to :
4. FIPS Compliant
Risk Factor
Low
Plugin Information:
Publication date: 2008/02/11, Modification date: 2014/01/07
Hosts
172.29.1.19 (tcp/3389)
The terminal services encryption level is set to :
2. Medium (Client Compatible)
172.29.1.62 (tcp/3389)
The terminal services encryption level is set to :
2. Medium (Client Compatible)
44
Description
This plugin is a SYN 'half-open' port scanner. It shall be reasonably quick even against a firewalled target.
Note that SYN scans are less intrusive than TCP (full connect) scans against broken services, but they might cause
problems for less robust firewalls and also leave unclosed connections on the remote target, if the network is loaded.
Solution
Protect your target with an IP filter.
Risk Factor
None
Plugin Information:
Publication date: 2009/02/04, Modification date: 2014/01/23
Hosts
172.29.1.19 (tcp/80)
Port 80/tcp was found to be open
172.29.1.19 (tcp/139)
Port 139/tcp was found to be open
172.29.1.19 (tcp/445)
Port 445/tcp was found to be open
172.29.1.19 (tcp/3389)
Port 3389/tcp was found to be open
172.29.1.62 (tcp/80)
Port 80/tcp was found to be open
172.29.1.62 (tcp/445)
Port 445/tcp was found to be open
172.29.1.62 (tcp/3389)
Port 3389/tcp was found to be open
45
Description
The remote service understands the CIFS (Common Internet File System) or Server Message Block (SMB) protocol,
used to provide shared access to files, printers, etc between nodes on a network.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2002/06/05, Modification date: 2012/01/31
Hosts
172.29.1.19 (tcp/139)
An SMB server is running on this port.
172.29.1.19 (tcp/445)
A CIFS server is running on this port.
172.29.1.62 (tcp/445)
A CIFS server is running on this port.
46
Description
This plugin attempts to determine the type and the version of the remote web server.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2000/01/04, Modification date: 2014/08/01
Hosts
172.29.1.19 (tcp/80)
The remote web server type is :
Microsoft-IIS/7.5
172.29.1.62 (tcp/80)
The remote web server type is :
Microsoft-IIS/7.5
47
Description
The remote host answers to an ICMP timestamp request. This allows an attacker to know the date that is set on
the targeted machine, which may assist an unauthenticated, remote attacker in defeating time-based authentication
protocols.
Timestamps returned from machines running Windows Vista / 7 / 2008 / 2008 R2 are deliberately incorrect, but
usually within 1000 seconds of the actual system time.
Solution
Filter out the ICMP timestamp requests (13), and the outgoing ICMP timestamp replies (14).
Risk Factor
None
References
CVE
CVE-1999-0524
XREF
OSVDB:94
XREF
CWE:200
Plugin Information:
Publication date: 1999/08/01, Modification date: 2012/06/18
Hosts
172.29.1.19 (icmp/0)
The ICMP timestamps seem to be in little endian format (not in network format)
The difference between the local and remote clocks is 172 seconds.
172.29.1.62 (icmp/0)
The ICMP timestamps seem to be in little endian format (not in network format)
The difference between the local and remote clocks is 141 seconds.
48
Description
Makes a traceroute to the remote host.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 1999/11/27, Modification date: 2013/04/11
Hosts
172.29.1.19 (udp/0)
For your information, here is the traceroute from 10.240.5.21 to 172.29.1.19 :
10.240.5.21
10.240.5.1
172.29.1.19
172.29.1.62 (udp/0)
For your information, here is the traceroute from 10.240.5.21 to 172.29.1.62 :
10.240.5.21
10.240.5.1
172.29.1.62
49
Description
The remote host is running Microsoft Windows operating system or Samba, a CIFS/SMB server for Unix. It was
possible to log into it using one of the following accounts :
- NULL session
- Guest account
- Given Credentials
See Also
http://support.microsoft.com/kb/143474
http://support.microsoft.com/kb/246261
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2000/05/09, Modification date: 2014/10/06
Hosts
172.29.1.19 (tcp/445)
- NULL sessions are enabled on the remote host
172.29.1.62 (tcp/445)
- NULL sessions are enabled on the remote host
50
10785 (2) - Microsoft Windows SMB NativeLanManager Remote System Information Disclosure
Synopsis
It is possible to obtain information about the remote operating system.
Description
It is possible to get the remote operating system name and version (Windows and/or Samba) by sending an
authentication request to port 139 or 445.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2001/10/17, Modification date: 2014/04/09
Hosts
172.29.1.19 (tcp/445)
The remote Operating System is : Windows Server 2008 R2 Enterprise 7601 Service Pack 1
The remote native lan manager is : Windows Server 2008 R2 Enterprise 6.1
The remote SMB Domain Name is : PERU
172.29.1.62 (tcp/445)
The remote Operating System is : Windows Server 2008 R2 Enterprise 7601 Service Pack 1
The remote native lan manager is : Windows Server 2008 R2 Enterprise 6.1
The remote SMB Domain Name is : PERU
51
Description
Using a combination of remote probes (TCP/IP, SMB, HTTP, NTP, SNMP, etc...), it is possible to guess the name of
the remote operating system in use. It is also sometimes possible to guess the version of the operating system.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2003/12/09, Modification date: 2014/02/19
Hosts
172.29.1.19 (tcp/0)
Remote operating system : Microsoft Windows Server 2008 R2
Confidence Level : 75
Method : HTTP
172.29.1.62 (tcp/0)
Remote operating system : Microsoft Windows Server 2008 R2 Enterprise Service Pack 1
Confidence Level : 99
Method : MSRPC
The remote host is running Microsoft Windows Server 2008 R2 Enterprise Service Pack 1
52
Description
This script displays, for each tested host, information about the scan itself :
- The version of the plugin set
- The type of scanner (Nessus or Nessus Home)
- The version of the Nessus Engine
- The port scanner(s) used
- The port range scanned
- Whether credentialed or third-party patch management checks are possible
- The date of the scan
- The duration of the scan
- The number of hosts scanned in parallel
- The number of checks done in parallel
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2005/08/26, Modification date: 2014/07/29
Hosts
172.29.1.19 (tcp/0)
Information about this scan :
Nessus version : 5.2.7
Plugin feed version : 201410070915
Scanner edition used : Nessus Home
Scan policy used : full_interna
Scanner IP : 10.240.5.21
Port scanner(s) : nessus_syn_scanner
Port range : default
Thorough tests : no
Experimental tests : no
Paranoia level : 1
Report Verbosity : 1
Safe checks : yes
Optimize the test : yes
Credentialed checks : no
Patch management checks : None
CGI scanning : disabled
Web application tests : disabled
Max hosts : 80
Max checks : 5
Recv timeout : 5
Backports : None
Allow post-scan editing: Yes
Scan Start Date : 2014/10/15 23:00 SA Pacific Standard Time
Scan duration : 251 sec
172.29.1.62 (tcp/0)
Information about this scan :
Nessus version : 5.2.7
Plugin feed version : 201410070915
Scanner edition used : Nessus Home
Scan policy used : full_interna
Scanner IP : 10.240.5.21
Port scanner(s) : nessus_syn_scanner
Port range : default
Thorough tests : no
Experimental tests : no
Paranoia level : 1
53
Report Verbosity : 1
Safe checks : yes
Optimize the test : yes
Credentialed checks : no
Patch management checks : None
CGI scanning : disabled
Web application tests : disabled
Max hosts : 80
Max checks : 5
Recv timeout : 5
Backports : None
Allow post-scan editing: Yes
Scan Start Date : 2014/10/15 23:00 SA Pacific Standard Time
Scan duration : 266 sec
54
Description
It was possible to identify the remote service by its banner or by looking at the error message it sends when it receives
an HTTP request.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2007/08/19, Modification date: 2014/07/24
Hosts
172.29.1.19 (tcp/80)
A web server is running on this port.
172.29.1.62 (tcp/80)
A web server is running on this port.
55
Description
This test gives some information about the remote HTTP protocol - the version used, whether HTTP Keep-Alive and
HTTP pipelining are enabled, etc...
This test is informational only and does not denote any security problem.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2007/01/30, Modification date: 2011/05/31
Hosts
172.29.1.19 (tcp/80)
Protocol version : HTTP/1.1
SSL : no
Keep-Alive : no
Options allowed : OPTIONS, TRACE, GET, HEAD, POST
Headers :
Server: Microsoft-IIS/7.5
Date: Thu, 16 Oct 2014 03:58:09 GMT
Content-Length: 0
172.29.1.62 (tcp/80)
Protocol version : HTTP/1.1
SSL : no
Keep-Alive : no
Options allowed : OPTIONS, TRACE, GET, HEAD, POST
Headers :
Server: Microsoft-IIS/7.5
Date: Thu, 16 Oct 2014 03:58:29 GMT
Content-Length: 0
56
24786 (2) - Nessus Windows Scan Not Performed with Admin Privileges
Synopsis
The Nessus scan of this host may be incomplete due to insufficient privileges provided.
Description
The Nessus scanner testing the remote host has been given SMB credentials to log into the remote host, however
these credentials do not have administrative privileges.
Typically, when Nessus performs a patch audit, it logs into the remote host and reads the version of the DLLs on
the remote host to determine if a given patch has been applied or not. This is the method Microsoft recommends to
determine if a patch has been applied.
If your Nessus scanner does not have administrative privileges when doing a scan, then Nessus has to fall back to
perform a patch audit through the registry which may lead to false positives (especially when using third-party patch
auditing tools) or to false negatives (not all patches can be detected through the registry).
Solution
Reconfigure your scanner to use credentials with administrative privileges.
Risk Factor
None
Plugin Information:
Publication date: 2007/03/12, Modification date: 2013/01/07
Hosts
172.29.1.19 (tcp/0)
It was not possible to connect to '\\PEHERACOSQ\ADMIN$' with the supplied credentials.
172.29.1.62 (tcp/0)
It was not possible to connect to '\\PEHERACOSQ\ADMIN$' with the supplied credentials.
57
Description
The remote host implements TCP timestamps, as defined by RFC1323. A side effect of this feature is that the uptime
of the remote host can sometimes be computed.
See Also
http://www.ietf.org/rfc/rfc1323.txt
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2007/05/16, Modification date: 2011/03/20
Hosts
172.29.1.19 (tcp/0)
172.29.1.62 (tcp/0)
58
26917 (2) - Microsoft Windows SMB Registry : Nessus Cannot Access the Windows Registry
Synopsis
Nessus is not able to access the remote Windows Registry.
Description
It was not possible to connect to PIPE\winreg on the remote host.
If you intend to use Nessus to perform registry-based checks, the registry checks will not work because the 'Remote
Registry Access'
service (winreg) has been disabled on the remote host or can not be connected to with the supplied credentials.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2007/10/04, Modification date: 2011/03/27
Hosts
172.29.1.19 (tcp/445)
Could not connect to the registry because:
Could not connect to \winreg
172.29.1.62 (tcp/445)
Could not connect to the registry because:
Could not connect to IPC$
59
42410 (2) - Microsoft Windows NTLMSSP Authentication Request Remote Network Name Disclosure
Synopsis
It is possible to obtain the network name of the remote host.
Description
The remote host listens on tcp port 445 and replies to SMB requests.
By sending an NTLMSSP authentication request it is possible to obtain the name of the remote system and the name
of its domain.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2009/11/06, Modification date: 2011/03/27
Hosts
172.29.1.19 (tcp/445)
The following 2 NetBIOS names have been gathered :
PEHERACOSQ
PERU
= Computer name
= Workgroup / Domain name
172.29.1.62 (tcp/445)
The following 2 NetBIOS names have been gathered :
PEHERACOSQ
PERU
= Computer name
= Workgroup / Domain name
60
Description
By calling the OPTIONS method, it is possible to determine which HTTP methods are allowed on each directory.
As this list may be incomplete, the plugin also tests - if 'Thorough tests' are enabled or 'Enable web applications tests'
is set to 'yes'
in the scan policy - various known HTTP methods on each directory and considers them as unsupported if it receives
a response code of 400, 403, 405, or 501.
Note that the plugin output is only informational and does not necessarily indicate the presence of any security
vulnerabilities.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2009/12/10, Modification date: 2013/05/09
Hosts
172.29.1.19 (tcp/80)
Based on the response to an OPTIONS request :
- HTTP methods
GET
HEAD
POST
172.29.1.62 (tcp/80)
Based on the response to an OPTIONS request :
- HTTP methods
GET
HEAD
POST
61
Description
By using information obtained from a Nessus scan, this plugin reports CPE (Common Platform Enumeration) matches
for various hardware and software products found on a host.
Note that if an official CPE is not available for the product, this plugin computes the best possible CPE based on the
information available from the scan.
See Also
http://cpe.mitre.org/
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2010/04/21, Modification date: 2014/09/19
Hosts
172.29.1.19 (tcp/0)
The remote operating system matched the following CPE :
cpe:/o:microsoft:windows_server_2008:r2 -> Microsoft Windows Server 2008 R2
Following application CPE matched on the remote system :
cpe:/a:microsoft:iis:7.5 -> Microsoft Internet Information Services (IIS) 7.5
172.29.1.62 (tcp/0)
The remote operating system matched the following CPE :
cpe:/o:microsoft:windows_server_2008:r2:sp1:enterprise
Following application CPE matched on the remote system :
cpe:/a:microsoft:iis:7.5 -> Microsoft Internet Information Services (IIS) 7.5
62
Description
Based on the remote operating system, it is possible to determine what the remote system type is (eg: a printer,
router, general-purpose computer, etc).
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2011/05/23, Modification date: 2011/05/23
Hosts
172.29.1.19 (tcp/0)
Remote device type : general-purpose
Confidence level : 75
172.29.1.62 (tcp/0)
Remote device type : general-purpose
Confidence level : 99
63
Description
The remote host is missing one or several security patches. This plugin lists the newest version of each patch to install
to make sure the remote host is up-to-date.
Solution
Install the patches listed below.
Risk Factor
None
Plugin Information:
Publication date: 2013/07/08, Modification date: 2014/09/09
Hosts
172.29.1.19 (tcp/0)
172.29.1.62 (tcp/0)
64
Description
This plugin connects to every SSL-related port and attempts to extract and dump the X.509 certificate.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2008/05/19, Modification date: 2012/04/02
Hosts
172.29.1.62 (tcp/3389)
Subject Name:
Common Name: PEHERACOSQ.PERU.FSM.CORP
Issuer Name:
Common Name: PEHERACOSQ.PERU.FSM.CORP
Serial Number: 52 33 A3 A9 BD 58 B5 A0 42 D2 EA 6C 80 78 16 EC
Version: 3
Signature Algorithm: SHA-1 With RSA Encryption
Not Valid Before: Jul 18 17:48:29 2014 GMT
Not Valid After: Jan 17 17:48:29 2015 GMT
Public Key Info:
Algorithm: RSA Encryption
Key Length: 2048 bits
Public Key: 00 B6 4A D1 D6
58 29 52 E5 EE
26 E9 64 47 C3
E0 83 56 36 26
5B C9 A6 BA 1A
F8 BF 88 31 61
99 D5 DD 5E 49
D2 AC 0E F3 64
2F 80 71 1E 4F
DB 73 DA 0C A7
89 66 23 A5 36
FA C9 16 DB 26
4D 24 43 0B 65
Exponent: 01 00 01
B5
D1
2D
6F
4D
F8
35
A8
64
C5
C3
BD
0E
C1
0E
6B
7A
AA
AC
89
14
7D
48
CE
24
07
1B
3A
B7
48
BE
64
66
53
E8
D2
88
65
79
EE
46
A9
25
83
90
E0
FA
2A
E6
4F
79
FC
15
AA
E9
44
09
1C
B3
A1
D8
45
D4
72
BE
bits
1F 36
1C 24
2F 04
8C C1
DE 65
F5 75
47 8C
85 51
99 A9
B1
7E
14
47
31
18
17
86
CC
BD
00
32
24
42
AB
2A
F5
BD
FB
C4
54
C1
D3
BA
55
1E
86
BE
C0
23
6B
F6
E9
2F
25
75
D3
AE
87
14
44
D8
C5
03
2F
BC
41
5D
B6
AE
7F
CA
9A
F0
C0
70
2C
0E
27
A9
CE
56
EF
37
91
F6
21
8D
AE
E9
1D
1E
BE
ED
26
42
92
3A
26
70
B8
00
1D
24
2F
52
C7
88
24
4D
1C
4B
12
8C
6D
7E
C9
31
99
25
FF
0C
5E
1D
48
83
AE
C9
55
99
8B
D8
ED
E9
60
11
BB
FB
B7
06
EE
96
1A
37
32
E3
29
C5
6F
F3
55
D3
04
39
A9
93
0B
5F
E4
7F
21
F1
B0
C3
27
A0
AB
95
8E
F3
ED
EE
FE
9D
07
52
96
C0
4D
15
87
32
09
B3
5D
54
FD
4D
2B
A6
36
04
F1
28
77
0E
10
CD
F3
FB
E8
85
B3
3C
05
AB
D6
CE
C8
ED
82
84
7B
2D
74
2A
2D
4C
E2
DD
FD
69
E0
F0
F0
2D
56
F2
64
6D
72
64
B0
D9
54
52
30
65
Description
Terminal Services allows a Windows user to remotely obtain a graphical login (and therefore act as a local user on the
remote host).
If an attacker gains a valid login and password, this service could be used to gain further access on the remote host.
An attacker may also use this service to mount a dictionary attack against the remote host to try to log in remotely.
Note that RDP (the Remote Desktop Protocol) is vulnerable to Man-in-the-middle attacks, making it easy for attackers
to steal the credentials of legitimate users by impersonating the Windows server.
Solution
Disable Terminal Services if you do not use it, and do not allow this service to run across the Internet.
Risk Factor
None
Plugin Information:
Publication date: 2002/04/20, Modification date: 2014/06/06
Hosts
172.29.1.62 (tcp/3389)
66
Description
This service presents an SSL certificate for which the 'commonName'
(CN) does not match the host name on which the service listens.
Solution
If the machine has several names, make sure that users connect to the service through the DNS host name that
matches the common name in the certificate.
Risk Factor
None
Plugin Information:
Publication date: 2010/04/03, Modification date: 2012/09/30
Hosts
172.29.1.62 (tcp/3389)
The host name known by Nessus is :
peheracosq
The Common Name in the certificate is :
peheracosq.peru.fsm.corp
67
Description
This script detects which SSL and TLS versions are supported by the remote service for encrypting communications.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2011/12/01, Modification date: 2014/04/14
Hosts
172.29.1.62 (tcp/3389)
This port supports TLSv1.0.
68
Description
The remote Terminal Services is configured to use SSL/TLS.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2013/02/22, Modification date: 2013/08/28
Hosts
172.29.1.62 (tcp/3389)
Subject Name:
Common Name: PEHERACOSQ.PERU.FSM.CORP
Issuer Name:
Common Name: PEHERACOSQ.PERU.FSM.CORP
Serial Number: 52 33 A3 A9 BD 58 B5 A0 42 D2 EA 6C 80 78 16 EC
Version: 3
Signature Algorithm: SHA-1 With RSA Encryption
Not Valid Before: Jul 18 17:48:29 2014 GMT
Not Valid After: Jan 17 17:48:29 2015 GMT
Public Key Info:
Algorithm: RSA Encryption
Key Length: 2048 bits
Public Key: 00 B6 4A D1 D6
58 29 52 E5 EE
26 E9 64 47 C3
E0 83 56 36 26
5B C9 A6 BA 1A
F8 BF 88 31 61
99 D5 DD 5E 49
D2 AC 0E F3 64
2F 80 71 1E 4F
DB 73 DA 0C A7
89 66 23 A5 36
FA C9 16 DB 26
4D 24 43 0B 65
Exponent: 01 00 01
B5
D1
2D
6F
4D
F8
35
A8
64
C5
C3
BD
0E
C1
0E
6B
7A
AA
AC
89
14
7D
48
CE
24
07
1B
3A
B7
48
BE
64
66
53
E8
D2
88
65
79
EE
46
A9
25
83
90
E0
FA
2A
E6
4F
79
FC
15
AA
E9
44
09
1C
B3
A1
D8
45
D4
72
BE
bits
1F 36
1C 24
2F 04
8C C1
DE 65
F5 75
47 8C
85 51
99 A9
B1
7E
14
47
31
18
17
86
CC
BD
00
32
24
42
AB
2A
F5
BD
FB
C4
54
C1
D3
BA
55
1E
86
BE
C0
23
6B
F6
E9
2F
25
75
D3
AE
87
14
44
D8
C5
03
2F
BC
41
5D
B6
AE
7F
CA
9A
F0
C0
70
2C
0E
27
A9
CE
56
EF
37
91
F6
21
8D
AE
E9
1D
1E
BE
ED
26
42
92
3A
26
70
B8
00
1D
24
2F
52
C7
88
24
4D
1C
4B
12
8C
6D
7E
C9
31
99
25
FF
0C
5E
1D
48
83
AE
C9
55
99
8B
D8
ED
E9
60
11
BB
FB
B7
06
EE
96
1A
37
32
E3
29
C5
6F
F3
55
D3
04
39
A9
93
0B
5F
E4
7F
21
F1
B0
C3
27
A0
AB
95
8E
F3
ED
EE
FE
9D
07
52
96
C0
4D
15
87
32
09
B3
5D
54
FD
4D
2B
A6
36
04
F1
28
77
0E
10
CD
F3
FB
E8
85
B3
3C
05
AB
D6
CE
C8
ED
82
84
7B
2D
74
2A
2D
4C
E2
DD
FD
69
E0
F0
F0
2D
56
F2
64
6D
72
64
B0
D9
54
52
30
69
Description
This script attempts to connect to the remote host via RDP (Remote Desktop Protocol) and attempts to take a
screenshot of the login screen.
While this is not a vulnerability by itself, some versions of Windows display the names of the users who can connect
and which ones are connected already.
Solution
n/a
Risk Factor
None
Plugin Information:
Publication date: 2013/04/22, Modification date: 2014/01/07
Hosts
172.29.1.62 (tcp/3389)
It was possible to gather the following screenshot of the remote login screen.
70