CWE-1384: Improper Handling of Physical or Environmental Conditions

Definition

What is CWE-1384?

This weakness occurs when a hardware device fails to manage unexpected physical or environmental situations, whether they happen naturally or are deliberately caused by an attacker. These conditions can force the hardware into an insecure state.

Hardware is designed to operate reliably within specific physical and environmental limits. When it encounters conditions outside this range—like extreme temperatures, power spikes, or electromagnetic interference—its behavior can become unpredictable and insecure. An attacker can artificially create these conditions to induce faults, such as flipping a critical bit used for authentication or bypassing a security check. Common threats include extreme temperatures, electromagnetic interference (EMI), unexpected light sources (lasers, UV), power anomalies (over/under-voltage), clock manipulation (glitching), component aging, and exposure to radiation. Since hardware often can't control its external environment, developers must design systems to either withstand these stresses or fail securely without compromising security controls.

Real-world impact

Real-world CVEs caused by CWE-1384

CVE-2019-17391

Lack of anti-glitch protections allows an attacker to launch a physical attack to bypass the secure boot and read protected eFuses.

How attackers exploit it

Step-by-step attacker path

1
Identify a code path that handles untrusted input without validation.
2
Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.
3
Deliver the payload through a normal request and observe the application's reaction.
4
Iterate until the response leaks data, executes attacker code, or escalates privileges.

Vulnerable code example

Vulnerable pseudo

MITRE has not published a code example for this CWE. The pattern below is illustrative — see Resources for canonical references.

Vulnerable pseudo

// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
  // Untrusted input flows directly into the sensitive sink.
  return executeUnsafe(input);
}

Secure code example

Secure pseudo

// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
  const safe = validateAndEscape(input);
  return executeWithGuards(safe);
}

What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.

Prevention checklist

How to prevent CWE-1384

Requirements In requirements, be specific about expectations for how the product will perform when it exceeds physical and environmental boundary conditions, e.g., by shutting down.
Architecture and Design / Implementation Where possible, include independent components that can detect excess environmental conditions and have the capability to shut down the product.
Architecture and Design / Implementation Where possible, use shielding or other materials that can increase the adversary's workload and reduce the likelihood of being able to successfully trigger a security-related failure.

Detection signals

How to detect CWE-1384

SAST High

Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.

DAST Moderate

Run dynamic application security testing against the live endpoint.

Runtime Moderate

Watch runtime logs for unusual exception traces, malformed input, or authorization bypass attempts.

Code review Moderate

Code review: flag any new code that handles input from this surface without using the validated framework helpers.

CWE-1384

Don't catalog this weakness. Prove it's reachable.

Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.

Request AI Swarm Pentest

Frequently asked questions

What is CWE-1384?

This weakness occurs when a hardware device fails to manage unexpected physical or environmental situations, whether they happen naturally or are deliberately caused by an attacker. These conditions can force the hardware into an insecure state.

How serious is CWE-1384?

MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.

What languages or platforms are affected by CWE-1384?

MITRE lists the following affected platforms: System on Chip, ICS/OT.

How can I prevent CWE-1384?

In requirements, be specific about expectations for how the product will perform when it exceeds physical and environmental boundary conditions, e.g., by shutting down. Where possible, include independent components that can detect excess environmental conditions and have the capability to shut down the product.

How does Plexicus detect and fix CWE-1384?

Plexicus's SAST engine matches the data-flow signature for CWE-1384 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.

Where can I learn more about CWE-1384?

MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/1384.html. You can also reference OWASP and NIST documentation for adjacent guidance.

Related weaknesses

Weaknesses related to CWE-1384

CWE-703 Parent

Ready to validate what matters?

Plexicus is Proof-Driven AppSec: validated findings, contextual understanding, and reviewed remediation — anchored in evidence, scoped with you.

Request AI Swarm Pentest

Improper Handling of Physical or Environmental Conditions

What is CWE-1384?

Real-world CVEs caused by CWE-1384

Step-by-step attacker path

Vulnerable pseudo

Secure pseudo

How to prevent CWE-1384

How to detect CWE-1384

Don't catalog this weakness. Prove it's reachable.

Frequently asked questions

Weaknesses related to CWE-1384

Improper Check or Handling of Exceptional Conditions

Improper Handling of Syntactically Invalid Structure

Uncaught Exception

Unchecked Error Condition

Missing Report of Error Condition

Return of Wrong Status Code

Declaration of Throws for Generic Exception

Improper Check for Unusual or Exceptional Conditions

Improper Handling of Exceptional Conditions

Further reading

Ready to validate what matters?

Check whether AI Swarm Pentest fits your environment.

Request received. Book the next step.

Sample evidence handover

Server-Side Request Forgery in `webhooks/receiver`