Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm having a bit of a problem getting my head round what this vulnerability means, can someone help me understand this?

I'm particularly puzzled by the RESULTS section. Why would source port 25 be any different from a random source port, they're both originating from the outside world?

TCP Source Port Pass Firewall

Your firewall policy seems to let TCP packets with a specific source port pass through.

Some types of requests can pass through the firewall. The port number listed in the results section of this vulnerability report is the source port that unauthorized users can use to bypass your firewall.

Make sure that all your filtering rules are correct and strict enough. If the firewall intends to deny TCP connections to a specific port, it should be configured to block all TCP SYN packets going to this port, regardless of the source port.

Not Applicable

The host responded 4 times to 4 TCP SYN probes sent to destination port 22 using source port 25. However, it did not respond at all to 4 TCP SYN probes sent to the same destination port using a random source port.

share|improve this question
up vote 4 down vote accepted

when a client connect to a server, the client pickup a free tcp port it has between 1024 and 65535. On Linux/Unix, non root user can't pick up a port < 1024. Then it connect to a well known port, like 80 for http...

The report claims that it can reach destination port if the source port is specific (22 and 25 in your sample), but it can't if it use a random port (between 1024 and 65535 for example). Client normally use random port and so your rule shouldn't take into account the source port number

So one of your rule is bad, because it allows flows if the source port is specific, whereas it should only filter on the destination port, which is the only static part between the two.

I guess you miss created one of your rule by inadvertly exchanging source and destination value

share|improve this answer it. Thanks for the help. – Kev Feb 4 '10 at 20:03

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.