ChronoStack is in its design phase. No releases exist, so there is no deployed code that could contain a vulnerability yet. This policy defines how security will be handled from the first release onward. Design-level security concerns are welcome now.
Please do not report security vulnerabilities through public issues, discussions or pull requests.
Use GitHub private vulnerability reporting: open the repository's Security tab and click "Report a vulnerability". It is enabled for this repository. There is no separate email contact.
Please include:
- the affected component (CLI,
clockd, preload library, MCP server, SDK); - the version or commit;
- reproduction steps;
- the impact you have identified.
These are targets; the project has no maintainer team yet, so please be patient:
- acknowledgement within 7 days;
- an initial assessment within 14 days;
- coordinated disclosure: we agree on a disclosure date with you, normally within 90 days of the report, or sooner once a fix is released;
- credit in the release notes, unless you prefer to remain anonymous.
| Version | Supported |
|---|---|
| None released | — |
Planned policy:
- Before 1.0, only the latest minor release receives security fixes.
- From 1.0, the latest minor release plus the previous one, for 6 months.
- ChronoStack must never change the host or VM operating-system clock. It does not use
settimeofday/clock_settimeand does not requestCAP_SYS_TIME. - It needs no privileged containers, and no container receives the Docker socket.
- The controller API binds to
127.0.0.1only and requires a per-session random token stored with user-only permissions. - The MCP server uses stdio only, exposes a fixed tool set, and cannot execute arbitrary commands. Only triggers declared in
chronostack.ymlcan run. - Reports and logs never include environment variables, and they redact likely secrets.
Any behaviour that breaks these boundaries is a security vulnerability.
- Preload library in every process. A bug in
libchronoclockcould crash or hang processes in your stack, including databases. Mitigations:- a minimal, allocation-free design;
- fail-open by default;
- a dedicated no-hang test suite.
- Triggers execute commands.
chronostack.ymltriggers run commands in your containers. They carry the same trust level asdocker compose upon that repository. Review them before running. - Virtual timestamps persist. Data written while time is shifted stays in ChronoStack's volumes. Never point ChronoStack at a database holding data you care about.
- Local API. Any process running as your user can read the session token and change the virtual clock.
Details: docs/SECURITY_AND_RELIABILITY.md