{"id":27027,"date":"2019-04-26T20:14:00","date_gmt":"2019-04-26T20:14:00","guid":{"rendered":"http:\/\/0dddc8ad-0e73-4f8a-9f3f-dc0703eda135"},"modified":"2019-04-26T20:14:00","modified_gmt":"2019-04-26T20:14:00","slug":"over-two-million-iot-devices-vulnerable-because-of-p2p-component-flaws","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/over-two-million-iot-devices-vulnerable-because-of-p2p-component-flaws\/","title":{"rendered":"Over two million IoT devices vulnerable because of P2P component flaws"},"content":{"rendered":"

\"hichip-camera-with-uid.png\"<\/span><\/a>Image: Paul Marrapese<\/span><\/p>\n

\n
<\/span><\/div>\n<\/div>\n

More than two million IoT devices, possibly more, are using a vulnerable P2P firmware component that allows hackers to locate and take over impacted systems.<\/p>\n

Vulnerable devices include IP cameras, baby monitors, smart doorbells, DVRs, and many others, manufactured and sold by multiple vendors under hundreds of brands, such as HiChip, TENVIS, SV3C, VStarcam, Wanscam, NEO Coolcam, Sricam, Eye Sight, and HVCAM, just to name a few.<\/p>\n

What all these devices have in common is that they use iLnkP2P, a firmware component that allows the device to talk to vendors’ servers via the P2P (peer-to-peer) protocol.<\/p>\n

Earlier this year, security researcher Paul Marrapese discovered two vulnerabilities in this component –tracked under the CVE-2019-11219 and CVE-2019-11220 identifiers.<\/p>\n

According to Marrapese, the first “allows attackers to rapidly discover devices that are online,” while the second “allows attackers to intercept connections to devices and perform man-in-the-middle attacks” and “to steal the password to a device and take control of it.”<\/p>\n

Component maker did not respond to security researcher<\/h3>\n

The researcher says that the vulnerable component’s maker –Chinese company Shenzhen Yunni Technology Company, Inc– did not reply to emails notifying the company about the two security flaws.<\/p>\n

Attempts to contact the vendor through the CERT Coordination Center (CERT\/CC) at the Carnegie Mellon University and China’s national Computer Emergency Response Team (CN-CERT) had also failed.<\/p>\n

\n<\/section>\n

“I strongly recommend anyone dispose of vulnerable devices, but only if they cannot, they should block OUTBOUND traffic to 32100\/udp,” the researcher told ZDNet in an email.<\/p>\n

Blocking traffic on UDP port 32100 will prevent attackers and botnets from exploiting the vulnerabilities remotely, although devices will remain vulnerable to exploitation attempts from the local network, but the researcher considers this a more acceptable risk.<\/p>\n

How to spot a vulnerable device<\/h3>\n

Since there are hundreds of device brands that may use the iLnkP2P component in their firmware, on a website<\/a> the researcher published this week, he listed two methods that device owners can use and see if their device might be impacted.<\/p>\n

“Devices that use the following Android apps may be vulnerable,” the researcher said:<\/p>\n