 |
|
|
|
There are 22 different meanings of Land.


IBM
8 products, approx. 50 pages
IBM AS/400 OS7400 3.7
HP
4 products, approx. 26 pages
HP External JetDirect Print Servers
OpenVMS
1 product, approx. 16 pages
OpenVMS 7.1 with UCX 4.1-7
Novell
1 product, approx. 15 pages
Novell 4.11
Firewall (networking)
4 products, approx. 13 pages
Most firewalls should intercept the poison packet thus protecting the host from this attack. Some operating systems released updates fixing this security hole.
AmigaOS
1 product, approx. 13 pages
AmigaOS AmiTCP 4.2 (Kickstart 3.0)
Mac OS
1 product, approx. 12 pages
Mac OS MacTCP, 7.6.1 OpenTransport 1.1.2 and 8.0
FreeBSD
1 product, approx. 10 pages
FreeBSD 2.2.5-RELEASE and 3.0 (Fixed after required updates)
SCO Group
1 product, approx. 8 pages
SCO Unixware 2.1.1 and 2.1.2
NetBSD
1 product, approx. 8 pages
NetBSD 1.1 to 1.3 (Fixed after required updates)
NetApp
1 product, approx. 8 pages
NetApp NFS server 4.1d and 4.3
BeOS
1 product, approx. 6 pages
BeOS Preview release 2 PowerMac
QNX
1 product, approx. 5 pages
QNX 4.24
SunOS
1 product, approx. 4 pages
SunOS 4.1.3 and 4.1.4
NeXTSTEP
1 product, approx. 4 pages
NeXTSTEP 3.0 and 3.1
Irix
1 product, approx. 3 pages
Irix 5.2 and 5.3
BSD/OS
1 product, approx. 2 pages
BSDi 2.0 and 2.1
A LAND attack is a DoS (Denial of Service) attack that consists of sending a special poison spoofed packet to a computer, causing it to lock up. The security flaw was actually first discovered in 1997 by someone using the alias "m3lt", and has resurfaced many years later in operating systems such as Windows Server 2003 and Windows XP SP2.
The attack involves sending a spoofed TCP SYN packet (connection initiation) with the target host's IP address and an open port as both source and destination. The reason a LAND attack works is because it causes the machine to reply to itself continuously. Definition: "A LAND attack involves IP packets where the source and destination address are set to address the same device." Other land attacks have since been found in services like SNMP and Windows 88/tcp (kerberos/global services) which were caused by design flaws where the devices accepted requests on the wire appearing to be from themselves and causing replies repeatedly.

|
|


|
|  |
 |
|  |