CWE-1119: Excessive Use of Unconditional Branching
The code uses too many unconditional branches (such as "goto").
View on MITREExtended Description
This issue makes it more difficult to understand and/or maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities. It also might make it easier to introduce vulnerabilities.
Technical Details
- Structure
- Simple
Applicable To
Security Consequences
Scope
Impact
Mitigation Strategies
No mitigation information available for this CWE.
Detection Methods
No detection method information available for this CWE.
Code Examples & CVEs
No examples or observed CVEs available for this CWE.
CWE Relationships
No relationship information available for this CWE.
Frequently Asked Questions
What is CWE-1119: Excessive Use of Unconditional Branching?+
CWE-1119: Excessive Use of Unconditional Branching is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The code uses too many unconditional branches (such as "goto"). This issue makes it more difficult to understand and/or maintain the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities. It also might make it easier to introduce vulnerabilities.
What are the security consequences of Excessive Use of Unconditional Branching?+
If exploited, CWE-1119 (Excessive Use of Unconditional Branching) it can compromise Other, leading to outcomes such as Reduce Maintainability.
What is the difference between a CWE and a CVE?+
A CWE (Common Weakness Enumeration) like CWE-1119 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.