NMAP脚本介绍
2016-04-11 00:00
302 查看
摘要: nmap脚本
一、ntp-info.nse
Gets the time and configuration variables from an NTP server. We send two requests: a time request and a "read variables" (opcode 2) control message. Without verbosity, the script shows the time and the value of the
See RFC 1035 and the Network Time Protocol Version 4 Reference and Implementation Guide (http://www.eecis.udel.edu/~mills/database/reports/ntp4/ntp4.pdf) for documentation of the protocol.
二、ntp-monlist.nse
Obtains and prints an NTP server's monitor data.
Monitor data is a list of the most recently used (MRU) having NTP associations with the target. Each record contains information about the most recent NTP packet sent by a host to the target including the source and destination addresses and the NTP version and mode of the packet. With this information it is possible to classify associated hosts as Servers, Peers, and Clients.
A Peers command is also sent to the target and the peers list in the response allows differentiation between configured Mode 1 Peers and clients which act like Peers (such as the Windows W32Time service).
Associated hosts are further classified as either public or private. Private hosts are those having IP addresses which are not routable on the public Internet and thus can help to form a picture about the topology of the private network on which the target resides.
Other information revealed by the monlist and peers commands are the host with which the target clock is synchronized and hosts which send Control Mode (6) and Private Mode (7) commands to the target and which may be used by admins for the NTP service.
It should be noted that the very nature of the NTP monitor data means that the Mode 7 commands sent by this script are recorded by the target (and will often appear in these results). Since the monitor data is a MRU list, it is probable that you can overwrite the record of the Mode 7 command by sending an innocuous looking Client Mode request. This can be achieved easily using Nmap: nmap -sU -pU:123 -Pn -n --max-retries=0 <target>
Notes:
The monitor list in response to the monlist command is limited to 600 associations.
The monitor capability may not be enabled on the target in which case you may receive an error number 4 (No Data Available).
There may be a restriction on who can perform Mode 7 commands (e.g. "restrict noquery" in ntp.conf) in which case you may not receive a reply.
This script does not handle authenticating and targets expecting auth info may respond with error number 3 (Format Error).
一、ntp-info.nse
Gets the time and configuration variables from an NTP server. We send two requests: a time request and a "read variables" (opcode 2) control message. Without verbosity, the script shows the time and the value of the
version,
processor,
system,
refid, and
stratumvariables. With verbosity, all variables are shown.
See RFC 1035 and the Network Time Protocol Version 4 Reference and Implementation Guide (http://www.eecis.udel.edu/~mills/database/reports/ntp4/ntp4.pdf) for documentation of the protocol.
二、ntp-monlist.nse
Obtains and prints an NTP server's monitor data.
Monitor data is a list of the most recently used (MRU) having NTP associations with the target. Each record contains information about the most recent NTP packet sent by a host to the target including the source and destination addresses and the NTP version and mode of the packet. With this information it is possible to classify associated hosts as Servers, Peers, and Clients.
A Peers command is also sent to the target and the peers list in the response allows differentiation between configured Mode 1 Peers and clients which act like Peers (such as the Windows W32Time service).
Associated hosts are further classified as either public or private. Private hosts are those having IP addresses which are not routable on the public Internet and thus can help to form a picture about the topology of the private network on which the target resides.
Other information revealed by the monlist and peers commands are the host with which the target clock is synchronized and hosts which send Control Mode (6) and Private Mode (7) commands to the target and which may be used by admins for the NTP service.
It should be noted that the very nature of the NTP monitor data means that the Mode 7 commands sent by this script are recorded by the target (and will often appear in these results). Since the monitor data is a MRU list, it is probable that you can overwrite the record of the Mode 7 command by sending an innocuous looking Client Mode request. This can be achieved easily using Nmap: nmap -sU -pU:123 -Pn -n --max-retries=0 <target>
Notes:
The monitor list in response to the monlist command is limited to 600 associations.
The monitor capability may not be enabled on the target in which case you may receive an error number 4 (No Data Available).
There may be a restriction on who can perform Mode 7 commands (e.g. "restrict noquery" in ntp.conf) in which case you may not receive a reply.
This script does not handle authenticating and targets expecting auth info may respond with error number 3 (Format Error).
相关文章推荐
- Nmap扫描与Tcpdump抓包分析
- 使用Nmap为你的Windows网络找漏洞的图文分析
- 网络安全审计工具ZMap
- Nmap 基础教程
- Linux系统中nmap网络扫描工具的命令用法详解
- 运维工程师必会工具(Nmap和TCPdump)
- ***测试工具Nmap从初级到高级(转自论坛)
- nmap 6.49-usage
- Nmap、Netcat、Hping3工具对比
- Nmap用法详解
- NMAP网络扫描嗅探工具。
- nmap使用说明
- 十条nmap实用命令行技巧
- Nmap入门教程
- linux 下nmap命令使用
- nmap入门之目标说明
- nmap入门之主机发现
- nmap入门之其他
- 批量探测主机是否存活
- 为软件设置系统变量的PATH