The Invite Link That Shared a Hash — JavaScript Bug Hunt
Modelled on Slack, August 2022: Slack disclosed that when a user created or revoked a shareable invitation link for a workspace, a bug sent that user's…
- Language: JavaScript
- Layer: Backend
- Difficulty: Easy
- Concepts: Security, Privacy
- Modelled on: Slack · 2022
- Visible tests: creating a link stores and returns it; the creation event carries only the public profile
- Reward: 50 XP for a complete fix
Incident
- Severity: SEV-1 (priority: Critical)
- Ticket: BUG-INVITE-HASH
- Reported by: security
- Time to fix: 10 minutes, the target for an easy incident
Failing checks on the shipped build
- the creation event carries only the public profile — expected [{"channel":"T1","event":{"type":"invite_link_created","code":"abc","actor":{"id":"U1","name":"Kai","avatar":"k.png"}}}] but got [{"channel":"T1","event":{"type":"invite_link_created","code":"abc","actor":{"id":"U1","name":"Kai","email":"kai@example.com","passwordHash":"hash:9f2c","avatar"…
How to work this incident
- Read the report: write down the expected behaviour and the actual one in a sentence each.
- Reproduce it: run the visible tests and find the failing check that matches the report.
- 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.
- Follow the request through the handler, the validation and the service it calls; find the first step whose output disagrees with the report.
- 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 Slack, August 2022: Slack disclosed that when a user created or revoked a shareable invitation link for a workspace, a bug sent that user's hashed password to the clients of other members of the workspace. The hashes were salted and not visible in the app, but Slack reset the passwords of the affected users.
This reconstruction broadcasts an event to the workspace whenever a link is created or revoked — and puts the whole stored user record in it.
Fix invites.js so events only ever carry the public profile.
Bug report
BUG-INVITE-HASH · Priority: Critical · Reported by: security
createInviteLink(workspace, user, code, bus) and revokeInviteLink(workspace, user, code, bus) broadcast an event on the workspace's channel. The event's actor must be the PUBLIC profile only: { id, name, avatar } — exactly users.PUBLIC_FIELDS, in that order. No other field of the stored record (passwordHash, email, …) may appear in any event.
- create: stores { code, workspace: workspace.id, active: true } in workspace.links, broadcasts { type: "invite_link_created", code, actor }, returns the link
- revoke: marks the link inactive, broadcasts { type: "invite_link_revoked", code, actor } and returns true; an unknown code returns false and broadcasts nothing
Observed: every member's client receives the actor's passwordHash and email.
Logs
[rt] T1 <- invite_link_created actor={"id":"U1","name":"Kai","email":"kai@example.com","passwordHash":"hash:9f2c…","avatar":"k.png"}The code as shipped
src/workspace/invites.js (editable)
exports.createInviteLink = function (workspace, user, code, bus) {
var link = { code: code, workspace: workspace.id, active: true };
workspace.links.push(link);
bus.broadcast(workspace.id, { type: "invite_link_created", code: code, actor: user });
return link;
};
exports.revokeInviteLink = function (workspace, user, code, bus) {
for (var i = 0; i < workspace.links.length; i++) {
var link = workspace.links[i];
if (link.code === code && link.active) {
link.active = false;
bus.broadcast(workspace.id, { type: "invite_link_revoked", code: code, actor: user });
return true;
}
}
return false;
};
Read-only context: src/workspace/bus.js, src/workspace/users.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.