Incorrect Control Flow Scoping
Weakness ID: 705 (Weakness Class)Status: Incomplete
+ Description

Description Summary

The software does not properly return control flow to the proper location after it has completed a task or detected an unusual condition.
+ Time of Introduction
  • Architecture and Design
  • Implementation
+ Applicable Platforms

Languages

All

+ Relationships
NatureTypeIDNameView(s) this relationship pertains toView(s)
ChildOfWeakness ClassWeakness Class691Insufficient Control Flow Management
Research Concepts (primary)1000
ChildOfCategoryCategory744CERT C Secure Coding Section 10 - Environment (ENV)
Weaknesses Addressed by the CERT C Secure Coding Standard (primary)734
ChildOfCategoryCategory746CERT C Secure Coding Section 12 - Error Handling (ERR)
Weaknesses Addressed by the CERT C Secure Coding Standard734
ParentOfWeakness VariantWeakness Variant382J2EE Bad Practices: Use of System.exit()
Research Concepts (primary)1000
ParentOfWeakness BaseWeakness Base396Declaration of Catch for Generic Exception
Research Concepts (primary)1000
ParentOfWeakness BaseWeakness Base397Declaration of Throws for Generic Exception
Research Concepts (primary)1000
ParentOfWeakness BaseWeakness Base455Non-exit on Failed Initialization
Research Concepts (primary)1000
ParentOfWeakness BaseWeakness Base584Return Inside Finally Block
Research Concepts (primary)1000
ParentOfWeakness BaseWeakness Base698Redirect Without Exit
Research Concepts (primary)1000
+ Taxonomy Mappings
Mapped Taxonomy NameNode IDFitMapped Node Name
CERT C Secure CodingENV32-CAll atexit handlers must return normally
CERT C Secure CodingERR04-CChoose an appropriate termination strategy
+ Content History
Submissions
Submission DateSubmitterOrganizationSource
2008-09-09MITREInternal CWE Team
Modifications
Modification DateModifierOrganizationSource
2008-07-01Eric DalciCigitalExternal
updated Time of Introduction
2008-11-24CWE Content TeamMITREInternal
updated Relationships, Taxonomy Mappings
Back to top