Nine Digits and You're In the Meeting

Medium

· Backend

Incident

SEV-1

BUG-ZOOM2020

Priority: Critical · reported by trust & safety

Time to fix: 20 min

Failing checks on the shipped build

  • a wrong passcode is denied

    a known id must not be enough: expected {"status":"denied","admitted":false} but got {"status":"ok","admitted":true}

  • repeated failures lock the meeting

    guessing must be throttled: expected {"status":"locked","admitted":false} but got {"status":"ok","admitted":true}

How to work this incident

  1. Read the report: write down the expected behaviour and the actual one in a sentence each.
  2. Reproduce it: run the visible tests and find the failing check that matches the report.
  3. Read the logs and the failing checks for the first value that is wrong — the earliest wrong value is nearer the cause than the loudest error.
  4. Follow the request through the handler, the validation and the service it calls; find the first step whose output disagrees with the report.
  5. Fix the cause rather than the symptom, run the visible tests again, and submit against the hidden ones — then write the root cause down.

Inspired by

Zoom · 2020

Modelled on Zoom's 2020 "Zoombombing" wave: meeting IDs were short numeric codes, passwords were off by default, and there was no rate limit on joining. Automated tools guessed live meeting IDs and dropped strangers into calls.

meetings.js admits anyone who supplies an existing meeting id.

Fix joinMeeting so a passcode is required and repeated failed attempts are throttled.

Code map

exports.joinMeeting = function (meetings, attempts, meetingId, passcode) {
  var meeting = meetings[meetingId];
  if (!meeting) return { status: "not-found", admitted: false };
  return { status: "ok", admitted: true };
};

Sign in to edit the file, run the tests and submit a fix

A free account — no card, no trial clock. You come straight back here.

Nine Digits and You're In the Meeting — JavaScript Bug Hunt

Modelled on Zoom's 2020 "Zoombombing" wave: meeting IDs were short numeric codes, passwords were off by default, and there was no rate limit on joining.

  • Language: JavaScript
  • Layer: Backend
  • Difficulty: Medium
  • Concepts: Security, Access Control
  • Modelled on: Zoom · 2020
  • Visible tests: the right passcode admits; a wrong passcode is denied; repeated failures lock the meeting
  • Reward: 50 XP for a complete fix

Incident

  • Severity: SEV-1 (priority: Critical)
  • Ticket: BUG-ZOOM2020
  • Reported by: trust & safety
  • Time to fix: 20 minutes, the target for a medium incident

Failing checks on the shipped build

  • a wrong passcode is denied — a known id must not be enough: expected {"status":"denied","admitted":false} but got {"status":"ok","admitted":true}
  • repeated failures lock the meeting — guessing must be throttled: expected {"status":"locked","admitted":false} but got {"status":"ok","admitted":true}

How to work this incident

  1. Read the report: write down the expected behaviour and the actual one in a sentence each.
  2. Reproduce it: run the visible tests and find the failing check that matches the report.
  3. Read the logs and the failing checks for the first value that is wrong — the earliest wrong value is nearer the cause than the loudest error.
  4. Follow the request through the handler, the validation and the service it calls; find the first step whose output disagrees with the report.
  5. Fix the cause rather than the symptom, run the visible tests again, and submit against the hidden ones — then write the root cause down.

Briefing

Modelled on Zoom's 2020 "Zoombombing" wave: meeting IDs were short numeric codes, passwords were off by default, and there was no rate limit on joining. Automated tools guessed live meeting IDs and dropped strangers into calls.

meetings.js admits anyone who supplies an existing meeting id.

Fix joinMeeting so a passcode is required and repeated failed attempts are throttled.

Bug report

BUG-ZOOM2020 · Priority: Critical · Reported by: trust & safety

joinMeeting(meetings, attempts, meetingId, passcode) must return { status, admitted }:

  • "not-found" when the meeting does not exist
  • "locked" when that client has already made 5 failed attempts
  • "denied" when the passcode does not match (and the failure is recorded)
  • "ok" with admitted true when it matches

attempts is a plain object mapping meetingId -> failed count.

Observed: any known meeting id admits the caller, and there is no attempt limit at all.

Logs

[meet] admitted anonymous joiner to 8471120394 (no passcode set)
[meet] 41,000 join attempts from one source in 6 minutes

The code as shipped

src/meet/meetings.js (editable)

exports.joinMeeting = function (meetings, attempts, meetingId, passcode) {
  var meeting = meetings[meetingId];
  if (!meeting) return { status: "not-found", admitted: false };
  return { status: "ok", admitted: true };
};

Read-only context: src/meet/POLICY.js.

Open the hunt to start the incident clock, edit the files, run the visible tests and submit against the hidden ones, then write the root cause down. More JavaScript bug hunts.