Skip to content

Security: serveroshq/.github

Security

SECURITY.md

Security policy

This policy covers every ServerOS repository that doesn't have its own SECURITY.md, plus serveros.com and ServerOS Cloud.

Reporting a vulnerability

Please don't open a public issue, discussion or pull request for a security problem.

Report it privately:

  • On GitHub: open the repo's Security tab and click Report a vulnerability
  • By email: security@serveros.com

Please include what's affected (repo and version, or URL), steps to reproduce, what an attacker could do with it, and whether you'd like credit.

What happens next

  • We reply within 3 working days to say we've got it.
  • We confirm whether it's a real issue, and how serious, as soon as we can, usually within 10 working days.
  • We fix it, release the fix and publish an advisory, crediting you if you want.
  • We ask that you give us 90 days, or until a fix is out if that's sooner, before you talk about it publicly.

Rules for testing

Test against your own install wherever you can. On serveros.com and ServerOS Cloud, only use accounts and servers you own, stop as soon as you reach anyone else's data, and don't run denial of service, spam, social engineering or heavy automated scans.

If you follow these rules and act in good faith, we won't take legal action against you or ask anyone else to, and we'll treat your research as authorised.

There aren't any published security advisories