Security Appliance for Firmware Upgrade Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing computing devices lack effective mechanisms to prevent unauthorized firmware and software upgrades, which poses critical security vulnerabilities due to the inability to cryptographically validate software signing signatures.

Innovation Solution

A mechanism for passively monitoring, alerting, and preventing unauthorized firmware and/or software upgrade image transmissions between computing devices connected through a data bus, using cryptographic validation without modifying existing hardware or software.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If cryptographic validation is implemented to prevent unauthorized firmware upgrades, then security reliability is improved, but device complexity increases

Engineering Contradiction:
ImprovesecurityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

A security appliance is introduced as an intermediary component between the maintenance device and target computing devices. This appliance passively monitors data bus transmissions, validates firmware images using cryptographic signatures, and prevents unauthorized upgrades without requiring modifications to the existing ECUs. The intermediary handles the cryptographic validation burden centrally, allowing legacy devices to benefit from security enhancements without individual complexity increases.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Difficulty of detecting and measuring

If passive monitoring of data bus transmissions is implemented, then detection capability is improved, but processing time increases

Engineering Contradiction:
Improvedetection capabilityVSAvoidprocessing time
Core Design Contradiction:
Difficulty of detecting and measuringVSLoss of time

Solution Approach 1:

The security appliance performs preliminary cryptographic validation of firmware images during the transmission phase before the actual upgrade process begins. By validating the cryptographic signatures and integrity of firmware images in advance, the system prevents unauthorized upgrades from completing, avoiding the need for post-upgrade detection and remediation actions.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If cryptographic signature validation is performed on all firmware images, then security reliability is improved, but productivity decreases

Engineering Contradiction:
ImprovesecurityVSAvoidupdate speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The firmware image validation process is segmented into distinct phases: cryptographic signature validation, integrity checking, and approval for deployment. The security appliance validates only the critical cryptographic signatures and key integrity markers during transmission, rather than performing exhaustive analysis of the entire firmware image. This segmented approach maintains security while reducing validation time and preserving update productivity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP4034996B1Passive monitoring and prevention of unauthorized firmware or software upgrades between computing devices
Publication Date: 2025.03.05 SHIFT5 INC
  • EP4034996B1 patent drawingFigure 1~2
  • EP4034996B1 patent drawingFigure 3~4
  • EP4034996B1 patent drawingFigure 5A

AI summary

An apparatus for preventing unauthorized software or firmware upgrades between two or more computing devices connected on a data bus includes a cryptographic engine, memory, and at least one processor coupled with the cryptographic engine and memory. The cryptographic engine stores cryptographic metadata for authorized upgrade images for updating at least one target computing device coupled to the data bus. The cryptographic metadata includes a manifest list of upgrade images. The processor is configured to monitor the data bus for transmissions of striped update hashes from a maintenance device, to receive signed striped hashes corresponding to an upgrade image file transmitted by the maintenance device, to validate the striped update hashes using information in the manifest list, to log that an unauthorized upload has been attempted when at least one of the striped update hashes fails validation, and to perform a mitigation action(s) in response to the attempted unauthorized upload.