We release patches for security vulnerabilities for the following versions:
| Version | Supported |
|---|---|
| latest | ✅ |
| < 0.1.0 | ❌ |
If you discover a security vulnerability within this project, please send an email to jan.scheffler@qodev.ai. All security vulnerabilities will be promptly addressed.
Please include the following information in your report:
- Type of vulnerability
- Full paths of affected source file(s)
- Location of the affected source code (tag/branch/commit or direct URL)
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if possible)
- Impact of the issue, including how an attacker might exploit it
When deploying this scheduler:
-
Docker Socket Access: The scheduler requires read access to
/var/run/docker.sock. This grants significant privileges. Only run the scheduler in trusted environments. -
Container Execution: The scheduler executes commands in other containers via
docker exec. Ensure that:- Container labels are only set by trusted sources
- Commands in cronjob labels are reviewed before deployment
- Containers running scheduled jobs have appropriate security constraints
-
Network Isolation: Consider running the scheduler in a separate Docker network with limited access.
-
Logging: Enable logging to monitor executed jobs and detect suspicious activity. Set
LOG_LEVEL=DEBUGto see detailed execution logs.
When we receive a security vulnerability report, we will:
- Confirm the problem and determine affected versions
- Audit code to find similar problems
- Prepare fixes for all supported versions
- Release new versions as soon as possible
Thank you for helping keep this project secure!