Use IPTables to block access to internal network resources #194

Closed
opened 2022-10-03 13:08:11 +00:00 by aryak · 3 comments

Currently, a malicious user can access things in the internal network of @a.
Using a rule like this could prevent this.
iptables -A OUTPUT -d 192.168.1.0/24 -j REJECT --reject-with icmp-net-unreachable
With the limited testing i did, going to dsldevice.attlocal.net gave me the MAC address of the devices connected too..
I am not sure if this would mess with port forwarding tho..

Currently, a malicious user can access things in the internal network of @a. Using a rule like this could prevent this. `iptables -A OUTPUT -d 192.168.1.0/24 -j REJECT --reject-with icmp-net-unreachable` With the limited testing i did, going to dsldevice.attlocal.net gave me the MAC address of the devices connected too.. I am not sure if this would mess with port forwarding tho..
Owner

I added the ufw rule ufw deny out to 192.168.1.254 port 80. I think this should be enough to prevent exposure of the MAC addresses, but let me know if more needs to be done.

I added the `ufw` rule `ufw deny out to 192.168.1.254 port 80`. I think this should be enough to prevent exposure of the MAC addresses, but let me know if more needs to be done.
a closed this issue 2022-10-03 14:22:53 +00:00
a added the
bug
security
labels 2022-10-03 14:22:58 +00:00
a added this to the (deleted) project 2022-10-03 14:23:00 +00:00
Author

https is still open @a

https is still open @a
Owner

https is still open @a

Fixed, thanks!

> https is still open @a Fixed, thanks!
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: exozyme/exozyme#194
No description provided.