Security

Security

DBNova is effectively a superuser console for your MySQL server, so it is built defensively.

#What DBNova does

  • Passwords never reach logs or stack traces. Password parameters are marked #[\SensitiveParameter].
  • Credentials live only in the encrypted session.
  • Exact account matching refuses sign-ins that MySQL matches to a different account.
  • Rate limits on sign-in, password re-entry and every write route.
  • One SQL statement per call. Multi-statements are off at the driver.
  • Option files for the mysql / mysqldump CLI refuse line-break injection.
  • Identifier validation is fuzz-tested against a real server: a canary database must survive hostile names.
  • Read-only mode is enforced in the data layer, not just hidden in the UI.
  • Typed confirmations for DROP and TRUNCATE.
  • Audit log that never stores row values.
  • Dependencies are audited in CI (composer audit, npm audit), with CodeQL scanning and Dependabot.

#What you should do

  • Don't expose DBNova publicly without HTTPS. Prefer a VPN or an IP allow-list.
  • For untrusted dumps, import with an account limited to the target database.
  • Remove anonymous MySQL accounts (mysql_secure_installation).
  • Set zend.exception_ignore_args = On in production.

#Reporting a vulnerability

Please do not open a public issue. Use GitHub's private reporting: Security → Report a vulnerability on the repository. Include what an attacker can do, the steps to reproduce it, and your DBNova, PHP and MySQL versions.

0 views Something unclear? Open an issue on GitHub