• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 680
  • Last Modified:

Does IPTables do port randomization?

Simple question, does IPTables do port randomization?  If so, does it do this by default?  

Thanks.
0
NYGiantsFan
Asked:
NYGiantsFan
  • 5
  • 4
  • 2
1 Solution
 
arnoldCommented:
Port Randomization? Usually when you have multiple IPs, you would do IP randomization.  It does not do it automatically, it has to be configured by altering the postrouting table.
http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:_Ch14_:_Linux_Firewalls_Using_iptables#.UOEiZKzNnTo

http://www.experts-exchange.com/OS/Linux/Q_26775594.html
0
 
DarinTCHSenior CyberSecurity EngineerCommented:
probably need to clarify what your doing

in other words I can set a rule in IPTables to accept ALL SOURCE traffic using and Ipaddress or port 1024:65535
going to DEST location x

or I could be discussing NAT
and I only have a few IP addresses so I am going to use ports in addition to this one...or these few address so I can have a large address range
and those ports can be assigned randomly

plus some ALGs use random ports

so simple answer YES - IPTables can work with ports
0
 
NYGiantsFanAuthor Commented:
Thanks for your follow up!!!!!


I ask, because it appears people are punching holes through the IPTables firewall using UDP packets.  

I can find no information how this was fixed in IP tables.  All the articles are years old and each of them say it cannot be solved, except through port randomization.

Your thoughts?
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
arnoldCommented:
Are there no originating udp packets to which these are responses?

You do not have an open udp port?  Are the destination the same port?
0
 
NYGiantsFanAuthor Commented:
The originating IP address is an unknown external.  The UDP packet (which IDS is detecting as a form of attack) is hitting a server interal to the network with a private IP address (10.16.0.55)

The source IP address port was 25033 and the destination IP address is 2877.
0
 
arnoldCommented:
What does the UDP packet contains?
Do you have UDP port redirect or is the System with IP 10.16.0.55 setup in a DMZ or has a rule that directs all traffic to WAN IP to this LAN IP?  I.e. you have a NAT rule x.x.x.x -> 10.16.0.55?
0
 
DarinTCHSenior CyberSecurity EngineerCommented:
same line of thinking
NAT often redirects and uses random ports
depending on how it was setup
some firewalls allow NAT with and without Ports
depending on the IP address pool
0
 
NYGiantsFanAuthor Commented:
It appears to be some type of SQL server attack.  The server is not in the DMZ.

According to the IDS, the packet attempts to execute an old SQL vulnerability.  

What I think is happening is that the attacker knows the location of the boxes (or IP ranges) and is using a UDP Pentration technique and punching a hole in the Firewall.  From what I have read, this type of attack was a vulnerability in IPTables Firewall solution (and many others).  

The
0
 
NYGiantsFanAuthor Commented:
Is it true that the only way to prevent this type of attack is using IP port randomization?  I think if the IP port is constantly assigned to a different server or device, a UDP packet cannot be sent in the exhaust port (sorry, firewall).  

Thanks.
0
 
arnoldCommented:
I think you are looking for a block as referenced
http://www.cyberciti.biz/tips/linux-iptables-10-how-to-block-common-attack.html

I think your issue seems to be that your iptables accept the packet and unnecessarily routes it.  Double deck to make sure it is not a packet that originates from your internal system and is returning.

Not sure how you envision port randomization.
Ports are usually randomly selected by the system and he remapped by the NAT on the router before letting the packet flow out to its destination.
0
 
NYGiantsFanAuthor Commented:
This question was too vague on my part.
0

Featured Post

Managing Security & Risk at the Speed of Business

Gartner Research VP, Neil McDonald & AlgoSec CTO, Prof. Avishai Wool, discuss the business-driven approach to automated security policy management, its benefits and how to align security policy management with business processes to address today's security challenges.

  • 5
  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now