CWEweakness

CWE-1253 Incorrect Selection of Fuse Values

Official page ↗
Abstraction
Base
Structure
Simple
Status
Draft
Languages
Not Language-Specific
CWE version
5.0

Description

The logic level used to set a system to a secure state relies on a fuse being unblown.

Extended description

Fuses are often used to store secret data, including security configuration data. When not blown, a fuse is considered to store a logic 0, and, when blown, it indicates a logic 1. Fuses are generally considered to be one-directional, i.e., once blown to logic 1, it cannot be reset to logic 0.

Common consequences

• Access Control, Authorization: Bypass Protection Mechanism, Gain Privileges or Assume Identity — If the logic used to determine system-security state (by leveraging the values sensed from the fuses) uses negative logic, an attacker might blow the fuse and drive the system to an insecure state. • Availability: DoS: Crash, Exit, or Restart • Confidentiality: Read Memory • Integrity: Modify Memory, Execute Unauthorized Code or Commands

Potential mitigations

• [Architecture and Design] Logic should be designed in a way that blown fuses do not put the product into an insecure state that can be leveraged by an attacker.

Related

Attack pattern · CAPEC (1)

  • CAPEC-74 Manipulating State attack pattern

Child of · CWE (1)

  • CWE-693 Protection Mechanism Failure weakness

Referenced by CAPEC · weakness (1)

  • CAPEC-74 Manipulating State attack pattern

Referenced by CVE · weakness (1)

  • CVE-2023-6355 Incorrect selection of fuse values in the Controller 7000 platform allows an attacker to bypass some protection mechanisms to enable local… vulnerability