📄 485.txt
字号:
Rule:--Sid:485--Summary:This event is generated when a router was unable to forward a packet dueto filtering and used the Internet Control Message Protocol to alertinvolved hosts.--Impact:Unknown. This particular message is meant only to be informative but can beindicative of malicious activity (spoofed traffic, DoS).--Detailed Information:A packet sent between two points on a network was administrativelyprohibited via filtering of some sort. The host or device performing thefiltering returned an ICMP message informing the apparent source hostthat filtering had been done.--Affected Systems: All systems.--Attack Scenarios:In a DoS attack it is common to to use spoofed source addresses. Ifand when the traffic gets filtered and an ICMP message is returned,the spoofed source address will be the recipient of the ICMP message.A similar situation may occur when a large portscan is occuring and anattempt is made to mask the true source of the scan by using spoofedsource addresses. --Ease of Attack:Simple. Tools are readily available that can craft arbitrary ICMPpackets. It is also possible to spoof packets using arbitraryaddresses potentially causing intermediary routers to generate ICMPmessages.--False Positives:None known.--False Negatives:None known.--Corrective Action:None needed unless messages become excessive or appear to be invalid. Determine what traffic caused this particular ICMP message to begenerated and act accordingly.--Contributors:Original rule writer unknownSnort documentation contributed by Jon Hart <warchild@spoofed.org>Sourcefire Vulnerability Research TeamNigel Houghton <nigel.houghton@sourcefire.com>-- Additional References:RFC 1812:ftp://ftp.isi.edu/in-notes/rfc1812.txt--
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -