Lessons from the Railway hack

Tier B · Patch this week – Put it in the sprint

Tier B because: Full takeover OR secrets exposed OR supply chain

Reach

Attack

Damage

Fix

Full takeover

The Brief

Cloud platform Railway has published a detailed postmortem about its recent hack.
The Pragmatic Engineer newsletter covers what can be learned from the incident.
The attacker's method is described in the postmortem, but the source excerpt available here is truncated.

Why it matters

The postmortem gives developers a detailed account of how a cloud platform was breached, which can inform their own incident response and security reviews.

The checklist behind the tier

Checklist · 2 of 10 yes · estimated from older data, not yet checked against the sources

Yes	Hits tech teams	Does it affect software, devices or services that developers, ops or IT teams build with, run or are responsible for?
No	Core infrastructure	Is the flaw in, or the compromise of, software that nearly every team runs?
No	Popular tool	Is the flaw in, or the compromise of, a widely used framework, tool, platform, OS or package?
No	Exploited in the wild	Do sources report real attacks using it?
No	Public exploit	Is a working exploit or detailed proof-of-concept public?
No	Remote, no login	Can an attacker use it over the network without credentials or user interaction?
Yes	Full takeover	Does it lead to code execution, root/admin rights or full account takeover?
No	Secrets exposed	Were credentials, tokens, keys, configs, source code or customer data stolen or exposed?
No	Supply chain	Was malicious code shipped through a channel developers trust?
No	No fix yet	Is there no patched version yet?

Source

The Pulse: What can we learn from the Railway hack? ↗ The Pragmatic Engineer · 50 min ago

First seen 50 min ago · 1 source · Full story page · How tiers are decided