CWE-369 Divide By Zero

The product divides a value by zero.

• Availability: DoS: Crash, Exit, or Restart — A Divide by Zero results in a crash.

• Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.) • Fuzzing: Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.

• CVE-2007-3268: Invalid size value leads to divide by zero. • CVE-2007-2723: "Empty" content triggers divide by zero. • CVE-2007-2237: Height value of 0 triggers divide by zero.