CWE-1334: Unauthorized Error Injection Can Degrade Hardware Redundancy

BaseDraft

An unauthorized agent can inject errors into a redundant block to deprive the system of redundancy or put the system in a degraded operating mode.

View on MITRE
Back to CWE Lookup

Extended Description

To ensure the performance and functional reliability of certain components, hardware designers can implement hardware blocks for redundancy in the case that others fail. This redundant block can be prevented from performing as intended if the design allows unauthorized agents to inject errors into it. In this way, a path with injected errors may become unavailable to serve as a redundant channel. This may put the system into a degraded mode of operation which could be exploited by a subsequent attack.

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Not Language-Specific
Platforms
Not OS-Specific

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-1334 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-1334, Unauthorized Error Injection Can Degrade Hardware Redundancy, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address Unauthorized Error Injection Can Degrade Hardware Redundancy during Architecture and Design

MITRE associates mitigation with Architecture and Design, Implementation, and Integration; recorded impacts include DoS: Crash, Exit, or Restart, DoS: Instability, Quality Degradation, DoS: Resource Consumption (CPU), and DoS: Resource Consumption (Memory); the entry maps to CAPEC-624, and CAPEC-625. Use these source-defined anchors to turn CWE-1334 into implementation, review, and verification checks for the affected component.

CWE-1334: Unauthorized Error Injection Can Degrade Hardware Redundancy — MITRE CWE

Triage CWE-1334 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-1334, Unauthorized Error Injection Can Degrade Hardware Redundancy, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-1334

Apply MITRE's full root-cause mapping guidance when using CWE-1334, Unauthorized Error Injection Can Degrade Hardware Redundancy. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-1334 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-1334, Unauthorized Error Injection Can Degrade Hardware Redundancy. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-1334: Unauthorized Error Injection Can Degrade Hardware Redundancy?+

CWE-1334: Unauthorized Error Injection Can Degrade Hardware Redundancy is a Common Weakness Enumeration (CWE) entry maintained by MITRE. An unauthorized agent can inject errors into a redundant block to deprive the system of redundancy or put the system in a degraded operating mode. To ensure the performance and functional reliability of certain components, hardware designers can implement hardware blocks for redundancy in the case that others fail. This redundant block can be prevented from performing as intended if the design allows unauthorized agents to inject errors into it. In this way, a path with injected errors may become unavailable to serve as a redundant channel. This may put the system into a degraded mode of operation which could be exploited by a subsequent attack.

What are the security consequences of Unauthorized Error Injection Can Degrade Hardware Redundancy?+

If exploited, CWE-1334 (Unauthorized Error Injection Can Degrade Hardware Redundancy) it can compromise Integrity and Availability, leading to outcomes such as DoS: Crash, Exit, or Restart, DoS: Instability, Quality Degradation, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory) and DoS: Resource Consumption (Other).

How do you prevent or mitigate Unauthorized Error Injection Can Degrade Hardware Redundancy?+

Recommended mitigations for CWE-1334 include: Ensure the design does not allow error injection in modes intended for normal run-time operation. Provide access controls on interfaces for injecting errors. Disallow error injection in modes which are expected to be used for normal run-time operation. Provide access controls on interfaces for injecting errors. Add an access control layer atop any unprotected interfaces for injecting errors.

Which programming languages are affected by Unauthorized Error Injection Can Degrade Hardware Redundancy?+

CWE-1334 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-1334 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

Find Related CVEs

Search for vulnerabilities that exploit CWE-1334

CVE vs CWE: What's the Difference?

Understanding vulnerabilities vs weaknesses

Understanding CVSS Scoring

How vulnerability severity is measured

View Full MITRE Entry

Complete technical details and references

Advertisement