Latest / Decrypted: The UK Cyber Briefing / The Metabase flaw in a password reset box, and the customers it caught
Transcript
- 0:03This is Decrypted. Saturday, the eighth of August.
- 0:06The Metabase flaw in a password reset box, and the customers it caught.
- 0:12Here's one for anyone running a dashboard tool.
- 0:16A single web page in the open-source analytics tool Metabase, one you can reach without logging in, let attac
- 0:24kers write their own instructions into a customer's database.
- 0:27They then walked out the other side as an administrator.
- 0:31Metabase rates the flaw the maximum 10.
- 0:350 on the C V S S scale. It says the flaw was under active exploitation before any fix existed.
- 0:43And this week two of its customers, the laptop maker Framework and the form-builder Tally, confirmed their Me
- 0:50tabase instances were breached as a result.
- 0:53For any UK organisation that has plugged a B I or dashboard tool into a production database, this is a live w
- 1:02arning, not an abstract one.
- 1:04Next. How a password reset became a database break-in.
- 1:09The vulnerable code sat behind the page for resetting a forgotten password.
- 1:14That page is reachable by design without logging in first.
- 1:19The flaw is that Metabase took part of what a visitor submitted there and dropped it straight into a database
- 1:25query. It didn't treat it purely as data.
- 1:28Picture a hotel. Guests fill in a slip to request a password reset.
- 1:34The porter reads the slip aloud into a microphone wired to the safe's lock.
- 1:39Phrase the slip correctly, and the porter, meaning only to help, opens the safe instead.
- 1:45That's S Q L injection. It's a class of bug that's been well understood for decades, and avoidable through b
- 1:52asic coding hygiene.
- 1:58It's tracked as G H S A-vwf4-m7j8-wcjf, since no C V E has yet been assigned.
- 2:09Framework told customers that attackers accessed its instance on 3 August and obtained names, email addresses
- 2:17, phone numbers and physical addresses.
- 2:19Tally reported its own environment compromised the same day.
- 2:23Metabase has shipped fixes across every supported release line, and says Cloud customers were patched automa
- 2:30tically. If you self-host version 1.
- 2:3358 or later, upgrade without delay.
- 2:36And if the reset-password endpoint was internet-facing, treat it as compromised.
- 2:41And finally. The Secure by Design lesson.
- 2:45The coding mistake is specific.
- 2:47But the blast radius is the generic lesson.
- 2:50Metabase instances typically hold live credentials for a company's actual production databases.
- 2:57So admin access to Metabase meant read access to whatever it was connected to.
- 3:03That's a recurring failure in analytics and reporting tooling.
- 3:06A convenience layer sits in front of sensitive data.
- 3:10It's reachable before login.
- 3:12And it carries credentials scoped far wider than the reporting job needs.
- 3:17So if you run any self-hosted B I, monitoring or reporting tool, ask two questions this week.
- 3:24Does it expose anything reachable before authentication?
- 3:28And does its database credential have write access, or access to tables it never actually queries?
- 3:34Tighter scoping on that connection wouldn't have stopped the S Q L injection.
- 3:39But it would have shrunk what an attacker could do once inside.
- 3:42That was Decrypted. The written version and every source are linked in the show notes.
- 3:48Thanks for listening.