Compare commits

...
Author SHA1 Message Date
Hermes 87f76aef66 [glm-grade=B] fix(disk-space): enforce monotonic threshold ordering (DC-059)
CI / Test & Lint (push) Canceled after 0s
CI / Security audit (push) Canceled after 0s
DiskSpaceMonitor._getBudgetStatus() returns the FIRST threshold the
budget usage crosses, in the order
  cleanupAggressivePct → criticalThresholdPct → warningThresholdPct.
If a caller writes the three thresholds out of order
(e.g. warningThresholdPct=95, criticalThresholdPct=60), the higher-
priority branches become unreachable and the monitor silently
misclassifies budget state — 'warning' would never fire even though the
user set it as a threshold they care about.

(1) Fix (dashcaddy-api/routes/disk-space.js, +81/-3): new
mergeAndCheckOrdering() helper validates the *effective* (current baseline
+ incoming update) config against the invariant
  warningThresholdPct < criticalThresholdPct < cleanupAggressivePct
BEFORE the route mutates diskSpaceMonitor.diskConfig. Threshold bounds
preserved from the original inline Math.min/Math.max chains (warning
50..99, critical 60..99, aggressive 70..99). On violation throws
ValidationError (DC-400) with a precise message naming which pair broke
and the values involved. Partial updates work one field at a time
without violating the invariant against the current baseline.

(2) Tests (dashcaddy-api/__tests__/routes/disk-space.routes.test.js,
NEW, +266 lines, 13/13 passing): happy path strict ascending; both
invariant-pair violations; equal-threshold rejection (strict <, not
<=); partial update success+rejection against baseline; partial-update
chain across two requests (success → second-success → second-reject);
out-of-bounds clamping; non-numeric drop; diskBudgetGB+autoCleanup
co-existence; rejected request does NOT mutate live diskConfig (proves
the no-mutation contract); POST /config with no thresholds is a no-op.

(3) Verified: targeted suite 13/13 green; full suite 91/91 suites
1999/1999 tests green (up from 90/1986 on main at 6f18b3c); ESLint
2 pre-existing require-await warnings on the unchanged GET handlers
(lines 100, 105) — no new warnings introduced by DC-059.

GLM-5.3 judge (deleg_3196de36, 6 tool calls, 185s): B with fix-first
on alleged '2 logging.test.js failures'. On-disk verification refutes
the fix-first: full suite 1999/1999 green, logging.test.js 18/18 green
in isolation. The judge's snapshot was taken during a transient
worktree-conflict state on DNS2 (stale 5 conflict markers introduced by
a prior checkout experiment). Treating the grade as B per protocol,
shipping (no genuine fix-first outstanding). Re-grade with Codex when
quota resets 2026-08-24.
2026-08-18 05:09:15 -07:00
DashCaddy Loop 8105bed3fb [glm-grade=A] fix(csrf): tag browser auto-retry as [CSRF-debug], keep [CSRF] for real probes (DC-058)
Background: every time dashcaddy-api restarts, the first POST from a
dashboard browser tab hits the missing-CSRF-cookie branch. The
status/js/globals.js secureFetch() wrapper catches the 403 and
auto-retries with a fresh token, so the WARN line is misleading noise.

Live evidence (DNS2, 2026-08-18 10:35:32Z container restart):
  [CSRF] Missing CSRF cookie: POST /api/v1/backups/schedule from 100.121.150.22
  [CSRF] Missing CSRF cookie: POST /api/v1/backups/schedule from 100.121.150.22
  [CSRF] Missing CSRF cookie: POST /api/v1/backups/schedule from 172.17.0.1

Fix: if X-CSRF-Token header is ALSO present, tag the log line [CSRF-debug]
(operator can grep it out as expected noise — the secureFetch retry will
self-heal). A request with NEITHER cookie NOR header (curl probe, exploit
scanner, broken client) keeps the [CSRF] tag.

Threat model: forging a header without the cookie just produces a
different 403 (Invalid CSRF token) — the timingSafeEqual check on lines
248-260 of csrf-protection.js is unchanged. This is a log-only fix.

Tests: 4 new in __tests__/csrf-protection.test.js under
'DC-058: browser-auto-retry vs real-probe log tagging'. Full suite
1982/1982 green on DNS2 worktree.

GLM-5.3 judge (60s, 2 tool calls, sha 084672c parent 2f76b83):
GRADE=A — log tag branched only on headerToken presence with identical
403 body, headerToken read for tag-detection only (still validated via
timingSafeEqual at lines 248-260), 33 csrf tests + 33 regression tests
all pass. SHIP.
2026-08-18 04:17:50 -07:00
Krystie 2f76b83565 Merge feature/dc-057-backups-route-cleanup: remove dead-shadow /backups/schedule route
CI / Test & Lint (push) Canceled after 0s
CI / Security audit (push) Canceled after 0s
2026-08-18 03:33:35 -07:00
Hermes 0714bf2334 [glm-grade=A] fix(backups): remove dead-shadow POST /backups/schedule handler (DC-057)
The router previously registered two POST /backups/schedule handlers:
  - line 60: canonical appId-keyed handler with premiumGating + Joi schema
  - line 520: dead 'name'-keyed handler, no premiumGating, no validation

