Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IoT/Embedded Security

// // //
07:00 AM
Larry Loeb
Larry Loeb
Larry Loeb

Japanese Government to Use 'Credential Stuffing' to Survey Consumer IoT Devices

The Japanese government is concerned about the security of IoT devices – but is a mass attempt to log into consumers' devices the right approach to the issue?

Japan has taken a new and authoritarian approach to the Internet of Things (IoT). According to a modification of a law passed that was last week, the National Institute of Information and Communications Technology (NICT), under the supervision of the Ministry of Internal Affairs and Communications, will attempt to survey and log into IoT devices owned by Japanese consumers.

They will use known default passwords (and dictionaries) in the effort. This is what has been called credential stuffing when done by a threat actor.

The authorities say they will, starting next month, compile a list of devices (like routers and cameras) which are vulnerable and then give the list to Internet service providers (ISP) who will then urge customers to correct them.

The first wave of scans could involve 200 million devices.

The government has said it is worried about attacks that could be carried out on the infrastructure of the Tokyo 2020 Summer Olympics by IoT devices.

Japan has a sketchy history with IoT devices in any case. The Ministry of Internal Affairs and Communications issued a report in 2016 that stated two thirds of reported cyber attacks involved IoT devices.

In 2018, Russians attacked the Pyeongchang Winter Olympics held in South Korea through use of the Olympic Destroyer malware. So Japan has a valid reason for such fears.

Even if this government-mandated survey is successful, the question remains unanswered of what good it will accomplish.

An alert made to consumers might accomplish the same goal of heightening awareness without the intrusive nature of the survey. The over-reaching problem is that even if vulnerable devices are discovered, there may be no easy way for consumers to patch them. They would still remain in their default and vulnerable state.

So why is this massive logon even being attempted?

It may be the Japanese want to measure the possible size of an IoT-based threat, so that they would know if it is something they need to prepare for. Their methodology remains suspect even to do this.

The credential stuffing approach is crude, similar in many ways to a brute force approach. If the devices were to be targeted by an attacker, there are other ways to they could be compromised than by the use of assumed default passwords to log on to them.

Recent attacks on routers have shown the existence of undocumented manufacturing backdoors, for example. The Japanese survey does not use this sort of vector, so it may give results that portray security in a higher state than it would appear if the IoT devices were under attack by a determined adversary.

The Japanese government may need to rethink exactly what it is trying to achieve with this effort, and whether or not they are on the most efficient path. Initial public reactions have been hostile, which means authorities have not made their case to the public for this survey.

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
Improving Enterprise Cybersecurity With XDR
Enterprises are looking at eXtended Detection and Response technologies to improve their abilities to detect, and respond to, threats. While endpoint detection and response is not new to enterprise security, organizations have to improve network visibility, expand data collection and expand threat hunting capabilites if they want their XDR deployments to succeed. This issue of Tech Insights also includes: a market overview for XDR from Omdia, questions to ask before deploying XDR, and an XDR primer.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2022-07-05
AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimised implementation will not encrypt the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was preexisting in the memory that wasn't written. In the special case of "in place" enc...
PUBLISHED: 2022-07-05
NULL Pointer Dereference allows attackers to cause a denial of service (or application crash). This only applies when lxml is used together with libxml2 2.9.10 through 2.9.14. libxml2 2.9.9 and earlier are not affected. It allows triggering crashes through forged input data, given a vulnerable code ...
PUBLISHED: 2022-07-05
Old session tokens can be used to authenticate to the application and send authenticated requests.
PUBLISHED: 2022-07-04
An issue was discovered in the Linux kernel through 5.18.9. A type confusion bug in nft_set_elem_init (leading to a buffer overflow) could be used by a local attacker to escalate privileges, a different vulnerability than CVE-2022-32250. (The attacker can obtain root access, but must start with an u...
PUBLISHED: 2022-07-04
Zoho ManageEngine ADSelfService Plus before 6203 allows a denial of service (application restart) via a crafted payload to the Mobile App Deployment API.