Adds an end-to-end Playwright test suite under e2e/ that spins up an
isolated docker-compose stack (Postgres :55432, Caddy :3101, backend with
EVENTSNAP_TEST_MODE=1, SvelteKit adapter-node frontend) and exercises the
SvelteKit app against the real Rust backend.
Phase 1 — happy paths covering every documented USER_JOURNEYS.md flow:
01-auth/ join, recover, admin login, leave event, PIN lockout
02-upload/ gallery picker (API path), rate-limit + admin toggle
03-feed/ like/comment SSE, filters, SSE reconnect on visibility
04-host/ event lock API, ban/unban, promote
05-admin/ config validation, foundational authz guards, stats
06-export/ /export status + download stub
__smoke/ cross-UA happy-path (runs on every UA project)
Phase 2 — adversarial + browser chaos:
07-adversarial/ XSS payloads (6 × display name path), SQLi shapes,
length / encoding / RTL override / NUL byte;
file-upload boundaries (ELF body claimed as JPEG,
oversize vs max_image_size_mb, zero-byte, NUL
filename, path-traversal, SVG-with-script);
JWT alg:none, signature/payload tamper, expired
session, PIN brute-force (serial + parallel),
admin password brute-force; deep authz (cross-user
delete, banned user across like/comment/feed-read,
host→admin escalation); small-scale DDoS (20× /join,
10MB comment body, 10 concurrent SSE).
08-browser-chaos/ localStorage / sessionStorage / cookie purge,
IndexedDB drop mid-session, offline → reconnect,
slow-3G, 503 flakes, 429 with no retry storm,
multi-tab same/different user, no-JS, hostile CSS,
clock skew ±1h / -2d, localStorage quota exhausted.
Phase 3 — mobile gestures (runs only on chromium-mobile / Pixel 7):
09-mobile/ touch-target ≥44px audit, env(safe-area-inset-bottom)
structural check, long-press (FeedListCard → ContextSheet,
quick-tap negation, click-suppression), double-tap
(feed card like + lightbox heart-burst, via synthetic
pointer events to bypass the first-tap-fires-click trap),
viewport reflow (portrait/landscape/narrow/phablet),
plus fixme stubs documenting planned gestures (swipe
lightbox L/R, swipe-down dismiss, pull-to-refresh,
long-press-comment).
Cross-UA matrix (chromium-engine projects run @smoke only):
chromium-pixel7, chromium-galaxy-s22, samsung-internet (Samsung UA
emulation on Galaxy viewport), edge-android, plus webkit-iphone,
chrome-ios, firefox-android, firefox-desktop — the latter four need
libavif16 on the host (Playwright dep) but the configs are in place.
Infrastructure:
- fixtures/test.ts central test.extend (api, db, adminToken, guest,
host, signIn). Per-test DB truncate via the dev-only POST
/admin/__truncate route, gated by EVENTSNAP_TEST_MODE=1.
- helpers/sse-listener.ts, helpers/upload-client.ts (Node-side
multipart for adversarial file-upload tests + JPEG/PNG/ELF magic
constants), helpers/touch.ts (longPress / doubleTap / swipe /
inlineStyle / computedStyle).
- 10 page objects covering every route + UploadSheet/Lightbox.
- global-setup waits for /health, logs in admin, disables every
rate-limit and quota toggle.
- .github/workflows/e2e.yml: PR check runs chromium-desktop + the
smoke matrix in parallel, uploads playwright-report/ and traces on
failure.
Findings the suite surfaces as live `[finding]` warnings (not silenced):
1. /admin/login has no rate-limit or lockout (bcrypt cost only).
2. PIN-attempt counter races under parallel /recover requests.
3. Zero-byte uploads pass /api/v1/upload.
4. SVG-with-script can pass the magic-byte check (consider CSP +
X-Content-Type-Options on /media/*).
Stack-internal docs live in e2e/README.md (UA tier table, Samsung
Internet escalation tiers A/B/C, debugging tips, roadmap).
Final tally: 134 passed / 0 failed / 9 skipped (test.fixme stubs for
not-yet-shipped gestures and one UI-upload-flow investigation).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
138 lines
6.4 KiB
TypeScript
138 lines
6.4 KiB
TypeScript
/**
|
||
* Phase 2 adversarial — file upload boundary tests. Exercises every input
|
||
* validation rule baked into [backend/src/handlers/upload.rs]:
|
||
*
|
||
* 1. Magic-byte detection rejects spoofed MIME categories
|
||
* (declared image/jpeg, actual application/octet-stream of e.g. an ELF binary).
|
||
* 2. Size limits read from the `config` table reject oversize files.
|
||
* 3. Filenames are not used as filesystem paths (path traversal ignored).
|
||
* 4. Zero-byte and missing-file cases fail safely.
|
||
* 5. `content_type: application/...` bypasses category check but still goes through size validation.
|
||
*/
|
||
import { test, expect } from '../../fixtures/test';
|
||
import { uploadRaw, ELF_MAGIC, JPEG_MAGIC } from '../../helpers/upload-client';
|
||
|
||
const BASE = process.env.E2E_FRONTEND_URL ?? 'http://localhost:3101';
|
||
|
||
test.describe('Adversarial — file upload', () => {
|
||
test('claimed image/jpeg with ELF body is rejected by magic-byte check', async ({ guest }) => {
|
||
const g = await guest('MimeSpoof');
|
||
const body = new Uint8Array(1024);
|
||
body.set(ELF_MAGIC, 0);
|
||
const res = await uploadRaw(g.jwt, body, { filename: 'evil.jpg', contentType: 'image/jpeg' });
|
||
expect(res.status).toBe(400);
|
||
const json: any = await res.json().catch(() => ({}));
|
||
expect((json.message ?? '').toLowerCase()).toMatch(/entspricht nicht|deklarierten/);
|
||
});
|
||
|
||
test('claimed image/jpeg with video bytes is rejected (cross-category)', async ({ guest }) => {
|
||
const g = await guest('CrossCat');
|
||
// Minimal MP4 ftyp header — infer detects as video/mp4.
|
||
const body = new Uint8Array(64);
|
||
const ftyp = new TextEncoder().encode('ftypisom');
|
||
body.set([0x00, 0x00, 0x00, 0x18], 0);
|
||
body.set(ftyp, 4);
|
||
const res = await uploadRaw(g.jwt, body, { filename: 'evil.jpg', contentType: 'image/jpeg' });
|
||
// Backend either rejects with 400 (cross-category) or accepts as video — both are documented behaviors.
|
||
expect([400, 201]).toContain(res.status);
|
||
});
|
||
|
||
test('oversize image (declared > max_image_size_mb) is rejected with 400', async ({ api, adminToken, guest }) => {
|
||
await api.patchConfig(adminToken, { max_image_size_mb: '1' }); // 1 MB cap for the test
|
||
try {
|
||
const g = await guest('Oversize');
|
||
const body = new Uint8Array(2 * 1024 * 1024); // 2 MB
|
||
body.set(JPEG_MAGIC, 0);
|
||
const res = await uploadRaw(g.jwt, body, { filename: 'big.jpg', contentType: 'image/jpeg' });
|
||
expect(res.status).toBe(400);
|
||
const json: any = await res.json().catch(() => ({}));
|
||
expect((json.message ?? '').toLowerCase()).toMatch(/zu groß|too large/i);
|
||
} finally {
|
||
await api.patchConfig(adminToken, { max_image_size_mb: '20' });
|
||
}
|
||
});
|
||
|
||
test('zero-byte file behavior (documented finding if accepted)', async ({ guest }) => {
|
||
const g = await guest('ZeroByte');
|
||
const res = await uploadRaw(g.jwt, new Uint8Array(0), { filename: 'empty.jpg', contentType: 'image/jpeg' });
|
||
// Current backend accepts zero-byte JPEGs (201) because the magic-byte check
|
||
// returns None for empty input and short-circuits validation. Documented as
|
||
// a finding — the compression worker should reject them downstream, but
|
||
// a 400 at the upload boundary would be cleaner.
|
||
expect([201, 400]).toContain(res.status);
|
||
if (res.status === 201) {
|
||
console.warn('[finding] zero-byte uploads pass /api/v1/upload — consider rejecting empty bodies upfront.');
|
||
}
|
||
});
|
||
|
||
test('multipart with no file field at all is rejected', async ({ guest }) => {
|
||
const g = await guest('NoFile');
|
||
const form = new FormData();
|
||
form.append('caption', 'no file here');
|
||
const res = await fetch(`${BASE}/api/v1/upload`, {
|
||
method: 'POST',
|
||
headers: { Authorization: `Bearer ${g.jwt}` },
|
||
body: form,
|
||
});
|
||
expect(res.status).toBe(400);
|
||
});
|
||
|
||
test('filename with path traversal is ignored (server uses upload_id for storage)', async ({ guest }) => {
|
||
const g = await guest('PathTrav');
|
||
const body = new Uint8Array(1024);
|
||
body.set(JPEG_MAGIC, 0);
|
||
const res = await uploadRaw(g.jwt, body, {
|
||
filename: '../../../../etc/passwd',
|
||
contentType: 'image/jpeg',
|
||
});
|
||
expect([201, 400]).toContain(res.status);
|
||
// Critical assertion: the server must not have created or read /etc/passwd. We can't directly
|
||
// probe the container, so we settle for the upload-response-doesn't-leak path check below.
|
||
if (res.status === 201) {
|
||
const json: any = await res.json();
|
||
expect(JSON.stringify(json)).not.toContain('/etc/');
|
||
expect(JSON.stringify(json)).not.toContain('..');
|
||
}
|
||
});
|
||
|
||
test('filename with embedded NUL byte does not crash the server', async ({ guest }) => {
|
||
const g = await guest('NulFile');
|
||
const body = new Uint8Array(1024);
|
||
body.set(JPEG_MAGIC, 0);
|
||
const res = await uploadRaw(g.jwt, body, {
|
||
filename: 'evil |