Is Port Forwarding risky?

[nine9s]

I play a free game called MULE (modern online version of early 1980s game.) Its server usually has 2 public games going but lately it has not. Individuals can host games through the service but you most open a specific port. I have done this and it works well.

I am wondering about the security risk. Is this very risky to do this? Should Windows 7 firewall (I did nothing with it, I did port forwarding in my router) protect against other traffic that might find that port or if another player, knowing my IP (it shows in the game) and knowing what port is open, tried something nefarious?

 

[AFurryReptile]

So long as something, like your server, is listening on that port, it isn't a huge risk. If the server isn't running, you won't want to leave that port open.

 

[nine9s]

So long as something, like your server, is listening on that port, it isn't a huge risk. If the server isn't running, you won't want to leave that port open.

Server is the game program?

 

[AFurryReptile]

Server is the game program?

Yes.

 

[nine9s]

Yes.

Thanks.

So all traffic to my IP via that port will go through that program. So the only risk would be if someone could exploit that program to gain access to my system?

If yes, then the problem I see is that it is a free game and not very much played (maybe a hundred or less of regular users), so the programmer probably did not go to much length to make sure it was secure since no money directly from it and it serves so few people.

I have Norton Anti-Virus (not security suite - just anti-virus.) Should Windows 7 Firewall or Norton Anti-Virus likely notice if someone entered my system via security holes/ problems in the program?

Is there anything, to limit the risk, I should do?

 

[AFurryReptile]

There really isn't much risk. Anyone trying to connect on that port is going to hit that game, and they aren't going to know what it is. The only thing that will even try to access your network are bots - and bots are dumb. They will check the port, see something listening on it, and move on.

You really don't have to worry. Just make sure to close the port if you ever stop running that game server.

 

[wirednuts]

same apply to utorrent when youre not sharing or downloading anything but the program is still open?

 

[SecurityTheatre]

I have Norton Anti-Virus (not security suite - just anti-virus.) Should Windows 7 Firewall or Norton Anti-Virus likely notice if someone entered my system via security holes/ problems in the program?

No, anti-virus is signature based, so it will only notice payloads that it is programmed to recognize. I sincerely doubt an attack against this software would trigger that sort of alert. But at the same time, who's writing exploits against this obscure program? Security by obscurity isn't "real" security, but it's not nothing either.

Is there anything, to limit the risk, I should do?

Try avoid publishing the IP/port too openly. Shut it down when not in use.

Realistically, that's about all you can do.

It's not terribly risky, to be honest.

 

[SecurityTheatre]

same apply to utorrent when youre not sharing or downloading anything but the program is still open?

It's probably best, but not absolutely required, in my opinion...

 

[AFurryReptile]

same apply to utorrent when youre not sharing or downloading anything but the program is still open?

You don't open any ports to run uTorrent, so you are not at any more risk using it than when you aren't.

Except that you might be getting tracked by the MPAA.

 

[Dravic]

So long as something, like your server, is listening on that port, it isn't a huge risk. If the server isn't running, you won't want to leave that port open.

Not entirely accurate. The software off and the port open is more secure as there is nothing to exploit. With the software off you would receive a connection refused message because the host is there but not accepting connections on that port.

"Walking" a firewall will tell me which ports are open regardless if something is on the inside to accept the connection.

The only danger is in the the exportability of the server software. All software has bugs, and any port open to the internet will be scanned all day everyday. Once you open the port Window's firewall's job is done and the security is up to the software vendor.

Door man cant hold the door open, then ask what everyone is doing inside the lobby.

Is the software still receiving updates (at least security fixes)?

If not you can mitigate the risk by only allowing the IP addresses required for play. Find out which port it uses (done). Type netstat -na when you are playing in a cmd window. You should see anyone who connected on that port now as ESTABLISHED. You should be able to set the scope in the windows firewall to allow just those IP addresses. This way you are only at risk from the service provider (matchmaker), and the individual computers making the connection to you as a client.

 

[Dravic]

You don't open any ports to run uTorrent, so you are not at any more risk using it than when you aren't.

Except that you might be getting tracked by the MPAA.

If your not sharing/seeding anything maybe, but utorrent and the rest also uses upnp which is a service on your firewall that will auto configure port forwarding for an application that needs it. One of the worst inventions security wise ever.

They only way to not open a port would be for the local client to make a call to the server on a regular basis to open a stateful connection in the firewall between you and the "seeder".

UPNP is terrible. Instead the education the masses (or adding network UAC type checks to the stack) lets just create a service that will open ports in the firewall without them knowing. Worst, upnp is enabled by default on many consumer firewall/router devices.

You too can become a botnet host.. but hey at least we all didn't have to learn how to open a port...