CWE-561 Base Draft

Dead Code

Dead code refers to sections of a program that can never run during normal execution, effectively making them inactive and unreachable.

Definition

What is CWE-561?

Dead code refers to sections of a program that can never run during normal execution, effectively making them inactive and unreachable.
Dead code occurs when logic within the program, such as conditional statements or function calls, permanently prevents its execution. This often results from overly restrictive conditions, code that's been commented out but left in place, or legacy functions that are no longer invoked after software updates. While not directly exploitable like a vulnerability, it bloats the codebase, obscures real issues during security reviews, and can mislead developers about the program's actual behavior. From a security and maintenance perspective, dead code creates unnecessary noise during static analysis and manual audits, potentially causing real vulnerabilities to be overlooked. It also increases the attack surface by adding complexity without providing value. Regularly removing dead code through refactoring and using code coverage tools helps keep the application lean, understandable, and easier to secure.
Real-world impact

Real-world CVEs caused by CWE-561

  • CVE-2014-1266

    chain: incorrect "goto" in Apple SSL product bypasses certificate validation, allowing Adversary-in-the-Middle (AITM) attack (Apple "goto fail" bug). CWE-705 (Incorrect Control Flow Scoping) -> CWE-561 (Dead Code) -> CWE-295 (Improper Certificate Validation) -> CWE-393 (Return of Wrong Status Code) -> CWE-300 (Channel Accessible by Non-Endpoint).

How attackers exploit it

Step-by-step attacker path

  1. 1

    The condition for the second if statement is impossible to satisfy. It requires that the variables be non-null. However, on the only path where s can be assigned a non-null value, there is a return statement.

  2. 2

    In the following class, two private methods call each other, but since neither one is ever invoked from anywhere else, they are both dead code.

  3. 3

    (In this case it is a good thing that the methods are dead: invoking either one would cause an infinite loop.)

  4. 4

    The field named glue is not used in the following class. The author of the class has accidentally put quotes around the field name, transforming it into a string constant.

Vulnerable code example

Vulnerable C++

The condition for the second if statement is impossible to satisfy. It requires that the variables be non-null. However, on the only path where s can be assigned a non-null value, there is a return statement.

Vulnerable C++ 
String s = null;
  if (b) {
  	s = "Yes";
  	return;
  }
  if (s != null) {
  	Dead();
  }
Secure code example

Secure pseudo

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-561

  • Implementation Remove dead code before deploying the application.
  • Testing Use a static analysis tool to spot dead code.
Detection signals

How to detect CWE-561

Architecture or Design Review High

According to SOAR [REF-1479], the following detection techniques may be useful: ``` Highly cost effective: ``` Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.) Formal Methods / Correct-By-Construction ``` Cost effective for partial coverage: ``` Attack Modeling

Automated Static Analysis - Binary or Bytecode High

According to SOAR [REF-1479], the following detection techniques may be useful: ``` Highly cost effective: ``` Binary / Bytecode Quality Analysis Compare binary / bytecode to application permission manifest

Dynamic Analysis with Manual Results Interpretation SOAR Partial

According to SOAR [REF-1479], the following detection techniques may be useful: ``` Cost effective for partial coverage: ``` Automated Monitored Execution

Automated Static Analysis SOAR Partial

According to SOAR [REF-1479], the following detection techniques may be useful: ``` Cost effective for partial coverage: ``` Permission Manifest Analysis

Automated Static Analysis - Source Code High

According to SOAR [REF-1479], the following detection techniques may be useful: ``` Highly cost effective: ``` Source Code Quality Analyzer ``` Cost effective for partial coverage: ``` Warning Flags Source code Weakness Analyzer Context-configured Source Code Weakness Analyzer

Dynamic Analysis with Automated Results Interpretation SOAR Partial

According to SOAR [REF-1479], the following detection techniques may be useful: ``` Cost effective for partial coverage: ``` Web Application Scanner Web Services Scanner Database Scanners

Plexicus auto-fix

Plexicus auto-detects CWE-561 and opens a fix PR in under 60 seconds.

Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.

Get a demo Try Plexicus free
Frequently asked questions

Frequently asked questions

What is CWE-561?

Dead code refers to sections of a program that can never run during normal execution, effectively making them inactive and unreachable.

How serious is CWE-561?

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-561?

MITRE has not specified affected platforms for this CWE — it can apply across most application stacks.

How can I prevent CWE-561?

Remove dead code before deploying the application. Use a static analysis tool to spot dead code.

How does Plexicus detect and fix CWE-561?

Plexicus's SAST engine matches the data-flow signature for CWE-561 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-561?

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

Related weaknesses

Weaknesses related to CWE-561

CWE-1164 Parent

Irrelevant Code

Irrelevant code refers to sections of a program that have no impact on its execution, data, or logic. Removing this code would not change…

CWE-107 Sibling

Struts: Unused Validation Form

This vulnerability occurs when a Struts application contains validation form definitions that are no longer linked to any active form or…

CWE-1071 Sibling

Empty Code Block

An empty code block occurs when a section of source code, such as a conditional statement or function body, contains no executable…

CWE-110 Sibling

Struts: Validator Without Form Field

This vulnerability occurs when a Struts application's validation configuration file references form fields that no longer exist in the…

CWE-563 Sibling

Assignment to Variable without Use

This vulnerability occurs when a value is stored in a variable, but that variable is never read or used in subsequent code, creating a…

Resources

Further reading

Ready when you are

Don't Let Security
Weigh You Down.

Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.

Get started free Book a demo