Friday, November 22, 2024

20K Ubiquiti IoT Cameras & Routers Are Sitting Ducks for Hackers

Tens of thousands of small office/home office (SOHO) devices sold by Ubiquiti Inc. are vulnerable on the open Internet to a five-year-old bug, researchers are warning.

In January 2019, broadband Internet expert Jim Troutman warned that an exposed port in dozens of Ubiquiti Internet of Things (IoT) gadgets was being exploited in denial-of-service (DoS) attacks. The underlying vulnerability, CVE-2017-0938, was assigned a “high” 7.5 score on the CVSS scale.

Seven months after that, researchers from Rapid7 were still able to find nearly 500,000 vulnerable devices. And now, even though Ubiquiti has long since acknowledged and patched the issue, around 20,000 devices remain vulnerable, Check Point Research noted in a new blog post.

“We can see that some of them were compromised,” says Radoslaw Madej, vulnerability research team leader at Check Point Software. “Also, I’ve only done pretty rudimentary fingerprinting of the devices. It’s quite possible that there are more of them [compromised] too.”

Check Point also warned that besides being used in a SOHO botnet for DoS attack amplification, compromised devices can leak potentially sensitive data, too.

Exposed Cameras & Routers Can Leak Data

In probing Ubiquiti gadgets like the G4 Instant Camera — an Internet-enabled camera with two-way audio — Check Point actually identified an additional exposed process beyond the one uncovered five years ago.

The original exposed process, on port 10001, was the Ubiquiti discovery protocol, used to communicate between the device and its CloudKey+ controller. The newly discovered exposed privileged process, on port 7004, is also used to communicate between devices.

Using spoofed packets, the Check Point researchers discovered that communicating with neither the CloudKey+ nor its connected devices required any sort of authentication. Further, the messages they received in response to their pings included specific information about the devices, plus their owners’ names and locations.

“In a few instances, actually, there was a first name and the last name of a person, and what turned out to be a location where a Ubiquiti router was located,” Madej recalls. “All this information … it took only one packet from me to receive that response.

“If I wanted to attack this entity, it would be easy for me, knowing the type of router they have, the name of the person, the exact software version, and their business address. [I could] find their contact details, and call them up saying: ‘Hey, I’m calling from your Internet provider. I need to do some maintenance work. Provide me with access to the admin panel.’ Because I can validate myself to this person by giving them all the information they need.”

The Issue with IoT

Patched Ubiquiti products have a safeguard against Internet-based attacks: They do not respond to pings coming from the wider Web, only from internal IP addresses.

Despite the easy availability of such a simple fix, tens of thousands affected products in the wild remain unpatched. This seems to have a lot less to do with Ubiquiti itself than IoT security in general.

“We got used to patching our Windows machines and MacBooks and mobile phones and whatnot, but we’re still not really used to the fact that we should also take care about our IoT devices, be it Wi-Fi routers, cameras, vacuum cleaners, fridges, and washing machines,” Madej says.

“Of course,” he adds, “the question is: To what extent an end user should even be bothered about it. We live in a time when all devices should have automatic updates enabled by default. I don’t think that should be a concern of the end user.”


Related Articles

Latest Articles