Malicious message plaintext is stored in database unmanaged

THREATQW63 · Unmanaged: No decision has been made about this threat yet. · Defined in catalog.py:3896

Risk
Unknown impact × Unknown likelihood = Unknown
After mitigations
Unknown impact × Unknown likelihood = Unknown (unchanged)

How statuses and scores work

Mitigations

No mitigations in place.

Residual risk

Changes in the future could re-active the stored malicious code

Where it applies

Applies to 1 component in 2 scenarios.

Workstation: reading submissions · sd-app (SecureDrop Client)
Workstation: export and print · sd-app (SecureDrop Client)

Notes

Existing mitigations: SQL prepared statments and React escaping mitigate the possibility of executing malicious code stored in the database. Currently input isn't sanatized so this risk could be further mitigated! But there are downsides to storing messages in escaped or sanatized format?.

How this threat is matched

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