CWE-691: Insufficient Control Flow Management

PillarDraft

The code does not sufficiently manage its control flow during execution, creating conditions in which the control flow can be modified in unexpected ways.

View on MITRE
Back to CWE Lookup

Technical Details

Structure
Simple

Applicable To

Languages
Not Language-Specific
Platforms

Frequently Asked Questions

What is CWE-691: Insufficient Control Flow Management?+

CWE-691: Insufficient Control Flow Management is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The code does not sufficiently manage its control flow during execution, creating conditions in which the control flow can be modified in unexpected ways.

What are the security consequences of Insufficient Control Flow Management?+

If exploited, CWE-691 (Insufficient Control Flow Management) it can compromise Other, leading to outcomes such as Alter Execution Logic.

Which programming languages are affected by Insufficient Control Flow Management?+

CWE-691 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 Insufficient Control Flow Management?+

MITRE documents real CVEs mapped to CWE-691, including CVE-2019-9805, CVE-2014-1266 and CVE-2011-1027. 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-691 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