Security risks of keeping a port open for Socket.ahk

[alesyt0h]

Hello all!

I have an script that performs several operations on my computer based on the url & parameters sended to my ip. Like http://65.120.20.30:3234/someQuery&params=etcetc

I can do this using localhost. But I want to open the port so I can do the same while I’m not at home.

I’m using the Socket.ahk library from Geekdude and using the web server to receive incoming connections.

My question is if I open this port to the internet what would be the security risks for this?
I’ve tested already a possible ddos and is fine, after 1400petitions or so the socket server just crashes but the ahk script continues to work, also I can add a sleep to specify a cooldown if needed.

So, what would be the security risks doing this?

Thank you very much everyone!

[alesyt0h]

Anyone can bring some light on this?

Thanks!

[alesyt0h]

bump!

[swagfag]

who knows...

setup per-port MAC filtering on ur router if ure paranoid about someone else accessing to the endpoint

[alesyt0h]

who knows...

setup per-port MAC filtering on ur router if ure paranoid about someone else accessing to the endpoint

Good advice! Thank you

But It be possible for someone to "brute-force" that open port to acces my machine or other unwanted things??