🛡️ Sentinel: [HIGH] Fix timing attack vulnerability in token validation

.jules/sentinel.md

@@ -0,0 +1,4 @@
+## 2026-07-22 - Fix Timing Attack Vulnerability in Token Comparison
+**Vulnerability:** Checking buffer lengths before calling `crypto.timingSafeEqual` creates a short-circuit fast path that leaks the secret's length via timing differences.
+**Learning:** `crypto.timingSafeEqual` throws an error if buffers have different lengths, so checking lengths first seems necessary, but it introduces a timing attack vulnerability.
+**Prevention:** Always hash both secrets to a fixed length (e.g., using `crypto.createHash('sha256')`) before comparison to ensure true constant-time evaluation.

src/cli/commands/serve.ts

@@ -346,13 +346,10 @@ export async function handleServeCommand(_options: unknown, command: Command) {
 
           let isAuthenticated = false;
           if (scheme?.toLowerCase() === 'bearer' && token) {
-            const tokenBuffer = Buffer.from(token);
+            const tokenHash = crypto.createHash('sha256').update(token).digest();
             for (const authToken of authTokens) {
-              const authTokenBuffer = Buffer.from(authToken);
-              if (
-                tokenBuffer.length === authTokenBuffer.length &&
-                crypto.timingSafeEqual(tokenBuffer, authTokenBuffer)
-              ) {
+              const expectedHash = crypto.createHash('sha256').update(authToken).digest();
+              if (crypto.timingSafeEqual(tokenHash, expectedHash)) {
                 isAuthenticated = true;
                 break;
               }