Recently ran across some AirGateway configs that had an extra user account on them. Typically on most Ubiquiti AirMax and AirGateway equipment, there are two user accounts that show up in the config. <\/p>\n\n\n\n
A cool trick we can do is add users in the config i.e. (users.3, users.4 etc.)<\/p>\n\n\n\n
So what do you do when you see a third user showing up that you didn’t put there?!<\/p>\n\n\n\n
The user account looked like the following.<\/p>\n\n\n\n
users.3.name=112233AABBCC\nusers.3.password=Gczz8EBQEdAIg \nusers.3.status=enabled<\/pre>\n\n\n\nThe username was the MAC address of the device and the password field is a DES(Unix) hash of what appears to be an 8 character randomly generated upper and lower case password. <\/p>\n\n\n\n
Older AirOS versions only let a user select a password up to 8 characters long. You could create a longer one and log in via SSH, but you wouldn’t be able to log into the web interface.<\/p>\n\n\n\n
Identifying Access<\/h2>\n\n\n\n
So how did these get on here in the first place?<\/p>\n\n\n\n
I am guessing that the users were created at some point while trying to adopt them to UNMS\/UISP before there was firmware that supported it. The user name is the actual MAC address of the device and the passwords do seem to be randomly generated. There do not appear to be any major differences between the support files from a normal AirGateway and a suspicious AirGateway.<\/p>\n\n\n\n
Also appears to only affects AirGateways which were the only devices that had issues in the past connecting to UNMS\/UISP. The rest of the AirMax equipment uses very similar firmware so if there was a security issue, it should have affected all the devices.<\/p>\n\n\n\n
The hashing type “DES(Unix)” does not appear to be used anymore, being replaced with MD5 Crypt. So this does appear to have happened awhile ago.<\/p>\n\n\n\n
Cracking the Hash<\/h2>\n\n\n\n
You’ll need hashcat installed and setup to crack the hash. Kali Linux has hashcat included (you will just want to have the NVIDIA drivers installed<\/a> for optimal performance). You can also check out installing hashcat on Fedora<\/a>, or check out the hashcat website for other systems. https:\/\/hashcat.net\/hashcat\/<\/a><\/p>\n\n\n\n
Put the hashes of interest into a text file called hash.txt<\/p>\n\n\n\n
Command to crack the passwords <\/p>\n\n\n\n
.\/hashcat.bin -a 3 -m 1500 .\/hash.txt -1?l?u ?1?1?1?1?1?1?1?1 -w 3 --session airgateway<\/pre>\n\n\n\nthe -1?l?u let’s us specify a custom character list made up of -l and -u. Lower and Upper case letters. –session airgateway will record a checkpoint ever so often. So if our run gets interrupted, we can restore the session with<\/p>\n\n\n\n
.\/hashcat.bin --session airgateway --restore<\/pre>\n\n\n\n<\/p>\n\n\n\n
Remediation<\/h2>\n\n\n\n
Fortunately, remediation is fairly simple.<\/p>\n\n\n\n
SSH into the affected device and open up the config file<\/p>\n\n\n\n
vi \/tmp\/system.cfg<\/pre>\n\n\n\nFind the lines that start with “users.3.”, delete them, and save the file<\/p>\n\n\n\n
Run the following command to save the changes.<\/p>\n\n\n\n
\/usr\/etc\/rc.d\/rc.softrestart save <\/pre>\n\n\n\nIf you are not comfortable with the command line, then you can, through the web gui, download a backup, edit the backup file in a text editor, then upload\/restore the backup.<\/em><\/p>\n\n\n\n
Other notes<\/h2>\n\n\n\n
Something else you may run across is a mcuser that shows up in \/etc\/passwd. This is typically a user used for AirControl, so if you have used AirControl in the past that is most likely why it is there. Check out the following article to remove the user.<\/p>\n\n\n\n