提出 #1052045: Cockpit-HQ Cockpit CMS 2.12.0 - 2.14.1 Authentication Bypass情報

タイトルCockpit-HQ Cockpit CMS 2.12.0 - 2.14.1 Authentication Bypass
説明Product: Cockpit CMS (Cockpit-HQ/Cockpit, PHP headless CMS; maintained continuation of agentejo/cockpit) Affected versions: 2.12.0 through 2.14.1 (current, unfixed). The web-worker entry point was introduced in 2.12.0 with this exact guard (tag bisect: cron.php absent at 2.11.0; vulnerable guard present at 2.12.0 and 2.14.1). SUMMARY: Cockpit CMS includes a web-based entry point for its worker (cron.php) guarded by a token check that fails open when the token is not configured: $webToken = $master->retrieve('worker/web/token'); if ($webToken && ($_GET['token'] ?? '') !== $webToken) { die('{"info": "Not authorized"}'); } When worker/web/enabled is true but the operator has not set worker/web/token, $webToken is falsy and the && short-circuits past the whole comparison -- there is no fail-closed branch for the 'feature enabled, token not configured' state. An unauthenticated remote attacker can start the web worker with a plain GET /cron.php, causing the CMS queue-processing loop (master queue plus every space queue) to execute on the attacker's request and holding a PHP execution slot for about 24 seconds per request (repeatable). Nothing in the repository documentation requires a token when enabling the web worker. ROOT CAUSE: cron.php:33-41 (web-entry guard); worker execution loop at cron.php:125-167 (master + every space queue processed every 100 ms for ~24 s per request; worker registered in storage/data/app.workers.pid). PROOF OF CONCEPT: live-verified on stock 2.14.1 (commit 489c3330) in Docker, four-test control matrix plus a server-side PID-file artifact. The unauthenticated request returns {"info": "Webworker started"} and runs the queue loop for 24.59 s when no token is configured, versus {"info": "Not authorized"} in 5 ms when a token is configured. The unauthenticated worker registers with mode 'web'. IMPACT / CVSS: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L = 4.7 (Medium). AC:H reflects two environmental preconditions: worker/web/enabled must be enabled (opt-in, default false) AND the operator must not have set worker/web/token. I:L/A:L: the attacker forces execution of queued jobs on demand, bypassing the intended cron schedule (jobs with side effects run early or repeatedly), and each request holds a PHP execution slot for ~24 s, repeatable. CWE-306 (Missing Authentication for Critical Function). FIX: fail closed when worker/web/enabled is true and worker/web/token is empty -- refuse the request (or refuse to enable the feature) instead of skipping authentication; document that enabling the web worker requires setting a token. DISCLOSURE: MITRE CNA-LR ticket 2098315 (MCID 15926918) was withdrawn by email on 2026-10-22 (Message-ID <[email protected]>). The maintainer was notified directly at [email protected] on 2026-10-22. Public sanitized advisory and reproduction: https://github.com/LeoWSY-hashblue/cve-tls-followup/tree/master/cockpit-failopen DEDUP: NVD/GitHub searched. The Cockpit ecosystem has 25+ published GHSA advisories (upload/XSS/NoSQL/traversal/RCE classes); none covers authentication of the cron.php web worker or the worker/web/token fail-open. A separate CWE-295 finding in the same code path was reported as issue #318 and fixed in 2.14.1; it is a different root cause.
ソース⚠️ https://github.com/LeoWSY-hashblue/cve-tls-followup/tree/master/cockpit-failopen
ユーザー
 NeoWSY (UID 82976)
送信2026年10月22日 14:02 (29 日 ago)
モデレーション2026年11月20日 20:33 (29 days later)
ステータス承諾済み
VulDBエントリ441597 [Cockpit-HQ Cockpit 迄 2.14.1 Web Worker cron.php token 弱い認証]
ポイント20

Want to stay up to date on a daily basis?

Enable the mail alert feature now!