June 21, 2017 By Larry Loeb 2 min read

Security is a constant concern within the Internet of Things (IoT), especially with the emergence of IoT malware such as the Mirai bot.

Researchers from Pen Test Partners recently discovered more about Mirai, rendering it potentially even more dangerous than previous iterations. The firm investigated the hardware and software in connected devices to determine what is possible — other than a giant distributed denial-of-service (DDoS) botnet.

IoT Malware Continues to Develop

Pen Test Partners researcher Ken Munro said the firm looked at over 30 brands of DVR hardware. It found, among other things, that an exploitable buffer overflow is present over port 80, which could give rise to a new DVR botnet composed of 1 million or more devices.

The act of port exploitation is actually quite simple. A GET request in the device’s web server can be crafted to allow remote code execution. This web server is enabled by default to allow users to remotely manage their DVRs.

If at least 153 characters are appended during remote code execution, the main Sofia process will crash and reboot. Since all processes on the DVR run as root, any commands that are injected during the attack will do the same.

“The binary running the web service has not been compiled with any of the common mitigations (ASLR, SSP etc.), allowing this to be used for remote code execution,” Pen Test Partners reported. The firm also discovered that some of the DVRs use TCP port 12323, a Telnet port that is vulnerable to the same Mirai default credentials that were used in previous attacks.

Persistence Is Possible

Interestingly, Bleeping Computer explained that Pen Test Partners also found a way to remotely crush a standard Mirai botnet. However, the method could also be used to make Mirai persistent beyond a power-off reboot, which normally wipes the attack code.

In light of this, Pen Test Partners refrained from publishing any details about this new method. It feared that a weaponized version of Mirai might emerge, which is reasonable, given how the original Mirai code was swiftly modified and used in attacks.

IoT devices are sources of unregulated and widespread insecurity. While some manufacturers have taken limited steps to moderate the effects of the devices they make, they still have a long way to go to fully mitigate the risks.

More from

NIST’s role in the global tech race against AI

4 min read - Last year, the United States Secretary of Commerce announced that the National Institute of Standards and Technology (NIST) has been put in charge of launching a new public working group on artificial intelligence (AI) that will build on the success of the NIST AI Risk Management Framework to address this rapidly advancing technology.However, recent budget cuts at NIST, along with a lack of strategy implementation, have called into question the agency’s ability to lead this critical effort. Ultimately, the success…

Researchers develop malicious AI ‘worm’ targeting generative AI systems

2 min read - Researchers have created a new, never-seen-before kind of malware they call the "Morris II" worm, which uses popular AI services to spread itself, infect new systems and steal data. The name references the original Morris computer worm that wreaked havoc on the internet in 1988.The worm demonstrates the potential dangers of AI security threats and creates a new urgency around securing AI models.New worm utilizes adversarial self-replicating promptThe researchers from Cornell Tech, the Israel Institute of Technology and Intuit, used what’s…

Passwords, passkeys and familiarity bias

5 min read - As passkey (passwordless authentication) adoption proceeds, misconceptions abound. There appears to be a widespread impression that passkeys may be more convenient and less secure than passwords. The reality is that they are both more secure and more convenient — possibly a first in cybersecurity.Most of us could be forgiven for not realizing passwordless authentication is more secure than passwords. Thinking back to the first couple of use cases I was exposed to — a phone operating system (OS) and a…

Topic updates

Get email updates and stay ahead of the latest threats to the security landscape, thought leadership and research.
Subscribe today