Heartbleed's Little Cousin

Hard

· Backend

Incident

SEV-1

BUG-HB

Priority: Existential · reported by security

Time to fix: 35 min

Failing checks on the shipped build

  • over-claimed lengths leak nothing

    only what was sent: expected "bird" but got "birdSECRET_MASTER_KEY_0xDEADBEEF_SESSION_TOKENS"

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

OpenSSL · 2014

Inspired by Heartbleed (2014): a heartbeat request says "echo 4 bytes back — no wait, echo 64,000" — and the server obliges, reading past the payload into memory holding private keys.

The echo service (locked memory region included) must never return more bytes than the client actually sent.

Code map

var memory = require("./memoryRegion");

// Echoes the heartbeat payload back to the client.
exports.echo = function (payload, claimedLength) {
  var buffer = payload + memory.ADJACENT_MEMORY;
  return buffer.slice(0, claimedLength);
};

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.

Heartbleed's Little Cousin — JavaScript Bug Hunt

Inspired by Heartbleed (2014): a heartbeat request says "echo 4 bytes back — no wait, echo 64,000" — and the server obliges, reading past the payload into…

  • Language: JavaScript
  • Layer: Backend
  • Difficulty: Hard
  • Concepts: Security, Bounds
  • Modelled on: OpenSSL · 2014
  • Visible tests: honest requests echo exactly; over-claimed lengths leak nothing; shorter claims truncate normally
  • Reward: 50 XP for a complete fix

Incident

  • Severity: SEV-1 (priority: Existential)
  • Ticket: BUG-HB
  • Reported by: security
  • Time to fix: 35 minutes, the target for a hard incident

Failing checks on the shipped build

  • over-claimed lengths leak nothing — only what was sent: expected "bird" but got "birdSECRET_MASTER_KEY_0xDEADBEEF_SESSION_TOKENS"

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

Inspired by Heartbleed (2014): a heartbeat request says "echo 4 bytes back — no wait, echo 64,000" — and the server obliges, reading past the payload into memory holding private keys.

The echo service (locked memory region included) must never return more bytes than the client actually sent.

Bug report

BUG-HB · Priority: Existential · Reported by: security

echo(payload, claimedLength):

  • return AT MOST payload.length bytes of the payload
  • the claimed length is untrusted client input

Observed: over-claimed lengths return the payload PLUS whatever sits next to it in the buffer — including the region marked SECRET.

Logs

[tls] heartbeat req len=4 claimed=64 -> response contains "SECRET_MASTER_KEY"

The code as shipped

src/tls/heartbeat.js (editable)

var memory = require("./memoryRegion");

// Echoes the heartbeat payload back to the client.
exports.echo = function (payload, claimedLength) {
  var buffer = payload + memory.ADJACENT_MEMORY;
  return buffer.slice(0, claimedLength);
};

Read-only context: src/tls/memoryRegion.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.