Impact
A non‑administrator user or API key granted create_events and run_events privileges can insert top‑level uid and gid fields when creating or updating an event. These injected values are stored verbatim, bypassing the normal run‑as‑user check in Cronicle. As a result the scheduled job runs with the supplied UID/GID, allowing the attacker to execute commands as any user, including root. The vulnerability permits full compromise of confidentiality, integrity and availability of the underlying system where the Cronicle daemon operates.
Affected Systems
The flaw affects Cronicle deployments before version 0.9.121. It applies to any installation of jhuckaby’s Cronicle, regardless of operating system, that runs the daemon with non‑root privileges and exposes the event creation API. The patch is included in release 0.9.121 and later.
Risk and Exploitability
The CVSS score of 8.8 classifies the flaw as high severity. EPSS data is unavailable, but the lack of a documented exploit and absence in the CISA KEV catalog suggest a moderate practical risk. An attacker can exploit the issue by sending crafted API requests to /api/app/create_event or /api/app/update_event with uid/gid payloads. The ability to elevate to root is only feasible when the Cronicle daemon runs with daemon privileges and the user holds the necessary API permissions; no additional network access is required beyond the API surface.
OpenCVE Enrichment