...
- Be wary when using and placement of statements such as break, continue, and return, as they're indicators that segments of code are at risk of being unreachable; as stated by "Case-Based Reasoning Research and Development: 24th International Conference".
- Use Structured Programming to help better the design of code therefore reducing the unnecessary use of break and continue;
- Modularize code as much as possible rather than combining methods/methods/classes/etc. into one.
- [LINK] This issue outlines that ...
- [LINK] This issue outlines that ...
Noncompliant Code Example
...
| Code Block | ||
|---|---|---|
| ||
int x = 1;
if (x == 1){
x += 1;
return x;
}
|
Exceptions
Risk Assessment
...
Rule | Severity | Likelihood | Remediation Cost | Priority | Level |
|---|---|---|---|---|---|
TBD | Medium | Probable | Medium |
|
|
Automated Detection
Tools are available online, such as ProGuard, that help clean up code by removing unused statements that may have been a result of code being unreachable.
Tool | Version | Checker | Description |
|---|---|---|---|
| TBD |
|
Related Vulnerabilities
...
In the URL example above, <RULE_ID> should be substituted by this CERT guideline ID (e.g., INT31-C). Then, remove this purple-font paragraph.
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
Related Guidelines
Fill in the table below with at least one entry row, per these instructions, then remove this purple-font section.
| DRD10-X. Do not release apps that are debuggable | Issues of bugs and discrepency within the code relates to this rule. | TBD (e.g., MITRE CWE) |
Bibliography
| [TBD] |