DGopher connects to production databases and handles their passwords, so security reports are welcome and taken seriously.
Report it privately through GitHub:
- Open the repository's Security tab.
- Choose Report a vulnerability.
- Describe the problem, how to reproduce it, and what an attacker could do with it.
Please do not open a public issue or pull request for a vulnerability until a fix is released.
Fixes go into the latest release. Update to the latest release before reporting, and say which version you tested.
Problems in DGopher itself, for example:
- A statement that bypasses the safety policy: a write or destructive statement that runs without the confirmation its environment requires, or a write on a read-only connection.
- A secret that reaches a project file, a log, query history or the audit log, or a password sent to a destination other than the one it was saved for (see Secrets).
- A project file (
dgopher.json, a query file, a dashboard, a data model, or a shipped.dgopher/folder) that makes the app read or write files outside the project, run a command, or connect without asking. - An audit log that can be changed without Verify Integrity noticing.
- TLS or SSH host verification that accepts what it should refuse.
- What a database server does once it accepts a statement. For a hard guarantee, connect as a role with only the privileges it needs (see What the policy cannot catch).
- Items already listed in Known limitations.
- Unsigned installers: the builds are not signed yet.