Files
securebit-chat/tests/verification-gate.test.mjs
T
lockbitchat 6152a77b51
CodeQL Analysis / Analyze CodeQL (push) Canceled after 0s
Deploy Application / deploy (push) Canceled after 0s
Mirror to Codeberg / mirror (push) Canceled after 0s
Mirror to PrivacyGuides / mirror (push) Canceled after 0s
security: fix SAS verification bypass and unauthenticated frame injection; release v5.5.2
A security review of the transport and verification layers. Every item is a fix
to how untrusted peer input is handled; no features changed.

- SAS verification could be bypassed. `verification_both_confirmed` is an
  unauthenticated frame on a channel that is not yet trusted, but it was taken as
  proof that both sides had compared their codes — so a peer who completed the
  signalling exchange could send it right after the data channel opened and drive
  the other side to a "verified" session while the user never looked at the code.
  It is now only an acknowledgement: refused unless this side already confirmed
  locally, and _setVerifiedStatus() independently rejects any SAS-based
  transition without a local confirmation. Holding ECDH-derived keys was never
  proof of identity — a MITM has those too.

- Unauthenticated frames could be injected into the chat. A bare
  {type:"message"} frame, a raw non-JSON frame and a binary frame were each
  decoded and rendered, bypassing decryption, the HMAC check and the verification
  gate; the injected text was indistinguishable from a genuine message. Chat
  content now reaches the UI only through the authenticated enhanced_message
  path.

- A peer could supply the verification code. `sas_code` announcements were
  adopted verbatim when no local SAS had been derived yet. They may now only
  corroborate the locally derived code.

- Anti-replay never ran. The sequence-number and AAD validators were defined on
  SecureKeyStorage instead of the connection manager, so every call site failed
  with a TypeError and the sliding replay window was dead code. Moved onto the
  manager, wired into the live chat path, and a missing or non-numeric sequence
  number now fails closed instead of sailing through the range checks.

- File transfers are gated on verification in both directions. Control frames are
  written straight to the data channel by the transfer system; sending was
  already gated, receiving now is too.

- Tighter CSP: connect-src and img-src no longer allow arbitrary https: hosts
  (nothing in the app talks to a third party), plus base-uri 'none'.

- The SAS is no longer written to logs, and is compared in constant time on every
  path. Fixed SecureMasterKeyManager.isUnlocked() testing a field renamed long
  ago, so it never actually gated anything.

- Fixed the header showing "Secure undefined%": getRealSecurityLevel() became
  reachable for the first time by the move above and returned only per-feature
  booleans, while the header renders `level` and `score` directly. It now runs
  the same verified scoring as every other consumer.

Adds regression tests for the verification gate, inbound frame authentication and
the security-level shape.
2026-07-27 00:10:29 -04:00

143 lines
5.6 KiB
JavaScript

