Millions of IoT devices and routers could have a mega security flaw
Anthony Spadafora
https://www.nastel.com/millions-of-iot-devices-and-routers-could-have-a-mega-security-flaw/
An unpatched vulnerability in a popular C standard library found in a wide range of IoT products and routers could put millions of devices at risk of attack.
The vulnerability, tracked as CVE-2022-05-02 and discovered by Nozomi Networks, is present in the domain name system (DNS) component of the library uClibc and its uClibc-ng fork from the OpenWRT team. Both uClibc and uClibc-ng are widely used by Netgear, Axis, Linksys and other major vendors as well as in Linux distros designed for embedded applications.
uClibc’s DNS implementation provides a mechanism for performing DNS-related requests including lookups and translating domain names to IP addresses.
At this time,a fix is currently unavailablefrom uClibc’s developer which means thatdevices from more than 200 vendors are currently at risk of DNS poisoning or DNS spoofingthat can redirect a potential victim to a malicious website hosted on an attacker controlled server.
Risk of DNS poisoning
Security researchers at Nozomi first came across the vulnerability in uClibc after reviewing traces of DNS requests performed by a connected device at which time they found several peculiarities caused by the library’s internal lookup function. Upon further investigation, the IoT security firm discovered that the transaction IDs of these DNS lookup requests were predictable and therefore DNS poisoning could be possible in certain circumstances.
Nozomi Networks provided further insight in a blog post on what an attacker could accomplish by carrying out DNS poisoning on vulnerable IoT devices and routers, saying:
“A DNS poisoning attack enables subsequent Man-in-the-Middle attacks because the attacker, by poisoning DNS records, is capable of rerouting network communications to a server under their control. The attacker could then steal and/or manipulate information transmitted by users, and perform other attacks against those devices to completely compromise them. The main issue here is how DNS poisoning attacks can force an authenticated response.”
After discovering this flaw in uClibc back in September of last year, Nozomi immediately informed CISA about it and then reported its findings to the CERT Coordination Center in December. However, it wasn’t until January of this year that the firm disclosed the vulnerability to the vendors whose devices may be impacted by the flaw.
While a fix currently isn’t available, the affected vendors and other stakeholders are working together to develop a patch. Still though, once a patch is ready, end-users will need to apply it themselves on their devices through firmware updates but this could delay the amount of time it takes for the vulnerability to be fixed for good.
This article originally appeared on techradar.com, to read the full article, click here.
Nastel Technologies is the global leader in Integration Infrastructure Management (i2M). It helps companies achieve flawless delivery of digital services powered by integration infrastructure by delivering Middleware Management, Monitoring, Tracking, and Analytics to detect anomalies, accelerate decisions, and enable customers to constantly innovate, to answer business-centric questions, and provide actionable guidance for decision-makers. It is particularly focused on IBM MQ, Apache Kafka, Solace, TIBCO EMS, ACE/IIB and also supports RabbitMQ, ActiveMQ, Blockchain, IOT, and many more.
__
No worries though, the IoB (Internet of Bodies) will be flawless. /s
https://www.weforum.org/agenda/2020/06/internet-of-bodies-covid19-recovery-governance-health-data/
https://www.rand.org/multimedia/video/2020/10/29/what-is-the-internet-of-bodies.html
https://www.forbes.com/sites/bernardmarr/2019/12/06/what-is-the-internet-of-bodies-and-how-is-it-changing-our-world/
https://www.analyticssteps.com/blogs/internet-bodies-everything-you-need-know
https://www.rand.org/blog/articles/2020/10/the-internet-of-bodies-will-change-everything-for-better-or-worse.html