Strange new rules added to my iptables config… Was my server hacked?












1















Today, I listed my iptables for a routine check -- and discovered two strange UFW rules that I don't remember setting up myself, referring to two specific IP addresses that I can't identify:



-A ufw-before-input -d 224.0.0.251/32 -p udp -m udp --dport 5353 -j ACCEPT
-A ufw-before-input -d 239.255.255.250/32 -p udp -m udp --dport 1900 -j ACCEPT


This is kind of scary. Did someone manage to hack into my server and add these rules? If not, what happened?



(And if some malicious agent did hack into my firewall, why would they use ports 5353 and 1900, that aren't being forwarded by my router??)










share|improve this question



























    1















    Today, I listed my iptables for a routine check -- and discovered two strange UFW rules that I don't remember setting up myself, referring to two specific IP addresses that I can't identify:



    -A ufw-before-input -d 224.0.0.251/32 -p udp -m udp --dport 5353 -j ACCEPT
    -A ufw-before-input -d 239.255.255.250/32 -p udp -m udp --dport 1900 -j ACCEPT


    This is kind of scary. Did someone manage to hack into my server and add these rules? If not, what happened?



    (And if some malicious agent did hack into my firewall, why would they use ports 5353 and 1900, that aren't being forwarded by my router??)










    share|improve this question

























      1












      1








      1


      1






      Today, I listed my iptables for a routine check -- and discovered two strange UFW rules that I don't remember setting up myself, referring to two specific IP addresses that I can't identify:



      -A ufw-before-input -d 224.0.0.251/32 -p udp -m udp --dport 5353 -j ACCEPT
      -A ufw-before-input -d 239.255.255.250/32 -p udp -m udp --dport 1900 -j ACCEPT


      This is kind of scary. Did someone manage to hack into my server and add these rules? If not, what happened?



      (And if some malicious agent did hack into my firewall, why would they use ports 5353 and 1900, that aren't being forwarded by my router??)










      share|improve this question














      Today, I listed my iptables for a routine check -- and discovered two strange UFW rules that I don't remember setting up myself, referring to two specific IP addresses that I can't identify:



      -A ufw-before-input -d 224.0.0.251/32 -p udp -m udp --dport 5353 -j ACCEPT
      -A ufw-before-input -d 239.255.255.250/32 -p udp -m udp --dport 1900 -j ACCEPT


      This is kind of scary. Did someone manage to hack into my server and add these rules? If not, what happened?



      (And if some malicious agent did hack into my firewall, why would they use ports 5353 and 1900, that aren't being forwarded by my router??)







      iptables firewall ufw hacking






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 9 at 23:44









      killer_rabbitkiller_rabbit

      112




      112






















          2 Answers
          2






          active

          oldest

          votes


















          0














          Quoting man ufw:



          NOTES
          On installation, ufw is disabled with a default incoming policy of
          deny, a default forward policy of deny, and a default outgoing policy
          of allow, with stateful tracking for NEW connections for incoming and
          forwarded connections. In addition to the above, a default ruleset is
          put in place that does the following:

          [ ... ]

          - ACCEPT mDNS (zeroconf/bonjour/avahi 224.0.0.251 for IPv4 and ff02::fb
          for IPv6) for service discovery (INPUT)

          - ACCEPT UPnP (239.255.255.250 for IPv4 and ff02::f for IPv6) for ser‐
          vice discovery (INPUT)


          So these two rules you are seeing are part of ufw's default settings and allow mDNS and UPnP services to work.






          share|improve this answer
























          • Aha! Right, I should have checked the manpage. Thanks for the clarification!

            – killer_rabbit
            Feb 11 at 9:56



















          1














          Googling says that those IP addresses are related to Simple Service Discovery Protocol (SSDP)/uPnP and iTunes. So it is likely that these rules are related to software you installed and relate to sharing information on a LAN. whois doesn't return any information for either IP.



          See



          https://stackoverflow.com/questions/12483717/what-is-the-multicast-doing-on-224-0-0-251



          and



          https://wiki.wireshark.org/SSDP






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "89"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1117024%2fstrange-new-rules-added-to-my-iptables-config-was-my-server-hacked%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Quoting man ufw:



            NOTES
            On installation, ufw is disabled with a default incoming policy of
            deny, a default forward policy of deny, and a default outgoing policy
            of allow, with stateful tracking for NEW connections for incoming and
            forwarded connections. In addition to the above, a default ruleset is
            put in place that does the following:

            [ ... ]

            - ACCEPT mDNS (zeroconf/bonjour/avahi 224.0.0.251 for IPv4 and ff02::fb
            for IPv6) for service discovery (INPUT)

            - ACCEPT UPnP (239.255.255.250 for IPv4 and ff02::f for IPv6) for ser‐
            vice discovery (INPUT)


            So these two rules you are seeing are part of ufw's default settings and allow mDNS and UPnP services to work.






            share|improve this answer
























            • Aha! Right, I should have checked the manpage. Thanks for the clarification!

              – killer_rabbit
              Feb 11 at 9:56
















            0














            Quoting man ufw:



            NOTES
            On installation, ufw is disabled with a default incoming policy of
            deny, a default forward policy of deny, and a default outgoing policy
            of allow, with stateful tracking for NEW connections for incoming and
            forwarded connections. In addition to the above, a default ruleset is
            put in place that does the following:

            [ ... ]

            - ACCEPT mDNS (zeroconf/bonjour/avahi 224.0.0.251 for IPv4 and ff02::fb
            for IPv6) for service discovery (INPUT)

            - ACCEPT UPnP (239.255.255.250 for IPv4 and ff02::f for IPv6) for ser‐
            vice discovery (INPUT)


            So these two rules you are seeing are part of ufw's default settings and allow mDNS and UPnP services to work.






            share|improve this answer
























            • Aha! Right, I should have checked the manpage. Thanks for the clarification!

              – killer_rabbit
              Feb 11 at 9:56














            0












            0








            0







            Quoting man ufw:



            NOTES
            On installation, ufw is disabled with a default incoming policy of
            deny, a default forward policy of deny, and a default outgoing policy
            of allow, with stateful tracking for NEW connections for incoming and
            forwarded connections. In addition to the above, a default ruleset is
            put in place that does the following:

            [ ... ]

            - ACCEPT mDNS (zeroconf/bonjour/avahi 224.0.0.251 for IPv4 and ff02::fb
            for IPv6) for service discovery (INPUT)

            - ACCEPT UPnP (239.255.255.250 for IPv4 and ff02::f for IPv6) for ser‐
            vice discovery (INPUT)


            So these two rules you are seeing are part of ufw's default settings and allow mDNS and UPnP services to work.






            share|improve this answer













            Quoting man ufw:



            NOTES
            On installation, ufw is disabled with a default incoming policy of
            deny, a default forward policy of deny, and a default outgoing policy
            of allow, with stateful tracking for NEW connections for incoming and
            forwarded connections. In addition to the above, a default ruleset is
            put in place that does the following:

            [ ... ]

            - ACCEPT mDNS (zeroconf/bonjour/avahi 224.0.0.251 for IPv4 and ff02::fb
            for IPv6) for service discovery (INPUT)

            - ACCEPT UPnP (239.255.255.250 for IPv4 and ff02::f for IPv6) for ser‐
            vice discovery (INPUT)


            So these two rules you are seeing are part of ufw's default settings and allow mDNS and UPnP services to work.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Feb 10 at 20:02









            Byte CommanderByte Commander

            65.6k27179302




            65.6k27179302













            • Aha! Right, I should have checked the manpage. Thanks for the clarification!

              – killer_rabbit
              Feb 11 at 9:56



















            • Aha! Right, I should have checked the manpage. Thanks for the clarification!

              – killer_rabbit
              Feb 11 at 9:56

















            Aha! Right, I should have checked the manpage. Thanks for the clarification!

            – killer_rabbit
            Feb 11 at 9:56





            Aha! Right, I should have checked the manpage. Thanks for the clarification!

            – killer_rabbit
            Feb 11 at 9:56













            1














            Googling says that those IP addresses are related to Simple Service Discovery Protocol (SSDP)/uPnP and iTunes. So it is likely that these rules are related to software you installed and relate to sharing information on a LAN. whois doesn't return any information for either IP.



            See



            https://stackoverflow.com/questions/12483717/what-is-the-multicast-doing-on-224-0-0-251



            and



            https://wiki.wireshark.org/SSDP






            share|improve this answer




























              1














              Googling says that those IP addresses are related to Simple Service Discovery Protocol (SSDP)/uPnP and iTunes. So it is likely that these rules are related to software you installed and relate to sharing information on a LAN. whois doesn't return any information for either IP.



              See



              https://stackoverflow.com/questions/12483717/what-is-the-multicast-doing-on-224-0-0-251



              and



              https://wiki.wireshark.org/SSDP






              share|improve this answer


























                1












                1








                1







                Googling says that those IP addresses are related to Simple Service Discovery Protocol (SSDP)/uPnP and iTunes. So it is likely that these rules are related to software you installed and relate to sharing information on a LAN. whois doesn't return any information for either IP.



                See



                https://stackoverflow.com/questions/12483717/what-is-the-multicast-doing-on-224-0-0-251



                and



                https://wiki.wireshark.org/SSDP






                share|improve this answer













                Googling says that those IP addresses are related to Simple Service Discovery Protocol (SSDP)/uPnP and iTunes. So it is likely that these rules are related to software you installed and relate to sharing information on a LAN. whois doesn't return any information for either IP.



                See



                https://stackoverflow.com/questions/12483717/what-is-the-multicast-doing-on-224-0-0-251



                and



                https://wiki.wireshark.org/SSDP







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Feb 10 at 2:43









                Organic MarbleOrganic Marble

                11.3k63459




                11.3k63459






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Ask Ubuntu!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1117024%2fstrange-new-rules-added-to-my-iptables-config-was-my-server-hacked%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                    Mangá

                     ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