Configuration vulnerability in Source interface partially mitigated

THREAT5 · Partially mitigated: Some controls are in place, but the risk is still too high. · Defined in catalog.py:98

Risk
High impact × Medium likelihood = 9 high
After mitigations
High impact × Medium likelihood = 9 high (unchanged)

How statuses and scores work

Misconfiguration of the SecureDrop instance may facilitate or introduce vulnerabilities in the application or infrastructure. For example, weak Flask secret keys could be configured manually by a user by mistake.

Threat actors: Any

Mitigations

Mitigation Status
Config managed by securedrop-client sdconfig CLI tool MITIG240 implemented

Possible further mitigations

Residual risk

Admins can overwrite each other's site-specific changes.

Where it applies

Applies to 1 component in 2 scenarios.

Source submission · SecureDrop Application
Physical and host layer · SecureDrop Application

Notes

Existing mitigations: All components are up to date with proper security configuration and versions. Configuration is tracked in the SecureDrop source repository, and installation-specific configuration is found in install_files/ansible-base/group_vars/all/site-specific and modified by securedrop-admin sdconfig (MITIG240). Further mitigations: Improve config story for SecureDrop (this is ticket https://github.com/freedomofpress/securedrop/issues/1966), and improve UX around modifying server config (https://github.com/freedomofpress/securedrop/issues/344) (MITIG242). Discourage admins from modifying state by hand (MITIG62). Prevent admins from overwriting each other's config changes (MITIG241). Automated test for mitigation: Partial.

How this threat is matched

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