// Regression tests for the MITM-protection gate.
//
// The whole security model rests on one step: the two users compare a Short
// Authentication String out-of-band. Everything below asserts that this step
// cannot be skipped, faked or supplied by the peer — an attacker who completes
// the signalling exchange (and therefore holds valid ECDH-derived keys) must
// still be unable to reach a verified session.
import assert from 'node:assert/strict';
globalThis.window = globalThis.window || {};
globalThis.window.EnhancedSecureCryptoUtils = {
constantTimeCompare: (a, b) => a === b
};
const { EnhancedSecureWebRTCManager } = await import('../src/network/EnhancedSecureWebRTCManager.js');
const P = EnhancedSecureWebRTCManager.prototype;
const settle = (ms = 2300) => new Promise((r) => setTimeout(r, ms));
function createPeerStub(overrides = {}) {
const stub = {
isVerified: false,
localVerificationConfirmed: false,
remoteVerificationConfirmed: false,
bothVerificationsConfirmed: false,
verificationCode: '1234567',
// Present right after ECDH — a MITM has these too, which is exactly why
// they must not be sufficient to become "verified".
encryptionKey: {},
macKey: {},
keyFingerprint: 'aa:bb:cc',
disconnected: false,
statusChanges: [],
uiMessages: [],
onStatusChange(s) { this.statusChanges.push(s); },
onVerificationStateChange() {},
_secureLog() {},
deliverMessageToUI(msg) { this.uiMessages.push(String(msg)); },
disconnect() { this.disconnected = true; },
dataChannel: { readyState: 'open', send() {} },
handleSystemMessage: P.handleSystemMessage,
handleVerificationBothConfirmed: P.handleVerificationBothConfirmed,
handleVerificationConfirmed: P.handleVerificationConfirmed,
handleSASCode: P.handleSASCode,
_validateSASCode: P._validateSASCode,
_checkBothVerificationsConfirmed: P._checkBothVerificationsConfirmed,
_setVerifiedStatus: P._setVerifiedStatus,
_enforceVerificationGate: P._enforceVerificationGate,
_notifyVerificationReadyIfPossible() {},
handleHeartbeat() {},
handlePeerDisconnectNotification() {},
handleVerificationRequest() {},
handleVerificationResponse() {},
processMessageQueue() {}
};
return Object.assign(stub, overrides);
}
// ── a peer cannot manufacture mutual confirmation ────────────────────────────
{
const victim = createPeerStub();
victim.handleSystemMessage({
type: 'verification_both_confirmed',
data: { timestamp: Date.now(), verificationMethod: 'SAS' }
});
await settle();
assert.equal(victim.isVerified, false, 'peer must not be able to force verified state');
assert.equal(victim.bothVerificationsConfirmed, false);
assert.equal(victim.disconnected, true, 'protocol violation must tear down the session');
assert.ok(
!victim.statusChanges.includes('verified'),
'no verified status may be emitted to the UI'
);
}
// ── the same frame IS honoured once the user has confirmed locally ───────────
{
const victim = createPeerStub({ localVerificationConfirmed: true });
victim.handleSystemMessage({
type: 'verification_both_confirmed',
data: { timestamp: Date.now(), verificationMethod: 'SAS' }
});
await settle();
assert.equal(victim.isVerified, true, 'legitimate mutual confirmation must still work');
assert.equal(victim.remoteVerificationConfirmed, true);
assert.equal(victim.disconnected, false);
assert.ok(victim.statusChanges.includes('verified'));
}
// ── _setVerifiedStatus refuses SAS transitions without local confirmation ────
{
const victim = createPeerStub();
assert.throws(
() => victim._setVerifiedStatus(true, 'MUTUAL_SAS_CONFIRMED', {}),
/without local SAS confirmation/,
'the low-level setter must fail closed too'
);
assert.equal(victim.isVerified, false);
}
// ── holding keys alone is never enough ───────────────────────────────────────
{
const victim = createPeerStub({ encryptionKey: null, macKey: null });
assert.throws(
() => victim._setVerifiedStatus(true, 'MUTUAL_SAS_CONFIRMED', {}),
/without encryption keys/
);
}
// ── a peer-announced SAS may corroborate, never supply ───────────────────────
{
// No locally derived code yet -> the announcement must be refused outright.
const victim = createPeerStub({ verificationCode: null });
victim.handleSystemMessage({ type: 'sas_code', data: { code: '7654321' } });
assert.equal(victim.verificationCode, null, 'peer-supplied SAS must not be adopted');
assert.equal(victim.disconnected, true);
}
{
// Locally derived code present and matching -> accepted, ours retained.
const victim = createPeerStub({ verificationCode: '1234567' });
victim.handleSystemMessage({ type: 'sas_code', data: { code: '1234567' } });
assert.equal(victim.verificationCode, '1234567');
assert.equal(victim.disconnected, false);
}
{
// Mismatch -> abort.
const victim = createPeerStub({ verificationCode: '1234567' });
victim.handleSystemMessage({ type: 'sas_code', data: { code: '7654321' } });
assert.equal(victim.disconnected, true, 'SAS mismatch must abort the session');
}
console.log('Verification gate tests passed');