8000 Overview · kividbio/kividb · GitHub
[go: up one dir, main page]

Skip to content

Security: kividbio/kividb

SECURITY.md

Security policy

Reporting a vulnerability

Please report security vulnerabilities privately. Do not open a public GitHub issue, pull request or discussion for a vulnerability, and do not disclose it publicly until a fix has been released.

Report it by either of these:

Please include:

  • the KiviDB version (kividb --version) and build variant (default, lua, tls or full), and how you installed it (binary, package, Docker image, built from source);
  • the operating system and architecture;
  • the relevant configuration (flags or config file, with passwords removed);
  • the steps or commands that reproduce the problem, and what an attacker gains;
  • whether the issue is already known to anyone else.

What happens next

  • We acknowledge your report within [RESPONSE TIME, e.g. 3 business days].
  • We aim to confirm or rule out the issue, and share our plan for a fix, within [ASSESSMENT TIME, e.g. 10 business days].
  • We keep you informed of progress, agree a disclosure date with you, and credit you in the release notes unless you prefer otherwise.

Supported versions

Security fixes are made for the latest release line only.

Version Security fixes
1.1.x Yes
< 1.1 No

Upgrade to the latest 1.1.x release to receive fixes.

Package signing key

The apt and dnf repositories at packages.kividb.io, and every RPM in them, are signed with one OpenPGP key. Its fingerprint is published here and in docs/INSTALL.md, in this repository, so that the key the site serves can be checked against a copy that the site does not serve:

Fingerprint: not published yet. It is published here once the key exists.

If the key a repository offers has any other fingerprint, do not install from it, and report it as above.

Deployment advice

KiviDB, like Redis, is meant to run on a trusted network. In particular:

  • keep protected mode on, or set a password (--requirepass or ACL users) before accepting clients from other machines;
  • do not expose the server port, or the cluster bus port (<port> + 10000), to the internet;
  • use a TLS build (tls or full) with --tls-port when traffic crosses an untrusted network.
Learn more about advisories related to kividbio/kividb in the GitHub Advisory Database
0