Welcome Guest. | Log In | Register | Membership Benefits

'Smart' Batteries May Leave Laptop Users Vulnerable, Researcher Says

In Black Hat talk, security expert will show a hack on an unexpected component: the laptop battery

Jul 28, 2011 | 10:09 PM | 

By Robert Lemos, Contributing Writer
Dark Reading


If you're looking for security vulnerabilities on you laptop, there's a new spot to check: the battery.

Click here for more of Dark Reading's Black Hat articles.

The embedded controllers on laptop batteries are hackable, a researcher says, because some manufacturers -- including Apple -- do not change the passwords that prevent changes to the smart battery system's firmware according to an investigation of Apple laptop batteries carried out by security researcher Charlie Miller.

The data, which will be presented by veteran security researcher Charlie Miller at the Black Hat Conference next week, found that Apple batteries have two fixed passwords that allow the company to update the laptop component's firmware. Unfortunately, those passwords also make the smart battery system hackable.

Miller, a senior security consultant at Accuvant, took apart the batteries, identified their components, and found that batteries sold by Apple have a default password to unlock them and another discoverable password to allow access to the firmware.

With those two passwords known, eavesdropping on the communications between the laptop and the battery -- and running your own programs -- are both possible, he says.

"I definitely completely destroyed that first and most important layer of defense," Miller says. "The main brains of the operation is this chip, and I can control that now."

In a white paper on the research, Miller described the smart battery system as consisting of three chips, two of which protect against potential electrical problems. In addition, each battery cell has a thermal cutoff fuse that physically cuts power to and from the cell if its temperature rises too high.

The batteries are shipped in a locked down, or "sealed," mode, but the default password in the battery manufacturer's specification allows the battery to be unsealed, Miller says. In By reverse-engineering a MacBook battery update, Miller found the password that gives full access to the system.

While Miller limited his investigation to MacBook batteries, the research may apply to other non-Apple laptops as well. He tested a single off-market battery, however, and found that the manufacturer used a non-default password, limiting his ability to hack the system.

Miller had no problem bricking the batteries, but he failed in his original plan: to make laptop batteries overheat or even explode.

"I can definitely make it so the battery doesn't respond anymore," he says. "I did that seven times already."

In the end, Miller found he could rewrite the smart battery firmware to make the battery respond as an attacker wanted. He theorized that a program could be placed on the battery to allow malware to survive a clean install of a system, making the battery one more place to hide persistent attacks.

While Miller's research did not result in any "explosive" vulnerabilities, the research shows that investigating hardware components can bear fruit, even for software hackers, says Joe Grand, principal electrical engineer for Grand Idea Studio and a noted hardware hacker.

"The one thing that Charlie's work really exemplifies is this blending of hardware and software," Grand says. "To do hardware hacking, you don't have to be a hardware guy anymore, you can be a software guy. All these embedded systems are just small software systems, small computers."

It's unlikely that attackers will start focusing on laptop batteries, however. There's no real profit motive in bricking laptop batteries, says Grand.

"Whether attacking a battery is a worthwhile endeavor or not remains to be seen," he says. "Most malicious people are going to do things that make them money."

Have a comment on this story? Please click "Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS



Database Security Reports

report Securing The Data Warehouse
Many enterprises are building data warehouses to centralize the ever-increasing information flowing through their organizations into useful repositories. This makes good business sense, but it opens up a slew of concerns from a security standpoint. IT professionals can apply many of the same security best practices used with databases, but there are new lessons to be learned as well.

report Defend Your Data From Malicious Insiders
The biggest threat to your company?s most sensitive data may be the employee who has legitimate access to corporate databases but less-than-legitimate intentions. And while the incidence of insider data breaches has decreased, external attacks often imitate them--and do serious damage. Follow our advice to mitigate the risk.

report Ensuring Secure Database Access
Role-based access control based on least user privilege is one of the most effective ways to prevent the compromise of corporate data. But proper provisioning is a growing challenging, due to the proliferation of "big data," NoSQLdatabases, and cloud-based data storage.

Other reports from the Database Security Tech Center:

Related Content

Establishing a Strategy for Database Security is No Longer Optional
As databases continue to grow in size, complexity and importance, enterprises struggle to identify the most appropriate controls regarding their use and misuse. The report identifies best practices, including: Implementing database activity monitoring to mitigate the high levels of risk from database vulnerabilities, and address audit findings in areas such as database segregation of duties and change management; using data security measures, such as data masking and data encryption; and monitoring privileged-user access and access to critical data.

Database Activity Monitoring Is Evolving Into Database Audit and Protection
In this report, Gartner writes that "Database audit and protection (DAP) represents an evolutionary advance in database activity monitoring tools." DAP suites provide comprehensive, cross-platform support in heterogeneous database environments to protect sensitive data from inappropriate use. Organizations are increasingly concerned with optimizing database security and mitigating risks associated with database vulnerabilities.

Protecting Against Database Attacks and Insider Threats: Top 5 Scenarios
Data security presents a multi-dimensional challenge in today's complex IT environment. Multiple access paths and permission levels have resulted in a broad array of security threats and vulnerabilities. We invite you to read this new eBook: "Protecting against database attacks and insider threats" to learn the top five scenarios and essential best practices for preventing database attacks and insider threats.

Demo: Distributed Database Security with Real-time Monitoring and Audit Protection
Organizations across the globe continue to experience compromised data caused by malicious attacks, web application vulnerabilities or unauthorized changes. View this demo and learn how IBM InfoSphere Guardium? database activity monitoring can help protect your sensitive data in distributed DBMS environments with a holistic approach to data security and compliance.

Look Beyond Native Database Auditing To Improve Security, Audit Visibility, And Real-Time Protection
Today's attacks on enterprise databases are more sophisticated than ever, and they occur so fast that it's often difficult to stop them in real time. Despite significant efforts to protect enterprise databases, the number of records breached has grown each year - due to all types of internal and external attacks and violations of corporate policy.




Featured Webcasts
Featured Whitepapers
Featured Reports