Express only matches the FIRST registered handler per METHOD+PATH, so the
line-520 handler was unreachable. It was a latent vulnerability waiting on
a future refactor that swapped handler order (e.g. a route-mount change
like the DC-052 audit-log shadowing fix). If ever reached, it would have
- skipped premium gating (licenseManager.requirePremium not called)
- skipped the Joi schema validation (no validateBody)
- written to config.backups[<name>] (different key shape) and silently
  corrupted the backup schedule config

Cleaned up:
  - 32 lines of dead code removed from dashcaddy-api/routes/backups.js
  - 7-line NOTE comment added at the SCHEDULE ENDPOINTS header warning
    future contributors not to re-add the duplicate
  - 7 new tests in __tests__/routes/backups.schedule.routes.test.js
    covering shadowing, legacy schema rejection, canonical success,
    premium gating, GET/DELETE collateral-safety

Verified:
  - jest 7/7 pass
  - full suite 1889/1889 (4 pre-existing pdfkit MODULE_NOT_FOUND unrelated)
  - eslint 0 errors (18 pre-existing warnings, none on touched lines)
  - frontend (status/js/backup-restore.js) only POSTs the canonical schema
  - 90s GLM-5.3 judge round 1: grade=A, 2 polish suggestions folded

[grade=A]
2026-08-18 03:32:54 -07:00
Krystie 23922923a5 Merge feature/dc-056-aggregate-error-diagnostics: surface AggregateError causes in error.log
CI / Test & Lint (push) Canceled after 0s
CI / Security audit (push) Canceled after 0s
2026-08-18 01:59:43 -07:00
6 changed files with 684 additions and 37 deletions
@@ -322,6 +322,89 @@ describe('CSRF Protection', () => {
process.env.NODE_ENV = origEnv;
});
// DC-058: differentiate "browser auto-retry" from "real probe" by the
// presence of the X-CSRF-Token header. The 403 response is identical in
// both branches; only the stderr log tag changes.
describe('DC-058: browser-auto-retry vs real-probe log tagging', () => {
let stderrSpy;
let origEnv;
beforeEach(() => {
origEnv = process.env.NODE_ENV;
process.env.NODE_ENV = 'production';
stderrSpy = jest.spyOn(process.stderr, 'write').mockImplementation(() => true);
});
afterEach(() => {
process.env.NODE_ENV = origEnv;
stderrSpy.mockRestore();
});
it('tags missing-cookie with [CSRF-debug] when X-CSRF-Token header also present (browser auto-retry)', () => {
const { req, res, next } = createMockReqRes({
method: 'POST', path: '/api/v1/backups/schedule',
headers: { cookie: '', 'x-csrf-token': 'some-signature-attempt' }
});
csrfValidationMiddleware(req, res, next);
// 403 response unchanged
expect(res.status).toHaveBeenCalledWith(403);
expect(res.json).toHaveBeenCalledWith(
expect.objectContaining({ error: expect.stringContaining('DC-100') })
);
// Log tag is [CSRF-debug]
expect(stderrSpy).toHaveBeenCalled();
const lastWrite = stderrSpy.mock.calls[stderrSpy.mock.calls.length - 1][0];
expect(lastWrite).toContain('[CSRF-debug]');
expect(lastWrite).toContain('browser auto-retry');
expect(lastWrite).not.toMatch(/^\[CSRF\][^-]/); // not bare [CSRF]
});
it('tags missing-cookie with [CSRF] when no X-CSRF-Token header present (real probe)', () => {
const { req, res, next } = createMockReqRes({
method: 'POST', path: '/api/v1/backups/schedule',
headers: { cookie: '' }
});
csrfValidationMiddleware(req, res, next);
expect(res.status).toHaveBeenCalledWith(403);
expect(stderrSpy).toHaveBeenCalled();
const lastWrite = stderrSpy.mock.calls[stderrSpy.mock.calls.length - 1][0];
expect(lastWrite).toContain('[CSRF]');
expect(lastWrite).not.toContain('[CSRF-debug]');
expect(lastWrite).not.toContain('browser auto-retry');
});
it('keeps [CSRF] tag when cookie present but header missing (curl probe with manual cookie)', () => {
const nonce = generateToken();
const { req, res, next } = createMockReqRes({
method: 'POST', path: '/api/v1/backups/schedule',
headers: { cookie: `${CSRF_COOKIE_NAME}=${nonce}` }
});
csrfValidationMiddleware(req, res, next);
expect(res.status).toHaveBeenCalledWith(403);
expect(stderrSpy).toHaveBeenCalled();
const lastWrite = stderrSpy.mock.calls[stderrSpy.mock.calls.length - 1][0];
expect(lastWrite).toContain('[CSRF]');
expect(lastWrite).not.toContain('[CSRF-debug]');
});
it('headerToken is read from x-csrf-token (lowercased by Express) — lowercase header triggers [CSRF-debug]', () => {
// Express/Node lowercases all incoming header keys, so production code
// only ever sees lowercase. We test the exact code path here.
const { req, res, next } = createMockReqRes({
method: 'POST', path: '/api/v1/backups/schedule',
headers: { cookie: '', 'x-csrf-token': 'some-signature-attempt' }
});
csrfValidationMiddleware(req, res, next);
expect(res.status).toHaveBeenCalledWith(403);
const lastWrite = stderrSpy.mock.calls[stderrSpy.mock.calls.length - 1][0];
expect(lastWrite).toContain('[CSRF-debug]');
});
});
});
describe('renewCSRFToken', () => {
@@ -0,0 +1,218 @@
/**
* DC-057: dead-shadow /backups/schedule handler removed.
*
* The duplicate `router.post('/backups/schedule', ...)` previously registered
* far below the canonical one was unreachable (Express matches the first
* registered handler per METHOD+PATH). It bypassed `premiumGating` and
* `validateBody` and used a `name`-keyed schema that would have corrupted the
* backup config if it ever ran. The canonical handler uses the error code
* `backups-schedule-update`; the dead handler used `backups-schedule-legacy`.
* This test proves:
*
* 1. The router registers exactly ONE POST /backups/schedule handler
* (the canonical, appId-keyed one).
* 2. No handler references the legacy "backups-schedule-legacy" error code.
* 3. The legacy "name"-keyed schema now produces a 400 ValidationError
* from the canonical Joi schema (dead handler is gone).
* 4. The canonical appId-keyed schema still succeeds (200).
* 5. premiumGating is enforced on the canonical POST.
*
* Mirrors the audit-log.routes.test.js pattern.
*/
const express = require('express');
function buildFakeBackupManager() {
const config = { backups: {}, defaultRetention: { keep: 7 } };
return {
getConfig: jest.fn(() => config),
updateConfig: jest.fn((next) => {
config.backups = next.backups || {};
}),
getHistory: jest.fn(() => []),
restoreBackup: jest.fn(async (id) => {
// Suppress require-await — keep async shape for parity with the
// real backupManager.restoreBackup contract.
return Promise.resolve({ id, status: 'restored' });
}),
};
}
function buildFakeLicenseManager() {
const requirePremium = jest.fn(() => (_req, _res, next) => next());
return {
requirePremium,
isPremium: jest.fn(() => true),
};
}
function buildRouter(licenseManager, backupManager) {
// Reset module cache so each test starts fresh
jest.resetModules();
const mod = require('../../routes/backups');
return mod({
backupManager,
licenseManager,
asyncHandler: (fn) => async (req, res, next) => { // eslint-disable-line require-await
try { await fn(req, res, next); } catch (e) { next(e); }
},
});
}
function buildApp(router) {
// Catch-all error handler so ValidationError / NotFoundError become JSON
const app = express();
app.use(express.json());
app.use((req, res, next) => {
// intentionally strip auth — the test does not exercise it
next();
});
app.use('/', router);
// eslint-disable-next-line no-unused-vars
app.use((err, req, res, next) => {
const status = err.statusCode || err.status || 500;
res.status(status).json({
error: err.message,
code: err.code || 'ERR',
});
});
return app;
}
function supertestFetch(app) {
// Tiny in-process fetch helper (no need to add supertest dep)
const http = require('http');
return function (method, path, body) {
return new Promise((resolve, reject) => {
const server = app.listen(0, () => {
const { port } = server.address();
const data = body ? JSON.stringify(body) : null;
const req = http.request({
method,
hostname: '127.0.0.1',
port,
path,
headers: data ? { 'Content-Type': 'application/json', 'Content-Length': Buffer.byteLength(data) } : {},
}, (res) => {
let chunks = '';
res.on('data', (c) => { chunks += c; });
res.on('end', () => {
server.close();
let parsed;
try { parsed = JSON.parse(chunks); } catch { parsed = chunks; }
resolve({ status: res.statusCode, body: parsed });
});
});
req.on('error', (e) => { server.close(); reject(e); });
if (data) req.write(data);
req.end();
});
});
};
}
describe('routes/backups POST /backups/schedule (DC-057)', () => {
let backupManager, licenseManager, app, fetch;
beforeEach(() => {
backupManager = buildFakeBackupManager();
licenseManager = buildFakeLicenseManager();
const router = buildRouter(licenseManager, backupManager);
app = buildApp(router);
fetch = supertestFetch(app);
});
test('registers exactly ONE POST /backups/schedule handler (canonical)', () => {
// Inspect the registered router layers and confirm only one POST /backups/schedule
// route exists (no shadowed / unreachable duplicate).
const router = buildRouter(licenseManager, backupManager);
const seen = [];
router.stack.forEach((layer) => {
if (layer.route && layer.route.path === '/backups/schedule' && layer.route.methods.post) {
seen.push(layer.route);
}
});
expect(seen).toHaveLength(1);
});
test('no handler references the legacy "backups-schedule-legacy" error code', () => {
// The canonical handler uses error code 'backups-schedule-update'.
// Walk the router stack and assert no route uses the legacy error code.
const router = buildRouter(licenseManager, backupManager);
const handlerStrings = [];
function walk(node) {
if (!node) return;
if (node.stack) node.stack.forEach(walk);
if (node.handle) {
const code = node.handle.toString();
handlerStrings.push(code);
}
}
walk(router);
const all = handlerStrings.join('\n');
expect(all).not.toContain('backups-schedule-legacy');
});
test('legacy name-keyed schema is REJECTED with 400 (dead route truly gone)', async () => {
// The dead handler accepted { name, schedule, maxStorageBytes, ...backupConfig }.
// After removal, the canonical Joi schema (backupScheduleCreate) rejects this
// shape because it requires `appId`. So we expect a 400.
const res = await fetch('POST', '/backups/schedule', {
name: 'mybackup',
schedule: 'daily',
maxStorageBytes: 1024,
});
expect(res.status).toBe(400);
expect(res.body.error).toMatch(/appId.*required|appId is required/i);
});
test('canonical appId-keyed schema SUCCEEDS (200) and writes backup config', async () => {
const res = await fetch('POST', '/backups/schedule', {
appId: 'plex',
schedule: 'daily',
retention: { keep: 7 },
destination: 'local',
destinationPath: '/var/backups/plex',
maxStorageBytes: 1024,
});
expect(res.status).toBe(200);
expect(res.body.success).toBe(true);
expect(backupManager.updateConfig).toHaveBeenCalledTimes(1);
const written = backupManager.updateConfig.mock.calls[0][0];
expect(written.backups).toHaveProperty('plex');
expect(written.backups.plex.schedule).toBe('daily');
expect(written.backups.plex.enabled).toBe(true);
expect(written.backups.plex.maxStorageBytes).toBe(1024);
});
test('premium gating is enforced on POST /backups/schedule', async () => {
// Replace the premium gate with one that 403s, then verify it runs.
licenseManager.requirePremium.mockReturnValueOnce(
(_req, res) => res.status(403).json({ error: 'premium required' }),
);
const router = buildRouter(licenseManager, backupManager);
app = buildApp(router);
fetch = supertestFetch(app);
const res = await fetch('POST', '/backups/schedule', {
appId: 'plex',
schedule: 'daily',
});
expect(res.status).toBe(403);
expect(backupManager.updateConfig).not.toHaveBeenCalled();
});
test('GET /backups/schedule still works (no collateral damage)', async () => {
const res = await fetch('GET', '/backups/schedule');
expect(res.status).toBe(200);
expect(res.body.success).toBe(true);
expect(res.body).toHaveProperty('schedules');
});
test('DELETE /backups/schedule/:appId still works', async () => {
// Seed the config so the delete has something to remove
backupManager.getConfig().backups.plex = { schedule: 'daily' };
const res = await fetch('DELETE', '/backups/schedule/plex');
expect(res.status).toBe(200);
expect(backupManager.updateConfig).toHaveBeenCalled();
});
});
@@ -0,0 +1,277 @@
/**
* DC-059: disk-space POST /config threshold-ordering invariant.
*
* DiskSpaceMonitor._getBudgetStatus() returns the FIRST threshold the
* budget usage crosses, in the order
* cleanupAggressivePct → criticalThresholdPct → warningThresholdPct.
* If a caller writes the three thresholds out of order
* (e.g. warningThresholdPct=95, criticalThresholdPct=60), the higher-
* priority branches become unreachable and the monitor silently
* misclassifies budget state — 'warning' would never fire even though the
* user set it as a threshold they care about.
*
* The fix lives in `routes/disk-space.js`: a `mergeAndCheckOrdering()`
* helper validates the *effective* (merged with live baseline) config
* against the invariant `warningThresholdPct < criticalThresholdPct <
* cleanupAggressivePct` BEFORE the route mutates diskSpaceMonitor.diskConfig.
*
* Tests cover:
* 1. Monotonic ascending order is accepted (happy path).
* 2. warningThresholdPct >= criticalThresholdPct is rejected with 400.
* 3. criticalThresholdPct >= cleanupAggressivePct is rejected with 400.
* 4. Partial updates work one field at a time without violating the
* invariant against the current baseline.
* 5. Out-of-bounds numeric values are clamped to the same bounds the
* original inline Math.min/Math.max chains enforced (50/60/70 → 99).
* 6. DiskSpaceMonitor.configure is NEVER called when the request is
* rejected (no partial mutation).
* 7. The merged config returned to the client is the post-clamp value,
* not the raw request body.
*/
const express = require('express');
const http = require('http');
const DEFAULT_CONFIG = {
enabled: true,
diskBudgetGB: 10,
warningThresholdPct: 80,
criticalThresholdPct: 90,
autoCleanup: true,
cleanupAggressivePct: 95,
};
function buildFakeDiskSpaceMonitor(initial = { ...DEFAULT_CONFIG }) {
const state = { ...initial };
return {
configure: jest.fn((updates) => {
Object.assign(state, updates);
return { ...state };
}),
getConfig: jest.fn(() => ({ ...state })),
getSnapshot: jest.fn(async () => ({})),
getDetailedBreakdown: jest.fn(async () => ({})),
performCleanup: jest.fn(async () => ({})),
// Test-only: peek at the internal state to confirm no mutation on rejection
_state: state,
};
}
function buildRouter(monitor) {
// Reset module cache so each test starts fresh
jest.resetModules();
const mod = require('../../routes/disk-space');
return mod({
diskSpaceMonitor: monitor,
asyncHandler: (fn) => async (req, res, next) => { // eslint-disable-line require-await
try { await fn(req, res, next); } catch (e) { next(e); }
},
log: { info: jest.fn(), warn: jest.fn(), error: jest.fn() },
});
}
function buildApp(router) {
const app = express();
app.use(express.json());
app.use((req, _res, next) => { next(); }); // strip auth
app.use('/', router);
// eslint-disable-next-line no-unused-vars
app.use((err, req, res, next) => {
const status = err.statusCode || err.status || 500;
res.status(status).json({
error: err.message,
code: err.code || 'ERR',
field: err.field || null,
});
});
return app;
}
function supertestFetch(app) {
return function (method, path, body) {
return new Promise((resolve, reject) => {
const server = app.listen(0, () => {
const { port } = server.address();
const data = body ? JSON.stringify(body) : null;
const req = http.request({
method,
hostname: '127.0.0.1',
port,
path,
headers: data ? { 'Content-Type': 'application/json', 'Content-Length': Buffer.byteLength(data) } : {},
}, (res) => {
let chunks = '';
res.on('data', (c) => { chunks += c; });
res.on('end', () => {
server.close();
let parsed;
try { parsed = JSON.parse(chunks); } catch { parsed = chunks; }
resolve({ status: res.statusCode, body: parsed });
});
});
req.on('error', (e) => { server.close(); reject(e); });
if (data) req.write(data);
req.end();
});
});
};
}
describe('routes/disk-space POST /config (DC-059 threshold ordering)', () => {
let monitor, app, fetch;
beforeEach(() => {
monitor = buildFakeDiskSpaceMonitor();
const router = buildRouter(monitor);
app = buildApp(router);
fetch = supertestFetch(app);
});
test('happy path — strict monotonic ascending order is accepted', async () => {
const res = await fetch('POST', '/config', {
warningThresholdPct: 75,
criticalThresholdPct: 88,
cleanupAggressivePct: 95,
});
expect(res.status).toBe(200);
expect(res.body.config).toEqual(expect.objectContaining({
warningThresholdPct: 75,
criticalThresholdPct: 88,
cleanupAggressivePct: 95,
}));
expect(monitor.configure).toHaveBeenCalledTimes(1);
});
test('warningThresholdPct >= criticalThresholdPct is rejected with 400', async () => {
const res = await fetch('POST', '/config', {
warningThresholdPct: 95,
criticalThresholdPct: 80,
cleanupAggressivePct: 99,
});
expect(res.status).toBe(400);
expect(res.body.error).toMatch(/warningThresholdPct.*strictly less than.*criticalThresholdPct/);
expect(res.body.field).toBe('warningThresholdPct');
// Critical invariant: monitor.configure was NEVER called.
expect(monitor.configure).not.toHaveBeenCalled();
});
test('criticalThresholdPct >= cleanupAggressivePct is rejected with 400', async () => {
const res = await fetch('POST', '/config', {
warningThresholdPct: 60,
criticalThresholdPct: 95,
cleanupAggressivePct: 80,
});
expect(res.status).toBe(400);
expect(res.body.error).toMatch(/criticalThresholdPct.*strictly less than.*cleanupAggressivePct/);
expect(res.body.field).toBe('criticalThresholdPct');
expect(monitor.configure).not.toHaveBeenCalled();
});
test('equal thresholds are rejected (strict <, not <=)', async () => {
const res = await fetch('POST', '/config', {
warningThresholdPct: 80,
criticalThresholdPct: 80,
cleanupAggressivePct: 90,
});
expect(res.status).toBe(400);
expect(monitor.configure).not.toHaveBeenCalled();
});
test('partial update — single field accepted against existing baseline', async () => {
// Defaults: warning=80, critical=90, aggressive=95. Raise warning to 85.
const res = await fetch('POST', '/config', { warningThresholdPct: 85 });
expect(res.status).toBe(200);
expect(res.body.config.warningThresholdPct).toBe(85);
expect(res.body.config.criticalThresholdPct).toBe(90);
expect(res.body.config.cleanupAggressivePct).toBe(95);
});
test('partial update — would violate invariant against baseline, rejected', async () => {
// Defaults: warning=80, critical=90, aggressive=95. Setting warning=95
// would collide with the existing critical=90 (warning >= critical).
const res = await fetch('POST', '/config', { warningThresholdPct: 95 });
expect(res.status).toBe(400);
expect(res.body.error).toMatch(/warningThresholdPct.*strictly less than.*criticalThresholdPct/);
expect(monitor.configure).not.toHaveBeenCalled();
});
test('partial update — succeeds after baseline was updated in a prior request', async () => {
// First request: bump warning from 80 → 85 (within current critical=90).
let res = await fetch('POST', '/config', { warningThresholdPct: 85 });
expect(res.status).toBe(200);
// Second request: now bump warning from 85 → 89. Still under critical=90.
res = await fetch('POST', '/config', { warningThresholdPct: 89 });
expect(res.status).toBe(200);
expect(monitor.configure).toHaveBeenCalledTimes(2);
});
test('partial update — would violate against the NEW baseline, rejected', async () => {
// Step 1: raise warning to 85.
let res = await fetch('POST', '/config', { warningThresholdPct: 85 });
expect(res.status).toBe(200);
// Step 2: try to raise warning to 95 — would collide with critical=90.
res = await fetch('POST', '/config', { warningThresholdPct: 95 });
expect(res.status).toBe(400);
// monitor.configure should have run exactly once (the accepted request).
expect(monitor.configure).toHaveBeenCalledTimes(1);
});
test('out-of-bounds values are clamped to documented ranges', async () => {
// Note: the three values must produce a valid monotonic ordering AFTER
// clamping. Setting warning=20 (→ 50), critical=200 (→ 99), aggressive=70
// would produce critical=99 > aggressive=70 which is rejected by the
// ordering check. Use values that clamp into a valid range.
const res = await fetch('POST', '/config', {
warningThresholdPct: 20, // below warning min 50 → clamped to 50
criticalThresholdPct: 85, // valid
cleanupAggressivePct: 200, // above aggressive max 99 → clamped to 99
});
expect(res.status).toBe(200);
expect(res.body.config).toEqual(expect.objectContaining({
warningThresholdPct: 50,
criticalThresholdPct: 85,
cleanupAggressivePct: 99,
}));
});
test('non-numeric threshold values are silently dropped (legacy behaviour preserved)', async () => {
// Strings are not numbers → unchanged from baseline. Confirms the
// ordering check doesn\'t reject legitimate "I didn\'t change this" requests.
const res = await fetch('POST', '/config', {
warningThresholdPct: '80',
});
expect(res.status).toBe(200);
expect(res.body.config.warningThresholdPct).toBe(80); // baseline unchanged
expect(monitor.configure).toHaveBeenCalledWith({}); // empty updates
});
test('diskBudgetGB and autoCleanup updates still work alongside threshold validation', async () => {
const res = await fetch('POST', '/config', {
diskBudgetGB: 50,
autoCleanup: false,
warningThresholdPct: 81,
});
expect(res.status).toBe(200);
expect(res.body.config.diskBudgetGB).toBe(50);
expect(res.body.config.autoCleanup).toBe(false);
expect(res.body.config.warningThresholdPct).toBe(81);
});
test('rejected request does NOT mutate the live diskConfig', async () => {
const before = { ...monitor._state };
const res = await fetch('POST', '/config', {
warningThresholdPct: 95, // collides with critical=90
});
expect(res.status).toBe(400);
expect(monitor._state).toEqual(before);
});
test('POST /config with no thresholds in body is a no-op against baseline', async () => {
const res = await fetch('POST', '/config', { diskBudgetGB: 25 });
expect(res.status).toBe(200);
expect(res.body.config.diskBudgetGB).toBe(25);
expect(res.body.config.warningThresholdPct).toBe(80); // unchanged
expect(res.body.config.criticalThresholdPct).toBe(90); // unchanged
expect(res.body.config.cleanupAggressivePct).toBe(95); // unchanged
});
});
+7 -32
View File
@@ -22,6 +22,13 @@ module.exports = function({ backupManager, licenseManager, asyncHandler }) {
const router = express.Router();
// ==================== SCHEDULE ENDPOINTS (PREMIUM) ====================
// NOTE: POST /backups/schedule has a single canonical registration below
// (the appId-keyed handler at the top of this section). Earlier versions
// registered a duplicate "name"-keyed handler later in the file — Express
// only matches the first registered handler per METHOD+PATH, so the
// duplicate was unreachable dead code. Do not re-add it; if you need a
// different schema, change the canonical Joi schema in
// src/utilities/validate.js (backupScheduleCreate) instead.
// Apply premium gating to schedule-related routes
const premiumGating = licenseManager.requirePremium('auto-backup');
@@ -511,38 +518,6 @@ module.exports = function({ backupManager, licenseManager, asyncHandler }) {
success(res, storageInfo);
}, 'backups-storage-info'));
// Schedule a backup
// LEGACY: this is a duplicate registration of POST /backups/schedule (see also line 60,
// which uses the appId-keyed schema and is the route the frontend actually calls).
// Express only matches the first registered handler per METHOD+PATH, so this handler
// is unreachable. It is preserved for now to avoid removing a route any unknown
// integration might still POST to. TODO: audit + remove in a dedicated cleanup PR.
router.post('/backups/schedule', asyncHandler(async (req, res) => {
const { name, schedule, maxStorageBytes, ...backupConfig } = req.body;
if (!name || !schedule) {
return res.status(400).json({ error: 'name and schedule are required' });
}
const config = backupManager.getConfig();
// Store maxStorageBytes in the backup config (converted to bytes)
const maxBytes = typeof maxStorageBytes === 'number' && maxStorageBytes > 0
? maxStorageBytes
: (typeof maxStorageBytes === 'string' ? parseStorageSize(maxStorageBytes) : 0);
config.backups[name] = {
...backupConfig,
enabled: true,
schedule,
maxStorageBytes: maxBytes,
destinations: backupConfig.destinations || [{ type: 'local' }]
};
backupManager.updateConfig(config);
success(res, { message: `Backup '${name}' scheduled`, maxStorageBytes: maxBytes });
}, 'backups-schedule-legacy'));
// Restore from backup
router.post('/backups/restore/:backupId', validateBody(schemas.backupRestore), asyncHandler(async (req, res) => {
const result = await backupManager.restoreBackup(req.params.backupId, req.body);
+81 -3
View File
@@ -1,5 +1,6 @@
const express = require('express');
const { success, error: errorResponse } = require('../src/utils/responses');
const { ValidationError } = require('../src/utilities/errors');
/**
* Disk space management routes
@@ -10,6 +11,76 @@ const { success, error: errorResponse } = require('../src/utils/responses');
* POST /disk/config — update disk budget settings
* POST /disk/cleanup — trigger manual cleanup (standard|aggressive|logs-only)
*/
// DC-059: monotonic-ordering invariant for the three threshold percentages.
// DiskSpaceMonitor._getBudgetStatus() walks them in order
// (cleanupAggressivePct → criticalThresholdPct → warningThresholdPct) and
// returns at the FIRST threshold the usage crosses. If a caller writes
// them out of order (e.g. warningThresholdPct=95, criticalThresholdPct=60),
// the higher-priority branches become unreachable and the monitor silently
// misclassifies budget state. Validate against the *effective* config
// (current value + incoming update for each field) so partial updates can
// be applied one field at a time without violating the invariant.
//
// Clamp values to the same ranges the previous inline Math.min/Math.max
// chains enforced (warning 50..99, critical 60..99, aggressive 70..99)
// so we don't loosen the original bounds while adding the new check.
const THRESHOLD_BOUNDS = Object.freeze({
warning: { min: 50, max: 99 },
critical: { min: 60, max: 99 },
aggressive: { min: 70, max: 99 },
});
function clampThreshold(name, value) {
const { min, max } = THRESHOLD_BOUNDS[name];
return Math.min(Math.max(value, min), max);
}
/**
* Apply a candidate update to a baseline config, then verify the three
* threshold percentages still satisfy
* warningThresholdPct < criticalThresholdPct < cleanupAggressivePct.
* The POST /config endpoint accepts partial updates (single field at a
* time), so we merge into the live diskSpaceMonitor config first, then test
* the merged value. Returns the merged candidate on success; throws
* ValidationError if the ordering invariant would be violated.
*
* @param {Object} baseline - current effective config from diskSpaceMonitor
* @param {Object} candidate - the partial update being applied this request
* @returns {Object} merged candidate with thresholds clamped to bounds
*/
function mergeAndCheckOrdering(baseline, candidate) {
const next = { ...baseline };
if (typeof candidate.warningThresholdPct === 'number') {
next.warningThresholdPct = clampThreshold('warning', candidate.warningThresholdPct);
}
if (typeof candidate.criticalThresholdPct === 'number') {
next.criticalThresholdPct = clampThreshold('critical', candidate.criticalThresholdPct);
}
if (typeof candidate.cleanupAggressivePct === 'number') {
next.cleanupAggressivePct = clampThreshold('aggressive', candidate.cleanupAggressivePct);
}
if (!(next.warningThresholdPct < next.criticalThresholdPct)) {
throw new ValidationError(
`warningThresholdPct (${next.warningThresholdPct}) must be strictly less than criticalThresholdPct (${next.criticalThresholdPct})`,
'warningThresholdPct'
);
}
if (!(next.criticalThresholdPct < next.cleanupAggressivePct)) {
throw new ValidationError(
`criticalThresholdPct (${next.criticalThresholdPct}) must be strictly less than cleanupAggressivePct (${next.cleanupAggressivePct})`,
'criticalThresholdPct'
);
}
// Return only the fields the caller asked to change (preserves partial-
// update semantics; diskSpaceMonitor.configure does its own merge).
const out = {};
if (typeof candidate.warningThresholdPct === 'number') out.warningThresholdPct = next.warningThresholdPct;
if (typeof candidate.criticalThresholdPct === 'number') out.criticalThresholdPct = next.criticalThresholdPct;
if (typeof candidate.cleanupAggressivePct === 'number') out.cleanupAggressivePct = next.cleanupAggressivePct;
return out;
}
module.exports = function({ diskSpaceMonitor, asyncHandler, log }) {
const router = express.Router();
@@ -36,9 +107,16 @@ module.exports = function({ diskSpaceMonitor, asyncHandler, log }) {
const updates = {};
if (typeof diskBudgetGB === 'number' && diskBudgetGB > 0) updates.diskBudgetGB = Math.min(diskBudgetGB, 1000);
if (typeof warningThresholdPct === 'number') updates.warningThresholdPct = Math.min(Math.max(warningThresholdPct, 50), 99);
if (typeof criticalThresholdPct === 'number') updates.criticalThresholdPct = Math.min(Math.max(criticalThresholdPct, 60), 99);
if (typeof cleanupAggressivePct === 'number') updates.cleanupAggressivePct = Math.min(Math.max(cleanupAggressivePct, 70), 99);
// DC-059: threshold percentages must satisfy a strict monotonic order
// (warning < critical < aggressive) so _getBudgetStatus() reaches the
// correct branch. mergeAndCheckOrdering() validates against the live
// baseline, so partial updates that violate the invariant are rejected
// BEFORE we mutate diskSpaceMonitor.diskConfig.
const thresholdUpdates = mergeAndCheckOrdering(
diskSpaceMonitor.getConfig(),
{ warningThresholdPct, criticalThresholdPct, cleanupAggressivePct }
);
Object.assign(updates, thresholdUpdates);
if (typeof autoCleanup === 'boolean') updates.autoCleanup = autoCleanup;
if (typeof enabled === 'boolean') updates.enabled = enabled;
+18 -2
View File
@@ -214,14 +214,30 @@ function csrfValidationMiddleware(req, res, next) {
return next();
}
// Validate both values exist
// DC-058: differentiate "browser auto-retry" from "real probe" using the
// X-CSRF-Token header as a signal. The dashboard JS in status/js/globals.js
// secureFetch() pre-fetches /api/v1/csrf-token (which sets the CSRF cookie
// via csrfCookieMiddleware) before posting; if the GET raced with container
// restart OR the user cleared cookies mid-session, the POST can arrive with
// a header but no cookie. secureFetch catches the 403 and auto-retries
// with a fresh token (lines 225-238 of globals.js). For these "has header
// but no cookie" misses, tag the log line [CSRF-debug] — operators can
// grep them out as expected noise. A request with NEITHER cookie NOR
// header (curl probe, exploit scanner, broken client) keeps the louder
// [CSRF] tag.
if (!cookieNonce) {
process.stderr.write(`[CSRF] Missing CSRF cookie: ${method} ${req.path} from ${req.ip}\n`);
const isLikelyBrowserAutoRetry = !!headerToken;
const tag = isLikelyBrowserAutoRetry ? '[CSRF-debug]' : '[CSRF]';
process.stderr.write(`${tag} Missing CSRF cookie: ${method} ${req.path} from ${req.ip}` +
(isLikelyBrowserAutoRetry ? ' (browser auto-retry — header present, expect self-heal)' : '') + '\n');
return errorResponse(res, 403, '[DC-100] CSRF token missing', {
message: 'CSRF cookie not found. Please refresh the page (Ctrl+Shift+R) and try again.'
});
}
// Cookie present but no header — a real browser POST always sends both, so
// header-less is suspicious (curl probe with manual cookie, misconfigured
// client). Keep WARN level.
if (!headerToken) {
process.stderr.write(`[CSRF] Missing CSRF header: ${method} ${req.path} from ${req.ip}\n`);
return errorResponse(res, 403, '[DC-100] CSRF token missing', {