Finger bomb recursive request |
---|
Risk Level: | Medium | Check or Attack Name: fingerbomb |
---|---|---|
Platforms: | Finger Service | |
Description: | The system is vulnerable to the Finger Bomb. Finger Bomb allows an attacker to disrupt your network using the redirection capability in the finger daemon. Some finger daemons allow redirecting a finger request to remote sites using the form finger username@hostname1@hostname2. The finger will go through hostname2, then to hostname1. This technique helps attackers cover their tracks, because hostname1 will see a finger coming from hostname2 instead of from the original service. This technique has been used to go through firewalls, if they are not properly configured. This can happen by using the command finger user@host@firewall. An attacker could also use a recursive finger, such as finger username@hostname@hostname@hostname. Finger will call itself repeatedly, using more resources until the machine has consumed all its resources. A similar denial of service attack may happen when an attacker types finger username@@@@@@@@@@@@@@@@@@@@@hostname1. The repeated @ causes finger to repeatedly finger the same machine until the memory and hard drive swap space fill up. This causes the machine to stop or slow to an unusable speed. |
|
Remedy: | Disable finger, or install a version of finger that turns off redirection. GNU Finger can be configured to not allow redirection. Unix: Disable the finger daemon. To disable a Unix daemon started from inetd, follow these steps:
—OR— To turn off finger redirection, Unix systems can use GNU finger available from ftp://prep.ai.mit.edu/pub/gnu/finger-1.37.tar.gz. Windows: Fingerd is not native to Windows, but may be present. To disable fingerd, follow these steps:
|
|
References: |
Know Your Risks |