Strange logs on pfSense - most probably somebody has found a way to hack partially the box
-
@pippin said in Strange logs on pfSense - most probably somebody has found a way to hack partially the box:
Still no rules posted.....
-
@albgen Not exactly sure what Server B is, but Internet should go to WAN side of pfSense, then pfSense to LAN. LAN would include the host the PFSense VM is runnng on.
-
@provels said in Strange logs on pfSense - most probably somebody has found a way to hack partially the box:
Not exactly sure what Server B is, but Internet should go to WAN side of pfSense, then pfSense to LAN. LAN would include the host the PFSense VM is runnng on.
A and B are just point i have inserted to make you understand what kind of IP Addresses are setup...
-
You have a rule allowing all TCP traffic on WAN. That's passing it.
-
Looks like you have an allow all rule. Lots of traffic on it also. 5 GB.
-
yes, correct. the allow all rule was actually allowing everything :)
but the question remains: how have they triggered those kind of logs?
-
@albgen said in Strange logs on pfSense - most probably somebody has found a way to hack partially the box:
yes, correct. the allow all rule was actually allowing everything :)
but the question remains: how have they triggered those kind of logs?
Bots or hackers just checking what you have going on. Given time they'd try a lot more things.
-
Because the webgui on the WAN interface was open to the internet.
You can see the requests they were making were all failing because the pages don't exist in pfSense. And even if they guessed an existing page they would not have been able to access it without logging in. But you should never open the webgui to public access.
-
@stephenw10 said in Strange logs on pfSense - most probably somebody has found a way to hack partially the box:
Because the webgui on the WAN interface was open to the internet.
You can see the requests they were making were all failing because the pages don't exist in pfSense. And even if they guessed an existing page they would not have been able to access it without logging in. But you should never open the webgui to public access.
Sure, it was unintentional. Most probably testing something and the rule was enabled.
The point is the message logged. I have seen those kind of messages only on bugged wordpress php plugins so that's why i openend this discussion.
No idea what kind of requests they have made to trigger it. Tomorrow will check the config of nginx on pfsense if i can see better what is logged.
-
Those logs are expected if you open the webgui to random connection attempts. It's not an indication of any sort of compromise.
You can test it yourself, just try to access some page before you login and you will see those logs:
Apr 5 22:02:16 nginx 2023/04/05 22:02:16 [error] 47504#100318: *72304 open() "/usr/local/www/somenonexistentpage.htm" failed (2: No such file or directory), client: 172.21.16.8, server: , request: "GET /somenonexistentpage.htm HTTP/2.0", host: "4100.stevew.lan"
