Insufficient Control Flow Management

Opis

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

Skutki

• Other

  Alter Execution Logic

Przykłady podatności

• CVE-2024-50653 e-commerce product does not restrict the number of requests for coupons
• CVE-2019-9805 Chain: Creation of the packet client occurs before initialization is complete (CWE-696) resulting in a read from uninitialized memory (CWE-908), causing memory corruption.
• 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). The code's whitespace indentation did not reflect the actual control flow (CWE-1114) and did not explicitly delimit the block (CWE-483), which could have made it more difficult for human code auditors to detect the vulnerability.
• CVE-2011-1027 Chain: off-by-one error (CWE-193) leads to infinite loop (CWE-835) using invalid hex-encoded characters.

Słabości podrzędne

• CWE-430 Deployment of Wrong Handler
• CWE-431 Missing Handler
• CWE-662 Improper Synchronization
• CWE-670 Always-Incorrect Control Flow Implementation
• CWE-696 Incorrect Behavior Order
• CWE-705 Incorrect Control Flow Scoping
• CWE-768 Incorrect Short Circuit Evaluation
• CWE-799 Improper Control of Interaction Frequency
• CWE-834 Excessive Iteration
• CWE-841 Improper Enforcement of Behavioral Workflow
• CWE-1281 Sequence of Processor Instructions Leads to Unexpected Behavior

Kiedy powstaje

• Architecture and Design
• Implementation

Dotyczy

Not Language-Specific, Not Technology-Specific