Turn "accept-both-outcomes" documentation tests — which pass whether the app is secure or vulnerable — into assertions that pin the secure behavior, and replace fake-UUID authz tests that 404'd before ever reaching the ownership guard with real cross-user resources. file-upload-attacks: - SVG-with-<script> → pin 400 (infer returns None for text → stored-XSS defense); was [201,400], which accepted the vulnerable outcome. - zero-byte → pin 400; path-traversal → pin 201 with UUID-derived storage and a no-path-echo check (both were [201,400]). - Fix the application/octet-stream rationale (no "application bypass" exists — the handler ignores the declared type and keys off magic bytes). authorization-deep (IDOR): - B deleting A's comment: seed a real upload+comment as A, assert 403, assert the comment survives, and assert the owner (A) still gets 204 — proving the 403 is about identity, not a broken route. (Was a DELETE on the all-zeros UUID → 404 before the user_id guard, so authorization was never exercised.) - Add B-deletes-A's-upload (403, countUploads unchanged) and B-edits-A's-caption (403, caption intact) — the find_by_id_and_event + ownership guards. export: pin the ZIP-download 404 (was [404,200] — a 200 is a data-exposure regression) and split into the two real branches: not-yet-ready, and ready-but-file-missing (new db.setExportZipReady helper). All 21 assertions verified green against the live secure backend. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
175 lines
7.5 KiB
TypeScript
175 lines
7.5 KiB
TypeScript
/**
|
|
* Phase 2 adversarial — deeper authorization escalation paths.
|
|
*
|
|
* Complements the foundational 403/401 checks in 05-admin/authorization.spec.ts
|
|
* with cross-user and banned-user scenarios that span multiple resources.
|
|
*/
|
|
import { test, expect } from '../../fixtures/test';
|
|
import { uploadRaw, JPEG_MAGIC } from '../../helpers/upload-client';
|
|
|
|
const BASE = process.env.E2E_FRONTEND_URL ?? 'http://localhost:3101';
|
|
|
|
/** Seed a real upload owned by `jwt` and return its id. */
|
|
async function seedUpload(jwt: string, caption?: string): Promise<string> {
|
|
const body = new Uint8Array(1024);
|
|
body.set(JPEG_MAGIC, 0);
|
|
const res = await uploadRaw(jwt, body, { filename: 'a.jpg', contentType: 'image/jpeg', caption });
|
|
if (res.status !== 201) throw new Error(`seed upload failed: ${res.status} ${await res.text()}`);
|
|
return (await res.json()).id;
|
|
}
|
|
|
|
/** Seed a real comment on `uploadId` authored by `jwt`; return its id. */
|
|
async function seedComment(jwt: string, uploadId: string, body = 'mine'): Promise<string> {
|
|
const res = await fetch(`${BASE}/api/v1/upload/${uploadId}/comments`, {
|
|
method: 'POST',
|
|
headers: { Authorization: `Bearer ${jwt}`, 'Content-Type': 'application/json' },
|
|
body: JSON.stringify({ body }),
|
|
});
|
|
if (res.status !== 201) throw new Error(`seed comment failed: ${res.status} ${await res.text()}`);
|
|
return (await res.json()).id;
|
|
}
|
|
|
|
async function listComments(jwt: string, uploadId: string): Promise<any[]> {
|
|
const res = await fetch(`${BASE}/api/v1/upload/${uploadId}/comments`, {
|
|
headers: { Authorization: `Bearer ${jwt}` },
|
|
});
|
|
return res.json();
|
|
}
|
|
|
|
test.describe('Adversarial — deep authorization', () => {
|
|
// IDOR: user B must not be able to delete user A's REAL comment. This exercises the
|
|
// ownership guard (`comment.user_id != auth.user_id` → 403) — the previous version fired
|
|
// at the all-zeros UUID, which 404s at the lookup BEFORE that guard runs, so it never
|
|
// tested authorization at all.
|
|
test('user B cannot delete user A\'s comment (real resource → 403, comment survives)', async ({ guest }) => {
|
|
const a = await guest('CommentOwnerA');
|
|
const b = await guest('AttackerB');
|
|
|
|
const uploadId = await seedUpload(a.jwt);
|
|
const commentId = await seedComment(a.jwt, uploadId, 'A owns this');
|
|
|
|
const res = await fetch(`${BASE}/api/v1/comment/${commentId}`, {
|
|
method: 'DELETE',
|
|
headers: { Authorization: `Bearer ${b.jwt}` },
|
|
});
|
|
// Must be 403 specifically — the comment exists and is in B's event, so a 404 would
|
|
// mean the ownership check was skipped/reordered.
|
|
expect(res.status).toBe(403);
|
|
|
|
// No state change: the comment is still there.
|
|
const after = await listComments(a.jwt, uploadId);
|
|
expect(after.some((c: any) => c.id === commentId)).toBe(true);
|
|
|
|
// Control: the real owner CAN delete it (proves the 403 was about identity, not a broken route).
|
|
const ownerDel = await fetch(`${BASE}/api/v1/comment/${commentId}`, {
|
|
method: 'DELETE',
|
|
headers: { Authorization: `Bearer ${a.jwt}` },
|
|
});
|
|
expect(ownerDel.status).toBe(204);
|
|
});
|
|
|
|
// IDOR: user B must not be able to delete user A's REAL upload.
|
|
test('user B cannot delete user A\'s upload (403, upload survives)', async ({ guest, db }) => {
|
|
const a = await guest('UploadOwnerA');
|
|
const b = await guest('AttackerB2');
|
|
|
|
const uploadId = await seedUpload(a.jwt);
|
|
expect(await db.countUploadsForUser(a.userId)).toBe(1);
|
|
|
|
const res = await fetch(`${BASE}/api/v1/upload/${uploadId}`, {
|
|
method: 'DELETE',
|
|
headers: { Authorization: `Bearer ${b.jwt}` },
|
|
});
|
|
expect(res.status).toBe(403);
|
|
|
|
// No state change: A's upload is still present (not soft-deleted).
|
|
expect(await db.countUploadsForUser(a.userId)).toBe(1);
|
|
});
|
|
|
|
// IDOR: user B must not be able to edit (re-caption / re-tag) user A's upload.
|
|
test('user B cannot edit user A\'s upload caption (403, caption unchanged)', async ({ guest, db }) => {
|
|
const a = await guest('UploadOwnerA2');
|
|
const b = await guest('AttackerB3');
|
|
|
|
const uploadId = await seedUpload(a.jwt, 'original caption');
|
|
// Make it visible in the feed so we can read the caption back.
|
|
await db.setUploadCompressionStatus(uploadId, 'done');
|
|
|
|
const res = await fetch(`${BASE}/api/v1/upload/${uploadId}`, {
|
|
method: 'PATCH',
|
|
headers: { Authorization: `Bearer ${b.jwt}`, 'Content-Type': 'application/json' },
|
|
body: JSON.stringify({ caption: 'hacked by B' }),
|
|
});
|
|
expect(res.status).toBe(403);
|
|
|
|
// No state change: the caption A set is intact.
|
|
const feedRes = await fetch(`${BASE}/api/v1/feed`, { headers: { Authorization: `Bearer ${a.jwt}` } });
|
|
const feed: any = await feedRes.json();
|
|
const list: any[] = feed.uploads ?? feed.items ?? feed;
|
|
const row = list.find((u: any) => u.id === uploadId);
|
|
expect(row?.caption).toBe('original caption');
|
|
});
|
|
|
|
test('banned user cannot toggle a like', async ({ api, host, guest }) => {
|
|
const target = await guest('BannedLike');
|
|
await api.banUser(host.jwt, target.userId, false);
|
|
|
|
const res = await fetch(`${BASE}/api/v1/upload/00000000-0000-0000-0000-000000000000/like`, {
|
|
method: 'POST',
|
|
headers: { Authorization: `Bearer ${target.jwt}` },
|
|
});
|
|
expect([403, 404]).toContain(res.status);
|
|
});
|
|
|
|
test('banned user cannot post a comment', async ({ api, host, guest }) => {
|
|
const target = await guest('BannedComment');
|
|
await api.banUser(host.jwt, target.userId, false);
|
|
|
|
const res = await fetch(`${BASE}/api/v1/upload/00000000-0000-0000-0000-000000000000/comments`, {
|
|
method: 'POST',
|
|
headers: { Authorization: `Bearer ${target.jwt}`, 'Content-Type': 'application/json' },
|
|
body: JSON.stringify({ body: 'should be rejected' }),
|
|
});
|
|
expect([403, 404]).toContain(res.status);
|
|
});
|
|
|
|
test('banned user can still read the feed (read-only access preserved)', async ({ api, host, guest }) => {
|
|
const target = await guest('BannedRead');
|
|
await api.banUser(host.jwt, target.userId, false);
|
|
|
|
const res = await fetch(`${BASE}/api/v1/feed`, {
|
|
headers: { Authorization: `Bearer ${target.jwt}` },
|
|
});
|
|
// The journey docs explicitly state banned users keep read access.
|
|
expect(res.status).toBe(200);
|
|
});
|
|
|
|
test('host cannot delete another host\'s session via /api/v1/session', async ({ api, host, guest }) => {
|
|
const otherHost = await guest('OtherHost');
|
|
// Promote so they have a host JWT to play with.
|
|
await api.setRole(host.jwt, otherHost.userId, 'host');
|
|
|
|
// The /session DELETE endpoint deletes the caller's own session by token hash.
|
|
// A host cannot pass another host's token here (no way to authenticate as them),
|
|
// so this is structurally safe — we assert by trying to delete with the wrong
|
|
// Authorization header and checking that only the caller's session is gone.
|
|
await api.logout(host.jwt);
|
|
const stillWorks = await fetch(`${BASE}/api/v1/me/context`, {
|
|
headers: { Authorization: `Bearer ${otherHost.jwt}` },
|
|
});
|
|
expect(stillWorks.status).toBe(200);
|
|
});
|
|
|
|
test('promote endpoint cannot be used to make oneself admin', async ({ host }) => {
|
|
const res = await fetch(`${BASE}/api/v1/host/users/${'00000000-0000-0000-0000-000000000000'}/role`, {
|
|
method: 'PATCH',
|
|
headers: { Authorization: `Bearer ${host.jwt}`, 'Content-Type': 'application/json' },
|
|
body: JSON.stringify({ role: 'admin' }),
|
|
});
|
|
// 400 (invalid role for host-callable endpoint) or 403/404.
|
|
expect([400, 403, 404]).toContain(res.status);
|
|
// Critically, NOT 200/204.
|
|
expect([200, 204]).not.toContain(res.status);
|
|
});
|
|
});
|