Error handling and logging vulnerability in Source interface mitigated
THREAT22
· Mitigated: Controls in place bring the risk down to an acceptable level.
· Defined in catalog.py:394
- Risk
- Medium impact × Low likelihood = 4 medium
- After mitigations
- Medium impact × Low likelihood = 4 medium (unchanged)
Improper error handling may lead to an adversary obtaining additional information on the application that may be used to find other vulnerabilities
Threat actors: Any
Mitigations
| Mitigation | Status |
|---|---|
| Debugging is disabled MITIG70 | implemented |
| Logging off for source interface MITIG41 | implemented |
Where it applies
Applies to 1 component in 2 scenarios.
Source submission · Source Interface
Supply chain and dependencies · Source Interface
Notes
Existing mitigations: Debug/Stack traces are disabled on production deployments (MITIG70). Sensitive information is not logged. All error logging on source interface is disabled. (MITIG41). Automated test for mitigation: No.
How this threat is matched
Listed for these components. A boundary covers every component inside it.