The product contains modules in which one module has references that cycle back to itself, i.e., there are circular dependencies.
As an example, with Java, this weakness might indicate cycles between packages.
This issue makes it more difficult to maintain the product due to insufficient modularity, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities. It also might make it easier to introduce vulnerabilities.
This issue can prevent the product from running reliably. If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability.
| Nature | Mapping | Type | ID | Name |
|---|
| Nature | Mapping | Type | ID | Name |
|---|
| Nature | Mapping | Type | ID | Name |
|---|
| Scope | Likelihood | Impact | Note |
|---|---|---|---|
| Other | N/A | Reduce Reliability | N/A |
| Reference | Description |
|---|
| Ordinality | Description |
|---|---|
| Indirect | N/A |
This entry is primarily a quality issue with no direct security implications.
Look for weaknesses that are focused specifically on insecure behaviors that have more direct security implications.
| Taxonomy Name | Entry ID | Fit | Entry Name |
|---|---|---|---|
| OMG ASCMM | ASCMM-MNT-7 | N/A | N/A |
| OMG ASCRM | ASCRM-RLB-13 | N/A | N/A |
| ID | Name |
|---|