Skip to content

Security: SyanCode/Mas

Security

SECURITY.md

Security policy

Mas runs as root and manages nginx, systemd, certificates and DNS records, so security reports are taken seriously.

Reporting a vulnerability

Please do not open a public issue. Use GitHub's private reporting instead: Security → Report a vulnerability on this repository.

Include what you can: affected version (mas --version), steps to reproduce, impact. You will get an answer as soon as possible; fixes are released with a note in the changelog once users have had a chance to update.

Supported versions

Mas is in beta: only the latest release receives security fixes.

Scope

In scope: the API and dashboard, authentication (passwords, TOTP and recovery codes, sessions, CSRF, read-only accounts), CMS editor accounts and their permissions per site (and the read-only "view as" of an administrator), preview deployments, hosted files and their download links (/d/<id>), the backups of Mas and their S3 copy, the deployment pipeline, the generated nginx/systemd configuration, the GitHub webhook, the DNS provider integrations and the installer. The security model describes what Mas is designed to protect against.

Dependencies of the hosted apps

Mas checks the packages installed with each app against the public OSV database every day and after each release (mas deps, the Dependencies page). Only package names and versions are sent to api.osv.dev, never code, files or domains; development packages are not sent. Turn it off with mas deps --off (only an administrator signed in, never an API token, can change it). A vulnerable package is reported in Health and by the server alerts with the version to upgrade to.

Mas then upgrades it by itself (mas deps --auto push, the default; pr for a pull request, off to only be told). The new lock file is computed with npm --package-lock-only --ignore-scripts as the user nobody, in a temporary folder holding only package.json and package-lock.json (no .npmrc, no secret, no code of the app): no package is installed and no package script runs at that step. The commit goes through the GitHub App on the deployed branch, so it is built by the usual pipeline as the app's own user; a failed release is undone by a second commit. Only security fixes inside the same major version are made. Changing this mode needs an administrator signed in, never an API token. The vhosts Mas writes hide the nginx version and the X-Powered-By header, but a framework can still print its version in its own files: keeping the packages up to date is the fix.

There aren't any published security advisories