Good morning all!
I wanted to run this by the Mangolassi team first
. So over the weekend, I determined that our router was compromised. Scott, this answers a lot of questions that we have been wondering for months! So I determined that after my assistant set up the router he never changed the default password (I know what you wanna say trust me). Well our router got probed, and eventually, someone set up a shadow process.
I worked with UBNT support and here is what I got told:
EdgeOS uses rsyslogd that runs as root, not syslogd that runs as an unprivileged user ('ubnt' here). This is likely a malicious executable that was installed after a compromise.
So, to fix the issue, we have reset the router to defaults and reconfigured it by CLI. Which now that I feel a little more comfortable with it, I don't see a point in some cases for using the GUI. Upon review of the config my assistant used, we noticed a configuration that I'm not sure about.
ethernet eth1 {
address 10.10.2.1/22
address 10.10.3.1/22
address 10.10.4.1/22
description Local
duplex auto
poe {
output off
}
speed auto
So just to give a little backstory, we are 100% virtualized for our servers. Our Active Directory server also is the host for dns and dhcp scopes. We have a super scope of 10.10.0.1 through 10.10.4.254. I'm not sure if the EdgeMax should have all 3 ip's on one interface. That raised a few questions from people at UBNT forums. What exactly is that "doing" in a case like this? As I'm under the impression all the work should be done with the Windows Server handling the scope.
As I dig a little deeper, this issue seems to get worse and worse. When I open up the DHCP Manager, we have the superscope setup. However, for the router properties, he programmed 10.10.2.1, 10.10.3.1, 10.10.4.1, 8.8.8.8, 4.2.2.2. UMM excuse me for not paying attention to this sooner, but why would the DNS servers be in the router option on Windows Server?
To be honest, this is making me wanna throw up
Yes I know about the .loc (I walked out the room when this was set up to my disgust.) What's happening is, if anyone uses for instance the wireless and it goes over to the 10.10.4.x network, they can't get online. So no big deal I know it's just not talking to 10.10.4.1. I'm not sure how or rather WTF would cause that at this point other than this config.


