IP Library › Granted Patent US 10,769,280
Granted Patent B2
US 10,769,280 · App. 16/218,727 · Granted Sep 8, 2020

Side channel attack countermeasures for secure bootloading

Inventors: Joshua Jay Norem (Austin, TX); Daniel Riedler (Los Angeles, CA); Chad Steven O'Neill (Abbotsford, AU)
Assignee: Silicon Laboratories, Inc.
G06F21/575G06F21/51G06F21/572H04L9/004H04L9/3247
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,769,280
App. No.
16/218,727
Granted
Sep 8, 2020
Kind
B2
Abstract

A system and method for minimizing the likelihood that the secret key used by a bootloader is compromised is disclosed. A bootloader is installed on the device. The bootloader is a software program that performs many functions. These functions may include checking the checksum of the incoming software image for integrity, decrypting the incoming software image using a secret key, deleting data in the FLASH memory, installing the new software image in the FLASH memory and other functions. The bootloader utilizes various techniques to track the versions of the software image being installed. The method counts the number of incomplete attempts that are made when trying to update the software image. By monitoring these parameters, the bootloader can determine when a malicious actor is attempting a side channel attack. In response, the bootloader may not allow a new software image to be loaded or the secret key to be accessed.

Claims (45)

1. A method of securely loading a new software image onto a device, comprising:

receiving, at the device, a bundle, the bundle containing a header and an encrypted payload, from a sender;

verifying the integrity of the header and the identity of the sender, wherein the header includes a version number;

performing a version check;

comparing a value of an attempts counter to install a new software image to a predetermined threshold, wherein the attempts counter tracks a number of times that an installation of a software image has been attempted;

decrypting the encrypted payload, wherein the new software image is contained in the encrypted payload, only if:

the version check is successful and the attempts counter is less than the predetermined threshold; and

after the decrypting, installing the new software image in a memory device in the device;

wherein the attempts counter is incremented prior to the decrypting.

2. The method of claim 1 , wherein the version check comprises determining that the version number in the header is greater than a version of the software image currently installed in the device.

3. The method of claim 1 , further comprising:

receiving an update graph from the sender, wherein the update graph specifies allowed versions as a function of a version of the software image currently installed in the device, wherein the version check determines whether the version in the header is an allowed version based on the update graph.

4. The method of claim 1 , wherein the version check comprises:

determining a number of times that a software image having the version number in the header has previously been installed in the device; and

determining whether the number of times is less than a predetermined threshold.

5. The method of claim 1 , wherein the attempts counter is reset after the software image has been successfully installed in the memory device.

6. The method of claim 1 , further comprising:

detecting that an error condition has occurred if the attempts counter is not less than the predetermined threshold.

7. The method of claim 6 , wherein the device will not decrypt any encrypted payloads once the error condition is detected.

8. The method of claim 1 , wherein the bundle is signed by the sender, and further comprising:

verifying the integrity of the bundle and the identity of the sender prior to the decrypting.

9. The method of claim 8 , wherein the header is signed by the sender using a header signature and the encrypted payload is also signed by the sender using a payload signature, further comprising:

verifying the integrity of the header and the identity of the sender prior to the decrypting; and

verifying the integrity of the software image and the identity of the sender prior to the decrypting.

10. A non-transitory storage medium, comprising a software program wherein the software program comprises instructions, which when executed by a processing unit of a device, enable the device to:

receive a bundle, the bundle containing a header and an encrypted payload, from a sender;

verify the integrity of the header and the identity of the sender, wherein the header includes a version number;

perform a version check;

compare a value of an attempts counter to install a new software image to a predetermined threshold, wherein the attempts counter tracks a number of times that an installation of a software image has been attempted;

decrypt the encrypted payload, wherein the new software image is contained in the encrypted payload, only if:

the version check is successful and the attempts counter is less than the predetermined threshold; and

after the decrypting, install the new software image in a memory device in the device;

wherein the attempts counter is incremented prior to the decrypting.

11. The non-transitory storage medium of claim 10 , wherein the version check comprises determining that the version number in the header is greater than a version of the software image currently installed in the device.

12. The non-transitory storage medium of claim 10 , wherein the software program further comprises instructions, which when executed by the processing unit, enable the device to:

receive an update graph from the sender, wherein the update graph specifies allowed versions as a function of a version of the software image currently installed in the device, wherein the version check determines whether the version in the header is an allowed version based on the update graph.

13. The non-transitory storage medium of claim 10 , wherein the attempts counter is reset after the software image has been successfully installed in the memory device.

14. The non-transitory storage medium of claim 10 , wherein the software program further comprises instructions, which when executed by the processing unit, enable the device to:

detect that an error condition has occurred if the attempts counter is not less than the predetermined threshold.

15. The non-transitory storage medium of claim 14 , wherein the device will not decrypt any encrypted payloads once the error condition is detected.

16. The non-transitory storage medium of claim 10 , wherein the bundle is signed by the sender, and wherein the software program further comprises instructions, which when executed by the processing unit, enable the device to:

verify the integrity of the bundle and the identity of the sender prior to the decrypting.

17. The non-transitory storage medium of claim 16 , wherein the header is signed by the sender using a header signature and the encrypted payload is also signed by the sender using a payload signature, wherein the software program further comprises instructions, which when executed by the processing unit, enable the device to:

verify the integrity of the header and the identity of the sender prior to the decrypting; and

verify the integrity of the software image and the identity of the sender prior to the decrypting.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 4, 2019
From: NOREM, JOSHUA JAY; RIEDLER, DANIEL; O'NEILL, CHAD STEVEN
To: SILICON LABORATORIES INC.
Reel/Frame 048227/0368 →
Continuity (1)
Related Publication 20200193028A1 · Jun 18, 2020