Vulnerability disclosure
How to report a security problem in HF Panel privately, how fast we answer, safe harbour for researchers and what is in scope.
If you find a security problem in HF Panel, HF Mail, HF Files, HF Studio, HF Server or HF Tunnel, please tell us privately so we can fix it before anyone can misuse it.
Report a vulnerability
Email security@hostfog.io. The same address is published in
https://hostfog.io/.well-known/security.txt, and every HF Panel server publishes its own administrator's
address in its own /.well-known/security.txt.
Please include:
- the HF Panel version (in
/etc/hostfog/VERSION, or on Server Admin › Server › HF Panel updates) and the operating system; - the steps to reproduce the problem, and what an attacker gains;
- a proof of concept, if you have one.
Never report a vulnerability in a public forum post, ticket or code review. If you want to encrypt your report, ask for a key in a short first message without details.
Note: a problem with one server, such as a hacked website or spam sent from an account, is for that server's administrator, not for this address.
What happens next
| Step | Target |
|---|---|
| We confirm we have your report | within 3 working days |
| First assessment: valid or not, and how severe | within 10 working days |
| Fix released for critical and high severity | within 30 days |
| Fix released for medium and low severity | in a regular release, normally within 90 days |
| Public disclosure | agreed with you after the fix is out, or 90 days after the report at the latest |
We keep you informed while we work on it, and we thank you in the release notes unless you prefer not to be named. Fixes ship as signed releases: servers with automatic updates get them overnight.
Supported versions
| Version | Security fixes |
|---|---|
| 1.0.x, the latest release | yes |
| older pre-release builds | no: update to the latest release first |
Safe harbour
We will not take legal action against anyone who, in good faith:
- tests only on servers and accounts they own or are allowed to test, such as their own HF Panel server or the HF Server desktop app on their own computer;
- does not harm other people's privacy, data or services, and stops as soon as they reach data that is not theirs;
- does not use denial-of-service, spam, social engineering or physical attacks;
- reports what they found promptly and keeps it confidential until it is fixed.
If you are unsure whether something is allowed, ask first.
Scope
| In scope | Out of scope |
|---|---|
| hf-api: the panels, the API, HF Mail, HF Files, HF Studio and the web disk | other software HF Panel installs (Nginx, Apache, PHP, databases, mail servers), unless HF Panel sets it up insecurely |
| hf-agent, the root helper, and how the panel calls it | customers' own websites and applications |
| the installer, updates and the signing of releases | problems that need root, physical access, or an administrator turning a protection off |
| the HF Server desktop app and HF Tunnel | missing best-practice headers or scanner output without a working proof |