DOTAZ: Open SNMP service used for an attack: 109.71.214.8 Vyřešeno
Napsal: 20 kvě 2014 16:21
Dobrý den. Dnes jsem dostala e-mail od mého poskytovatele Internetu. Vůbec netuším, co tím autor myslel a co vlastně se po mně chce. Žádného ajťáka nemám, vše týkaje pc si dělám sama. Na tohle si netroufnu. Poradí mi někdo? Jenom zběžné info - žádnou síť nemám, mám jeden počítač a není propojen s žádným jiným PC, zmiňovaná IP adresa je moje....Viz mejl zde.....
Dobrý den,
přeposílám událost o odchycení nevhodného dat. streamu.
Pokud o problému nevíte, doporučuji kontrolu všech počítačů
ve vnitřní síti, případně pořešit s AjŤákem, který Vám spravuje vnitřní síť.
S pozdravem
Antonín Holub
administrátor sítě skvely.net
-------- Původní zpráva --------
Předmět: Open SNMP service used for an attack: 109.71.214.8
Datum: Tue, 20 May 2014 03:54:49 -0700
Od: NFOservers.com DDoS notifier <ddos-response@nfoservers.com>
Komu: admini@altnet.cz
You appear to be running an open SNMP server at IP address 109.71.214.8 that participated in an attack against a customer of ours today, generating large UDP responses to spoofed queries, with those responses becoming fragmented because of their size.
Please consider reconfiguring your SNMP system in one or more of these ways:
- Block queries made by unauthorized addresses. This can be done with an ACL or other firewall rule.
- Use a different query string than "public" and which cannot be easily guessed by a 3rd party.
- Disable SNMP entirely.
If you are an ISP, please also look at your network configuration and make sure that you do not allow spoofed traffic (that pretends to be from external IP addresses) to leave the network. Hosts that allow spoofed traffic make possible this type of attack.
Example SNMP responses sent to us by your device during the attack are given below.
Timestamps (far left) are PST (UTC-8), and the date is 2014-05-20.
02:02:14.749298 IP (tos 0x0, ttl 47, id 54035, offset 0, flags [+], proto UDP (17), length 1500) 109.71.214.8.161 > 192.223.24.x.80: UDP, length 4268
0x0000: 4500 05dc d313 2000 2f11 7680 6d47 d608 E......./.v.mG..
0x0010: c0df 184e 00a1 0050 10b4 e700 3082 10a8 ...N...P....0...
0x0020: 0201 0104 0670 7562 6c69 63a2 8210 9902 .....public.....
0x0030: 024e 4702 0100 0201 0030 8210 8b30 3d06 .NG......0...0=.
0x0040: 082b 0601 0201 0101 0004 314c 696e 7578 .+........1Linux
0x0050: 2032 .2
(The final octet of our customer's IP address is masked in the above output because some automatic parsers become confused when multiple IP addresses are included. The value of that octet is "78".)
-John
President
Nuclearfallout, Enterprises, Inc. (NFOservers.com)
(We're sending out so many of these notices, and seeing so many auto-responses, that we can't go through this email inbox effectively. If you have follow-up questions, please contact us at noc@nfoe.net.)
Dobrý den,
přeposílám událost o odchycení nevhodného dat. streamu.
Pokud o problému nevíte, doporučuji kontrolu všech počítačů
ve vnitřní síti, případně pořešit s AjŤákem, který Vám spravuje vnitřní síť.
S pozdravem
Antonín Holub
administrátor sítě skvely.net
-------- Původní zpráva --------
Předmět: Open SNMP service used for an attack: 109.71.214.8
Datum: Tue, 20 May 2014 03:54:49 -0700
Od: NFOservers.com DDoS notifier <ddos-response@nfoservers.com>
Komu: admini@altnet.cz
You appear to be running an open SNMP server at IP address 109.71.214.8 that participated in an attack against a customer of ours today, generating large UDP responses to spoofed queries, with those responses becoming fragmented because of their size.
Please consider reconfiguring your SNMP system in one or more of these ways:
- Block queries made by unauthorized addresses. This can be done with an ACL or other firewall rule.
- Use a different query string than "public" and which cannot be easily guessed by a 3rd party.
- Disable SNMP entirely.
If you are an ISP, please also look at your network configuration and make sure that you do not allow spoofed traffic (that pretends to be from external IP addresses) to leave the network. Hosts that allow spoofed traffic make possible this type of attack.
Example SNMP responses sent to us by your device during the attack are given below.
Timestamps (far left) are PST (UTC-8), and the date is 2014-05-20.
02:02:14.749298 IP (tos 0x0, ttl 47, id 54035, offset 0, flags [+], proto UDP (17), length 1500) 109.71.214.8.161 > 192.223.24.x.80: UDP, length 4268
0x0000: 4500 05dc d313 2000 2f11 7680 6d47 d608 E......./.v.mG..
0x0010: c0df 184e 00a1 0050 10b4 e700 3082 10a8 ...N...P....0...
0x0020: 0201 0104 0670 7562 6c69 63a2 8210 9902 .....public.....
0x0030: 024e 4702 0100 0201 0030 8210 8b30 3d06 .NG......0...0=.
0x0040: 082b 0601 0201 0101 0004 314c 696e 7578 .+........1Linux
0x0050: 2032 .2
(The final octet of our customer's IP address is masked in the above output because some automatic parsers become confused when multiple IP addresses are included. The value of that octet is "78".)
-John
President
Nuclearfallout, Enterprises, Inc. (NFOservers.com)
(We're sending out so many of these notices, and seeing so many auto-responses, that we can't go through this email inbox effectively. If you have follow-up questions, please contact us at noc@nfoe.net.)