Automatic Update?
-
If I was doing anything for a business, I'd use a non-windows computer to admin the pfsense and would make it a no-personal-bs box.
-
Yeah normally I use my Linux Laptop to administrate the box but sometimes it has to windows.
I was going through the logs of the box and it really was an attack over the webGUI.
Mar 16 08:15:06 hostname php: /index.php: Successful login for user 'admin' from: 18.239.0.140
Mar 16 08:15:06 hostname php: /index.php: Successful login for user 'admin' from: 18.239.0.140
Mar 16 08:17:18 hostname shutdown: reboot by root:
Mar 16 08:17:18 hostname shutdown: reboot by root:edit:
I can tell from which IP's I will access this box. Since they are all static and only 3 diffrent. And I don't have access to any Server in the MIT network. -
Yikes. :o
You never want to see that.Steve
-
Hackers out of MIT? haha…
Go figure...
Yeah - wipe and reinstall by hand.
-
I will try to export only the Firewall Rules and OpenVPN Server config and check them, because the rules are too much to do them by hand and also the VPNServer configs. But I need to change the keys since they are no longer save.
Thanks for your help!!!
-
Good deal.
BTW - Nice of your hacker friends to maintain your network for you. I've only ever known one set of hackers to do such a thing. Interesting.
-
Yuk. I have to know. Was it still admin/pfsense?
-
haha - I'd assumed no, but thats actually a great question.
-
no :) it was admin with a 26 char password containing letters,numbers and special characters.
-
Umm. Ok. Were you sniffed somewhere? Was http/80 available? Was that what you used when outside?
-
Pretty bad Rep on that IP.
https://www.projecthoneypot.org/ip_18.239.0.140
https://www.senderbase.org/lookup/ip/?search_string=18.239.0.140
That IP is listed in the Snort BL that I use for pfBlockerNG:
https://labs.snort.org/feeds/ip-filter.blf
grep "^18.239.0." /var/db/pfblockerng/deny/*
/var/db/pfblockerng/deny/BadIPs.txt:18.239.0.126
/var/db/pfblockerng/deny/Snort_BL.txt:18.239.0.140
/var/db/pfblockerng/deny/Snort_BL.txt:18.239.0.155 -
I'm pretty sure its a proxy address used by lots of people. Thats not the biggest deal. Whats on the other side of that pfsense? Anything important?
-
Also listed in the Spamhaus XBL list.
http://www.spamhaus.org/query/bl?ip=18.239.0.140It is also listed in MaxMind Inc. Anonymous Proxy list:
https://www.maxmind.com/en/proxy/18.239.0.140Stop Forum Spam - appears in our database 402 times. Current country of … 14-Mar-15 13:54
www.stopforumspam.com/ipcheck/18.239.0.140 -
Was that 2.1-RELEASE, not 2.1.2 or newer? If so, that was Heartbleed vulnerable. Definitely could be compromised through either OpenVPN (if a server is listening and not using TLS auth) and the web interface since it was open to the world. That's my best guess as to what happened. Given it was upgraded, sounds like maybe someone hacking Heartbleed vulnerable devices to patch them.
That IP is clearly a compromised machine of some sort, given the spam and other abuse coming out of it. Though it's odd that someone into spamming would be going around fixing people's security vulnerabilities. I'd expect them to want to be silent, to keep access to the system without you being aware. It's not uncommon for attackers to patch a system after they compromise it, because they don't want others to hack "their" systems, but usually done more quietly so the system's owner is unaware.
-
Actually that's a Tor exit node, which changes things a bit. It's potentially anyone in the world, not just a machine controlled by some spammers/hackers. More likely to have "altruistic" possibilities in that case.
-
Yes it was still 2.1 since I never got the downtime to patch it :( Which I did now….
the WebGUI of the PFsense was available via HTTPs on the OPT1 Interface which is the DMZ.
In the DMZ thare are a couple of WebServer, Lync Frontend and the usual stuff.
The PFsense is also holding a couple of VPN Tunnels to remote Sites and Remote Access for VPN Clients.
And all the Clients have been using OpenVPN without TLS!!! -
You think the hacker hacked his system and patched it to be nice?
Or that the TOR node is made available to be nice? (This on I can believe)
Heartbleed - I didn't even consider that but really I should have.
Unless I'm understanding wrong, you have to update not only the pfsense but also any SSH or Openvpn client accessing it.
Any unpatched server or client makes everything vulnerable. Is this correct?
-
Since I had De-Duplication on in pfBNG my first search only showed that IP in one list, i did a full search for that IP and it is a TOR exit node and listed on more Lists…
grep "^18.239.0." *
Blut_Tor.orig:18.239.0.140
ET_IPrep.orig:18.239.0.140
Greensnow.orig:18.239.0.155
Iblock_TOR.orig:18.239.0.155/32
Infiltrated.orig:18.239.0.140
Snort_BL.orig:18.239.0.140 -
You think the hacker hacked his system and patched it to be nice?
Possibly. That or they're super inept given absolutely no attempts to clear up their tracks - no clearing of logs showing their login and IP, and probably other traces left behind.
-
Yeah - These guys left alot of evidence behind. Pretty sloppy… Barely better than I could do (-:
