A few Dell PowerEdge R410 customers got slipped a mickey in the form of malware. Luckily customers were notified quickly but it is a warning that even the best need to be vigilant. Identifying the problem quickly prevented this from escalating into something on the order of the Energizer USB Battery incident. A thread was started on the Dell support website but, as noted in the thread, customers were contacted directly.
The malware some how found its way into the management firmware. An update essentially eliminated the problem. The details of the malware were not exposed and there is no indication that it caused any major problems. The problem only affected Windows-based machines that were updated with some service stock motherboards. New machines were not affect.
The problem again highlights the importance of vigilance, good reporting, and prompt reponse to software issues such as this regardless of the nature of the deployed platform. The PowerEdge R410 is effectively an embedded system. Embedded systems rarely have the direct interaction with a user as a laptop or mobile device so detecting a problem can be next to impossible for most users. Likewise, correcting this type of problem is not always an easy fix since the device may not have remote update capability.
This kind of problem hightlights two issues embedded developers need to keep in mind. First, problems like these need to be considered when creating the development, testing, deployment and upgrade policies for a company. Second, remote or in field updates to address this kind of problem should be considered when designing a system. On the other hand, update facilities need to be designed carefully so they are not also an attack vector for other kinds of viruses and worms. These days it is rare that USB or network connectivity is not part of a product design.
The Dell server was an easy target and the malware was probably not specific to the R410. Still, embedded systems are utilizing standard operating systems like Windows CE and Linux so generic malware, virueses and worms are now more likely able to operate on embedded devices. Knowing the problem can exist is a start. Putting the proper policies in place to prevent and address the problem is the next step. Finally, actual hardware and software design needs to take the issue into account otherwise a product might easily turn from a cash cow into legal liability.