Version 2.3.10 Is Not Older Than 2.3.9

Medium

· Backend

Incident

SEV-1

BUG-CVE2017-5638

Priority: Critical · reported by security

Time to fix: 20 min

Failing checks on the shipped build

  • a double-digit patch is not older

    10 is a larger patch than 9: expected false but got true

  • a double-digit major is not older

    expected false but got 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

Equifax · 2017

Modelled on the Equifax breach (2017), which turned on a known-vulnerable dependency that was never upgraded. A common contributing bug in patch tooling is comparing semantic versions as strings, so "2.3.10" sorts before "2.3.9" and a patched build is reported as still vulnerable — or worse, an unpatched one as fixed.

versions.js compares versions lexicographically.

Fix isVulnerable so versions are compared numerically, component by component.

Code map

// True when the installed version predates the fix.
exports.isVulnerable = function (installed, fixedIn) {
  return installed < fixedIn;
};

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.

Version 2.3.10 Is Not Older Than 2.3.9 — JavaScript Bug Hunt

Modelled on the Equifax breach (2017), which turned on a known-vulnerable dependency that was never upgraded.

  • Language: JavaScript
  • Layer: Backend
  • Difficulty: Medium
  • Concepts: Security, Versioning
  • Modelled on: Equifax · 2017
  • Visible tests: an older patch is vulnerable; a double-digit patch is not older; a double-digit major is not older
  • Reward: 50 XP for a complete fix

Incident

  • Severity: SEV-1 (priority: Critical)
  • Ticket: BUG-CVE2017-5638
  • Reported by: security
  • Time to fix: 20 minutes, the target for a medium incident

Failing checks on the shipped build

  • a double-digit patch is not older — 10 is a larger patch than 9: expected false but got true
  • a double-digit major is not older — expected false but got 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 the Equifax breach (2017), which turned on a known-vulnerable dependency that was never upgraded. A common contributing bug in patch tooling is comparing semantic versions as strings, so "2.3.10" sorts before "2.3.9" and a patched build is reported as still vulnerable — or worse, an unpatched one as fixed.

versions.js compares versions lexicographically.

Fix isVulnerable so versions are compared numerically, component by component.

Bug report

BUG-CVE2017-5638 · Priority: Critical · Reported by: security

isVulnerable(installed, fixedIn) must return true when the installed version is strictly OLDER than fixedIn, comparing "major.minor.patch" numerically.

Observed: string comparison decides that "2.3.10" < "2.3.9", so a fully patched host is flagged, and "10.0.0" < "9.0.0" leaves a truly vulnerable host unflagged.

Logs

[scan] host web-14 installed=2.3.10 fixedIn=2.3.9 vulnerable=true (wrong)
[scan] host web-22 installed=10.0.0 fixedIn=9.0.0 vulnerable=false (wrong)

The code as shipped

src/scan/versions.js (editable)

// True when the installed version predates the fix.
exports.isVulnerable = function (installed, fixedIn) {
  return installed < fixedIn;
};

Read-only context: src/scan/SEMVER.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.