Error handling and logging vulnerability in Journalist interface mitigated

THREAT26 · Mitigated: Controls in place bring the risk down to an acceptable level. · Defined in catalog.py:459

Risk
Medium impact × Low likelihood = 4 medium
After mitigations
Medium impact × Low likelihood = 4 medium (unchanged)

How statuses and scores work

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
Journalist interface: Sensitive information is not logged MITIG216 implemented

Where it applies

Applies to 1 component in 2 scenarios.

Journalist triage · Journalist Interface
Workstation: reading submissions · Journalist Interface

Notes

Existing mitigations: Debug/Stack traces are disabled on production deployments (MITIG70). Sensitive information is not logged (MITIG216). Automated test for mitigation: Yes.

How this threat is matched

Listed for these components. A boundary covers every component inside it.