Security
How to report a vulnerability in Maran, what is in scope and what is not, the response times you can expect, and what the project does on its own side.
Maran installs a daemon that runs as root and a panel that provisions system users. A defect here can be serious, so we welcome reports and answer every one.
Reporting a vulnerability
Write to security@innovayse.com. Do not open a public issue, and do not describe the problem in a pull request before it is fixed. If you would rather encrypt, say so in a first message with no details and a key will be sent.
Reports are acknowledged within 48 hours. For critical issues we aim to ship a fix or a documented mitigation within 14 days. Less severe ones are scheduled and we tell you when. We honour coordinated disclosure and credit you by the name you choose, unless you ask us not to.
What to include
Enough to reproduce the problem, and nothing that is not yours to send:
- what an attacker gains, such as reading another tenant's files, escalating to root or bypassing a limit;
- the smallest sequence that shows it, and which distribution and version you saw it on;
- whether it needs an authenticated session, and at which role;
- logs if they help, with tokens, hostnames and customer data removed.
Test against your own installation
Do not probe somebody else's server running this software. No finding excuses it, we do not accept reports obtained that way, and it may be a crime where you or they are. Installing your own copy takes one command.
Scope
In scope: everything the project ships, meaning the panel API, the single-page application, the Rust agent and its socket, the installer, and the templates the agent renders. Design problems are in scope too. If a written rule is the wrong rule, we want to hear it, and it is worth more than a bug.
Out of scope: findings that require an attacker to already be root on the host, denial of service by exhausting the machine's own resources, missing hardening headers with no demonstrated impact, and scanner output with no analysis attached.
Supported versions
Until 1.0, only the latest release receives fixes. After 1.0 the policy will name the versions that do.
What the project does on its own side
Changes to authentication, sessions and tokens, to the agent's privilege handling, to licence verification, or to a privileged step in the installer require a second reviewer and a written threat note before they merge. Dependencies are pinned and updated by hand, not by a bot, and secrets are never committed. Access is closed by default: an API endpoint with no declared rule is administrator-only, and a test fails if someone adds an endpoint without a rule.
The architecture is the first line of defence. The panel runs unprivileged, one small daemon holds root, and the contract between them has no operation that runs a caller-supplied program. See how it is built for the details.