Weakness · High
CWE-1253: Incorrect Selection of Fuse Values
What it is
The logic level used to set a system to a secure state relies on a fuse being unblown.
- Severity (our rating)
- High
- Likelihood of exploit
- Not rated by MITRE
- Introduced during
- Architecture and Design, Implementation
- Exploited in the wild
- No CVE in CISA's catalog
In more detail
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.
What an attacker can do
- Bypass Protection Mechanism (Access Control, Authorization)
- Gain Privileges or Assume Identity (Access Control, Authorization)
- DoS: Crash, Exit, or Restart (Availability)
- Read Memory (Confidentiality)
- Modify Memory (Integrity)
- Execute Unauthorized Code or Commands (Integrity)
How to prevent it
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.
H2 Security
Found it in your code?
We review where it appears, fix it with your team, and check it was not already used against you.
Talk to our teamT Academy
Stop writing it in the first place
Learn to build software and systems without weaknesses like this one, with practice on real hosts in your browser, every objective checked on the machine.
Start freeSource: MITRE Common Weakness Enumeration, CWE version 4.19.1. CWE is a trademark of The MITRE Corporation.