COMMON WEAKNESS ENUMERATIONDraft

CWE-1253

Incorrect Selection of Fuse Values

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

Abstraction

Base

Structure

Simple

Likelihood of Exploit

Medium

Understand the problem

What is the problem?

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.

Root cause

How and when does the problem arise?

Lifecycle phase

Architecture and Design

Lifecycle phase

Implementation

Risk

What does successful exploitation lead to?

Bypass Protection MechanismGain Privileges or Assume Identity

Affected security scopes: Access Control, Authorization

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.
DoS: Crash, Exit, or Restart

Affected security scopes: Availability

Read Memory

Affected security scopes: Confidentiality

Modify MemoryExecute Unauthorized Code or Commands

Affected security scopes: Integrity

Defence

How is it prevented and fixed?

Architecture and Design

Architecture and design approach

Detail
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.
CWE-1253: Common Weakness Enumeration Entry CWE-1253 · DayBreach Sözlük · DayBreach