Forum Discussion

Sree_87068's avatar
Sree_87068
Icon for Nimbostratus rankNimbostratus
Apr 27, 2016

VIP listening on other ports other than defined

Have a Virtual server which is hosting traffic from internet and is hosting service port SMTP & UDP 53 . As per the vulnerability check its been found that the VIP is open also on SNMP and cpuple of other ports . Can you restrict other ports access from outside through an Irule ? can anyone please advice on the same

 

6 Replies

  • Vernon_97235's avatar
    Vernon_97235
    Historic F5 Account

    Assuming you are talking about LTM Virtual Servers, it is useful to distinguish two concepts: a Virtual IP and a Virtual Server. A Virtual IP is just that: an IP addresses for which the BIG-IP may accept traffic. A Virtual Server is a Virtual IP, a port and a protocol. A BIG-IP will reject all traffic that matches a VIP but does not match a Virtual Server -- unless you change the global setting for this, but you have to go out of your way to do that. If, on the other hand, a wildcard VS (that is, a Virtual Server listening on all ports) is defined for a VIP, naturally, traffic for any port will be accepted. Finally, if a VIP matches a self-IP, the self-IP may accept local traffic. But you should avoid this type of configuration.

     

    Ordinarily you should not need an iRule or something similar to prevent traffic.

     

    • Sree_87068's avatar
      Sree_87068
      Icon for Nimbostratus rankNimbostratus
      Thanks for your response . Apologize for not being clear in my query . I am referring to Virtual server . Currently Virtual server is defined as VIP:25 (TCP) & VIP:53(UDP) on LTM running Ver 10.2.4 . But during the scan its been found same VIP is also accepting on VIP: 161 (TCP) & VIP: 8080 . As per my understanding the traffic must be dropped by LTM when traffic is destined to VIP on port which is not defined ..Please do correct me if i am wrong ..
  • Assuming you are talking about LTM Virtual Servers, it is useful to distinguish two concepts: a Virtual IP and a Virtual Server. A Virtual IP is just that: an IP addresses for which the BIG-IP may accept traffic. A Virtual Server is a Virtual IP, a port and a protocol. A BIG-IP will reject all traffic that matches a VIP but does not match a Virtual Server -- unless you change the global setting for this, but you have to go out of your way to do that. If, on the other hand, a wildcard VS (that is, a Virtual Server listening on all ports) is defined for a VIP, naturally, traffic for any port will be accepted. Finally, if a VIP matches a self-IP, the self-IP may accept local traffic. But you should avoid this type of configuration.

     

    Ordinarily you should not need an iRule or something similar to prevent traffic.

     

    • Sree_87068's avatar
      Sree_87068
      Icon for Nimbostratus rankNimbostratus
      Thanks for your response . Apologize for not being clear in my query . I am referring to Virtual server . Currently Virtual server is defined as VIP:25 (TCP) & VIP:53(UDP) on LTM running Ver 10.2.4 . But during the scan its been found same VIP is also accepting on VIP: 161 (TCP) & VIP: 8080 . As per my understanding the traffic must be dropped by LTM when traffic is destined to VIP on port which is not defined ..Please do correct me if i am wrong ..
  • LTM will not accept the traffic unless you defined to accept (proxy thing). What do you see in the capture? is 'not defined' traffic getting dropped at VIP ?

     

  • That behaviour certainly is unexpected. The BigIP itself should not answer those ports assuming that the virtuals are configured properly. I'm not sure whether this is even possible, but do you happen to have a bidirectional NAT in place for the same IP address the virtual is using? That NAT might be forwarding traffic not accounted by the virtual to some server that will answer requests itself, for example SNMP (161/udp). Just an idea...

     

    HTH

     

    Martin