CWE-670: Always-Incorrect Control Flow Implementation

ClassDraft

The code contains a control flow path that does not reflect the algorithm that the path is intended to implement, leading to incorrect behavior any time this path is navigated.

View on MITRE
Back to CWE Lookup

Extended Description

This weakness captures cases in which a particular code segment is always incorrect with respect to the algorithm that it is implementing. For example, if a C programmer intends to include multiple statements in a single block but does not include the enclosing braces (CWE-483), then the logic is always incorrect. This issue is in contrast to most weaknesses in which the code usually behaves correctly, except when it is externally manipulated in malicious ways.

Technical Details

Structure
Simple

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-670 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-670, Always-Incorrect Control Flow Implementation, 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 FrameworkNational Institute of Standards and Technology

Make elimination of CWE-670 a product outcome

Apply CISA's Secure by Design principle of taking ownership of customer security outcomes to CWE-670, Always-Incorrect Control Flow Implementation. Put the weakness in the product threat model and security roadmap, fund class-level design and platform changes, prefer safe defaults and reusable guardrails, and publish measurable progress. Do not transfer the primary burden to customer configuration when the manufacturer can remove or contain the root cause in the product.

Shifting the Balance of Cybersecurity Risk: Secure by Design SoftwareCybersecurity and Infrastructure Security Agency

Connect Always-Incorrect Control Flow Implementation to documented attack evidence

Recorded impacts include Other, and Alter Execution Logic; observed examples include CVE-2021-3011; related weaknesses include CWE-691. Use these source-defined anchors to turn CWE-670 into implementation, review, and verification checks for the affected component.

CWE-670: Always-Incorrect Control Flow ImplementationMITRE CWE

Apply precise root-cause mapping to CWE-670

Apply MITRE's full root-cause mapping guidance when using CWE-670, Always-Incorrect Control Flow Implementation. 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 GuidanceMITRE CWE

Validate CWE-670 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-670, Always-Incorrect Control Flow Implementation. 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 TipsMITRE CWE

Frequently Asked Questions

What is CWE-670: Always-Incorrect Control Flow Implementation?+

CWE-670: Always-Incorrect Control Flow Implementation is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The code contains a control flow path that does not reflect the algorithm that the path is intended to implement, leading to incorrect behavior any time this path is navigated. This weakness captures cases in which a particular code segment is always incorrect with respect to the algorithm that it is implementing. For example, if a C programmer intends to include multiple statements in a single block but does not include the enclosing braces (CWE-483), then the logic is always incorrect. This issue is in contrast to most weaknesses in which the code usually behaves correctly, except when it is externally manipulated in malicious ways.

What are the security consequences of Always-Incorrect Control Flow Implementation?+

If exploited, CWE-670 (Always-Incorrect Control Flow Implementation) it can compromise Other, leading to outcomes such as Other and Alter Execution Logic.

Which programming languages are affected by Always-Incorrect Control Flow Implementation?+

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

What are real-world examples of Always-Incorrect Control Flow Implementation?+

MITRE documents real CVEs mapped to CWE-670, including CVE-2021-3011. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

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

A CWE (Common Weakness Enumeration) like CWE-670 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

Advertisement