| Wiki Markup |
|---|
MemoryDynamic memory management is a common source of programming flaws that can lead to security vulnerabilities. Decisions regarding how dynamic memory is allocated, used, and deallocated are the burden of the programmer. Poor memory management can lead to security issues such as heap-buffer overflows, dangling pointers, and double-free issues \[Seacord 05\]. From the programmer's perspective, memory management involves allocating memory, reading and writing to memory, and deallocating memory. |
...
Recommendation | Severity | Likelihood | Remediation Cost | Priority | Level |
|---|---|---|---|---|---|
MEM00-A | 3 (high) | 2 (probable) | 1 (high) | P6 | L2 |
MEM01-A | 3 (high) | 2 (probable) | 3 (low) | P18 | L1 |
Rule | Severity | Likelihood | Remediation Cost | Priority | Level |
|---|---|---|---|---|---|
MEM30-C | 3 (high) | 3 (likely) | 2 (medium) | P18 | L1 |
MEM31-C | 3 (high) | 2 (probable) | 1 (high) | P6 | L2 |
MEM32-C | 1 (high) | 3 (likely) | 2 (high) | P6 | L1 |
MEM33-C | 2 (medium) | 1 (unlikely) | 3 (low) | P6 | L2 |
MEM34-C | 1 (high) | 3 (likely) | 2 (high) | P6 | L1 |
MEM35-C | 3 (high) | 2 (probable) | 1 (high) | P6 | L2 |
MEM36-C | 3 (high) | 2 (probable) | 2 (medium) | P12 | L1 |
MEM37-C | 3 (high) | 1 (low) | 1 (high) | P12 | L1 |
...