Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Tech Talks With Kinsoft

Tech Talks With Kinsoft artwork

Mathspace - 1,079,819 People, a 23-Day Gap, and the Advisory That Never Reached Anyone

Sep 15, 202620 minAudio

Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Sydney edtech company Mathspace has disclosed a data breach affecting 1,079,819 students, parents and guardians, teachers and staff across Australia and New Zealand. The cause was not an unavailable patch - it was a vulnerability-notification process that never escalated the advisory to anyone who could act. The flaw: CVE-2026-72898, an unauthenticated SQL injection in Metabase's password reset endpoint, granting administrator access without a valid login. CVSS v3.1 base score 10.0 and CVSS v4.0 base score 10.0. Metabase published its advisory and patched versions on 6 August 2026; confirmation it had already been exploited in the wild as a zero-day followed on 8 August; CISA added it to the Known Exploited Vulnerabilities catalogue on 11 August. Timeline. 6 Aug: advisory published; Mathspace's internal notification process fails to identify and escalate it. 10 Aug: earliest unauthorised access, four days after the patch became available. 27 Aug: the attacker downloads data from the Australian reporting database. 29 Aug: Mathspace patches, 23 days after the advisory, but does not perform the compromise checks Metabase recommended for potentially exposed instances. 3 Sep: a historical access log review confirms the breach, five days after patching; Metabase is taken offline and all API keys and database credentials rotated. 4 Sep: notifications to the OAIC, ASD's ACSC, New Zealand's Privacy Commissioner and NCSC, and Australian state and territory education departments. 5 Sep: public disclosure. 6 Sep: individual notifications begin. Twenty-four days from intrusion to detection; two days from detection to disclosure. Data involved: user ID, username, first and last name, email address, country, time zone, user type, email verification status, last active date, last login date and date joined - not every field for every person. Explicitly not exposed: academic records, learning activities, results and assessments, passwords including hashes, authentication tokens, SSO credentials and API credentials. No password resets are being required, and as at its 8 September update Mathspace had seen no evidence the data has been published, distributed, sold or otherwise misused. Attribution, read carefully: Mathspace states the identity of the attacker remains unknown and no group has claimed the breach. Separately, BleepingComputer has reported that ShinyHunters added Metabase to its leak site on 11 August and links the group to the wider campaign against Metabase instances - that is reporting about a campaign, not a confirmed attribution for Mathspace. Whether a ransom was demanded is unknown; asked by Information Age, Mathspace pointed back to its blog post. What to take from it. First, shadow infrastructure needs an owner - if a self-hosted tool isn't on an asset inventory with a named owner subscribed to that vendor's advisories, it isn't being patched. Second, patching is not the finish line: if an internet-reachable system was exploitable, assume compromise until the logs prove otherwise. Third, internal tools hold external data - Metabase had no customer logins and no public front door, and was still the pivot to a million records because it was internet-reachable and connected to production data warehouses. Mathspace's disclosure was unusually detailed and self-critical, naming its own process failures. Melbourne barrister Peter A Clarke, who writes on privacy law, called it excellent and said it provided real information to customers rather than the usual boilerplate. Visit www.kinsoft.com.au to talk through your security and IT needs. Sources: Mathspace incident disclosure (Alvin Savoy, CTO, 5 September 2026, updated 8 September); BleepingComputer; ACS Information Age; Cyber Daily; The Hacker News; Metabase advisory GHSA-vwf4-m7j8-wcjf; CISA KEV catalogue.

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

Imagine leaving your front door wide open when you go to bed. Right. Which is just terrifying to think that. Exactly. And, you know. Not because you don't have a lock. You have this fantastic state -of -the -art lock. And it's not like you deliberately decided to take a risk either. Yeah, you didn't just forget. No, you left the door open simply because the sticky note reminding you to turn the deadbolt got lost in the mail. Like a piece of paper literally just didn't reach the right desk. A total administrative failure. Yeah, and because of that one little bureaucratic

hiccup, over a million people had their personal data exposed. It's wild. So welcome to today's deep dive. I am your host. And as always, I'm joined by our resident cybersecurity expert to help me figure this out. Glad to be here. This is a really fascinating case to unpack. It really is. We are looking at a massive cybersecurity incident involving the Australian ed tech company, Mathspace. We're pulling our source material today from a breakdown on a show called Tech Talks with Kinsoft. A really great breakdown, by the way. Yeah, absolutely. What becomes immediately

clear from their reporting is that the biggest threat to your data isn't always like. a brilliant hacker bypassing some firewall, sometimes it's just a catastrophic failure of mundane office communication. Which completely flips how we usually think about risk, you know? Right. I mean, you assume a breach of this scale requires zero -day exploits deployed by these nation -state actors in some high -stakes digital chess match. Like in the movies. Exactly, like a movie. But in reality, modern breaches are almost always process failures first. A patch gets released,

the alert goes into an unmonitored inbox, and the attackers simply walk through an open vulnerability. So for anyone listening, whether you manage an enterprise IT network or you just trust your data to cloud platforms, which, I mean, that's literally all of us. Yeah, everyone. Understanding the anatomy of this specific breach reveals exactly how threat actors exploit that gap between a security alert being published and a company actually hitting update. The dangerous gray area. Right. So to understand the break -in, we really have to look at the target. Which strangely wasn't

their main vault. Yeah, it wasn't. Because Mathspace is a major player. They were founded in Sydney back in 2010, and they run this online mathematics learning platform that is heavily utilized across roughly 3 ,400 Australian schools. And they have a massive presence overseas too, right? Yeah. In New Zealand, the U .S., and the U .K. Yeah, so they sit on a mountain of student and teacher data, but the hackers didn't break into the student learning platform. They compromised a secondary tool. called Metabase. Yeah, and Metabase is

business intelligence software. It's essentially an internal visualization tool for the staff. Okay, so what does it actually do? Well, instead of making your staff write raw SQL queries to figure out how many users signed up last month, Metabase connects directly to your databases. Right. And it lets employees build dashboards and charts through this really simple graphical interface. Super common. Wait, so if this is just an internal tool for staff to make pie charts, why on earth is it reachable from the open Internet? Like, why isn't it locked behind a VPN or entirely

walled off? That paradox is actually a massive vulnerability across modern corporate architecture. Really? Oh, yeah. In the era of remote work and cloud native infrastructure, the whole concept of a secured perimeter is almost extinct. Companies deploy tools like Metabase in cloud environments, like AWS or Google Cloud, to easily connect them to their cloud data warehouses. Ah, okay, so it's about convenience. Exactly. For convenience, so a remote product manager can log in without

wrestling with a clunky VPN, the instance is often just left exposed to the public internet. But it's not like you can just Google it, right? Well, no, it might not have a public DNS record like dashboard .mathspace .com. But attackers don't use URLs anyway. They use automated scanners. Oh, wow. So they're just constantly looking. Yeah. These scanners constantly ping every single IP address on the Internet looking for a specific software signature. Yeah. If it's exposed, they will find it in minutes. And when they found this one, they definitely hit the jackpot. The vulnerability here, which was cataloged as CVE

-2026 -72898, was an unauthenticated SQL injection in the password reset endpoint. A really nasty one. Yeah, the industry gave this a CVSS severity score of 10 .0 out of 10. Which is the absolute maximum. You can't get worse than a 10. Right, but I want to understand the actual mechanism here. How does a simple password reset page hand over the keys to the entire system? So a SQL injection happens when an application fails to properly sanitize the input a user types into

a form. Sanitize meaning like checking to make sure it's actually an email address. Precisely. In a normal password reset, you type your email. And the backend database checks if that email exists. Yeah. But with this vulnerability, an attacker doesn't type an email. They type raw database commands into that text box. Oh, geez. Yeah. And because Metabase didn't filter that input, the underlying database just executed the attacker's commands as if they were legitimate instructions from the system itself. So they're essentially tricking the database into hijacking itself. Exactly. And what pushes this to a CVSS

10 .0 is the unauthenticated part. Right. They don't even need an account. Nope. The attacker doesn't need to steal a password. They don't need to guess a credential or possess any existing privileges. They can just hit the public -facing password reset page, inject the malicious SQL code, and instantly grant themselves administrative access to the entire Metabase instance. Wow. It is the absolute worst -case scenario. Zero friction, zero authentication. Total system compromise. OK, so because that specific door was exposed,

a ticking clock started the second this vulnerability was publicly announced. The race was on. Yeah. And the timeline Kinsoff lays out here is just agonizing. It perfectly illustrates the terrifying speed of modern attackers versus the lumbering slowness of corporate bureaucracy. It's a classic mismatch. It really is. So on August 6th, Metabase officially publishes the security advisory and releases a patch. The fix is live. Right. The vendor did their job. But then, just two days later, on August 8th, threat intelligence confirms

this is being actively exploited in the wild. Attackers have already weaponized the flaw. 48 hours later. That is so fast. I know. Then, on August 11th, the U .S. Cybersecurity and Infrastructure Security Agency, CISA, adds this exact vulnerability to their known exploited vulnerabilities catalog. Which is a huge deal. That catalog is the gold standard for what you need to fix yesterday. Right. So by August 11th, we have... It really comes down to the psychology and the mechanics of alert fatigue. Alert fatigue. Yeah. Imagine

trying to find a single life -saving text message while you're standing on the floor of a noisy casino with alarms and flashing lights going off in every direction. That sounds like a nightmare. That is exactly what managing enterprise software vulnerabilities feels like right now. A modern company uses hundreds of different software libraries, APIs, and vendor tools. Right. It's not just one software they're running. No, it's a massive web. Dozens of new CVEs are published every single day. If your organization doesn't have a strict

programmatic mapping that routes a specific alert for a specific tool directly to the human engineer responsible for maintaining it. It just gets lost. Yeah. That alert drops into a generic IT admin inbox. Basically the digital equivalent of a junk drawer. Exactly. It gets buried under 100 other automated emails. Or. Quite commonly, the developer who initially set up that specific Metabase instance two years ago has left the company, and the vendor security alerts are just bouncing off a deactivated email address. So

while that alert is sitting in a dead inbox, the attackers are moving. Oh, they are moving fast. Just four days after the patch was published, on August 10th, attackers successfully breached Mathspace's Metabase instance. Four days. Four days. That is the gap between a software vendor announcing a flaw and an attacker kicking down your door. But they didn't actually steal the data right away, did they? No, they didn't. And this really highlights the operational patience of modern threat actors. They breached the system

on August 10th, but they waited until August 27th to actually execute their primary objective and exfiltrate the Australian reporting database. That is 17 days of dwell time just sitting there. Right. During that window, they were likely mapping the environment, trying to understand what Metabase was connected to, and ensuring they had stable, persistent access before making a noisy move like downloading massive databases. Because downloading a database triggers alarms, right? Exactly. It creates a spike in network traffic. So they want to be sure they have everything set up before

they pull the trigger. Meanwhile, Mathspace remains completely unaware. It took them until August 29th, which is 23 days after the initial alert, to finally apply the Metabase patch. 23 days is a fatal delay for an internet -facing zero day. Yeah, and they only patched it because a completely separate subsequent notice happened to catch their attention. It was pure luck they even saw the second notice. Right. But what happens on August 29th is arguably the most instructive

failure in this entire case. Because you would assume August 29th is the finish line. You'd think so, yeah. They finally applied the patch. They turned the deadbolt. Problem solved. Yeah, the false finish line. What do you mean? Well, when you apply a patch, all you are doing is updating the software's code so that specific vulnerability no longer exists. You have fixed the lock on the door. But Mathspace stopped there. Right. They completely... failed to carry out the compromise checks that Metabase explicitly warned all users to perform if their instance

had been internet exposed. Yeah, the source outlines those checks. They recommend session revocation, API key review, admin account review, and credential rotation. Crucial steps. But why are those specific actions so critical mechanically? Like if you patched the hole, aren't the attackers locked out? Not if they left a back door open from the inside. Oh, I see. Let's break down the mechanics here. If a hacker had administrative access for nearly three weeks, they didn't just browse around.

They likely generated their own API keys. And what exactly does an API key do in this context? Wow. Yeah. So what does this all mean for the

listener? It is basically like coming home. Finding your front door wide open, locking it, and then just sitting on the couch to watch TV without checking to see if anyone is still hiding inside your house. That is the perfect analogy. You have secured the perimeter, but completely ignored the interior. Right. Session revocation is literally cutting the active connection of anyone currently logged in. Credential rotation means changing the passwords for the databases that Metabase talks to, assuming the attacker scraped those

credentials while they were inside. And Mathspace didn't do any of that at first. No. By skipping these checks, they operated under the incredibly dangerous assumption that patching a system retroactively evicts an attacker. It doesn't. Because they skipped those checks, they sat blind for another five days. It wasn't until September 3rd, while conducting a historical review of their access logs, that Mathspace finally realized an unauthorized actor had been in their system. Five whole days after they thought they fixed the problem. Yeah. They skipped it. Honestly. The drive to just

hit the update button and close the ticketing system task is a very powerful psychological motivator for IT teams that are driven by metrics. Like just getting it off the desk. Exactly. Actually hunting through access logs to verify you haven't been breached is tedious, time -consuming work. Yeah. But Skiving, it costs them crucial response time. However, the Kinsoft source emphasizes a massive pivot here. Once Mathspace actually looked in the logs and realized they had been compromised, their response behavior completely

inverted. It was a night and day difference. Yeah, they went from agonizingly slow and disconnected to incredibly aggressive and transparent. Their September 3rd response is basically textbook incident remediation. What did they do? The moment they detected the breach, they didn't just tweak settings. They amputated the compromised LIMP. They took Metabase entirely offline. They revoked all API keys. Okay, so they finally did the checks. Oh, they went further. They went into their massive cloud data warehouses, specifically their Australian and U .S. snowflake environments, and completely

disabled the database access accounts that Metabase used. They rotated the passwords on their Cloud SQL databases. They systematically severed every internal connection Metabase had to the broader company infrastructure. And externally, they move just as fast. The very next day, September 4th, they were already notifying government authorities. Right. The Office of the Australian Information Commissioner, the Cybersecurity Center, New Zealand's Privacy Commissioner. And then by September 5th. public disclosure was out. And by the sixth,

they were directly emailing the affected individuals. Think about that timeline for a second. 24 days from the initial intrusion to detection, but only 48 hours from detection to public disclosure. Yeah. In corporate crisis management, releasing a public statement detailing a breach two days after discovery is almost unheard of. Usually companies drag their feet for months. Let's talk about the blast radius, though, because over a million people. 1 ,079 ,819 students, parents, teachers and staff across Australia and New Zealand

were caught in this. What was actually taken? Well, the attackers exfiltrated basic user information, user IDs, first and last names, email addresses, account types and the timestamps of when users last logged in. But the critical part of the story is what was not taken. Right. No academic records, no grades, no learning activity. That's right. And from a technical standpoint, the most crucial saving grace here. No passwords. Not even hashed or encrypted passwords. No authentication tokens. That technical detail is what prevents

this from being a total catastrophe. How so? If attackers steal password hashes, they can run offline cracking tools to decipher them. If they steal authentication tokens, they can potentially hijack active web sessions and impersonate users on the platform. I see. Because neither of those were taken, the attackers secured a massive directory of names and emails, sure. But they did not acquire the credentials necessary to move laterally into the user's broader digital lives or completely take over their Mathspace accounts. And as of the source's publication, there's no evidence this data has been monetized

or misused yet. Thankfully, no. Speaking of the attackers, we should note that attribution remains pretty murky. Mass Space hasn't identified the actor and no ransom demand has been publicized. Right. The source does mention that tech outlets like Bleeping Computer linked a broader campaign targeting Metabase instances to an extortion group called Shiny Hunters. Yeah. But we need to be careful there. Exactly. Because as the Kinsoft text strictly notes, that is general industry reporting. It is not confirmed attribution for the Mathspace incident specifically. Yeah.

In the immediate aftermath of a breach, separating verified forensic evidence from broader threat landscape speculation is super vital. Threat actors often use the exact same automated scripts, which makes attribution based purely on the exploited vulnerability incredibly difficult. Makes sense. What really stands out to me about the aftermath, though, is the reaction to Mathspace's public disclosure. It was overwhelmingly positive. Yeah. Melbourne privacy barrister Peter A. Clarke publicly praised them, calling their self -critical disclosure excellent. Which is rare for a lawyer to say.

Right. Legal departments usually fight tooth and nail against this kind of transparency to minimize liability. Why is admitting failure like this so valuable to the industry? Because generic boilerplate statements like, we take your privacy seriously and experience this sophisticated cyber event, those teach the industry nothing. They're just PR fluff. Exactly. Mathspace explicitly admitted their internal alert routing failed. They admitted they applied a patch but failed to perform compromise checks. Wow. By trading

short -term PR embarrassment for technical transparency, they provided actionable intelligence. Other engineering teams can read that disclosure and immediately go check their own database logs or audit their own vulnerability notification pipelines. Transparency basically acts as an inoculation for the rest of the ecosystem. Which perfectly sets up how you, listening to this, can apply these lessons to your own networks. The source material brings in this highly effective triage framework from Steve Hunter, a director of engineering at Arctic Wolf. How do you prevent

a forgotten internal tool from leaking a million records? Hunter's framework demands that we stop prioritizing vulnerabilities based solely on a vendor's CVSS score and start analyzing the environmental context. So looking at the bigger picture. Yes. You have to ask two distinct questions. First, is the system exposed to the Internet? Second, what data can the system reach? It's the blast radius. Exactly. Metabase was just a reporting tool. If you asked an executive to list their mission -critical, highly defended applications, Metabase wouldn't even make the list. Right. But because of its function, it

had high -level read access directly into their Snowflake and Cloud SQL production databases. A low -importance system with high data access is the exact asymmetric target an attacker wants. Because it's easier to hit? Yeah, they don't want to try and brute force their way through the heavily monitored front door of your core product if they can just slip through the unmonitored side window of a secondary reporting tool. So how do you defeat that shadow infrastructure? Like the tools a developer quietly spun up on an AWS instance three years ago that eventually

became structurally load -bearing. You have to eliminate orphan software. And the solution isn't some fancy AI firewall. It's rigorous administrative hygiene. Just doing the boring work? Pretty much. You must maintain a dynamic inventory of every single software instance running in your environment. More importantly, every single instance must have a specific named human owner assigned to it. And that human's active email address must be subscribed to the vendor's security feed. And if they leave? If a tool doesn't have an

owner, it gets taken offline. Period. And the final piece of the puzzle here is changing how we view the patching process itself. As we saw with Mathspace's five -day blind spot, patching is the middle of the incident response, not the end. It's never the end. If a system was vulnerable and exposed to the internet, you have to operate under the assumption that it was successfully breached. You have to review the API keys, audit the logs, and rotate the credentials. Because in modern cybersecurity, The gap between a public patch announcement and a weaponized exploit scanning

the internet is now measured in hours, not weeks. Four days was all it took here. Four days? Yeah. If you patch late, you aren't preventing an intrusion. You're just locking the attacker inside with you. Man, that raises a vital question for you, the listener. How much shadow IT is quietly humming away at your workplace right now? We constantly worry about our highly sensitive financial data or user passwords being locked away in the main digital vault. But if a seemingly mundane, internal -only business intelligence tool can act as the

skeleton key to over a million user records, well, what other harmless -looking software in our daily lives is silently connected to the most sensitive data we possess? Could the biggest threat to our privacy actually be the tools we assume are just too boring for hackers to care about? It's a sobering thought. It really is something to deeply consider the next time you assume an internal system doesn't need external defenses. Thank you for joining us on this deep dive. Stay curious, audit your digital infrastructure, and we will catch you next time.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Iris Ohyama - A Suspicious File in the Cloud, 7.7 Million Customers at Risk, and an Online Store That Went Dark

    Nov 19, 202620 minAudio

    Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Japanese home goods company Iris Ohyama (online store operator Iris Plaza) found a suspicious file in an external...

    Credit the people on this episode

  2. Who Gives A Crap - A Marketing Supplier Breached, Six Days to Tell the Client, and Customer Data That Didn't Need to Be There

    Nov 17, 202619 minAudio

    Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Australian online retailer Who Gives A Crap told customers on 7 November 2026 that their information was accessed...

    Credit the people on this episode

  3. Last Week in Tech - An Outlook Zero-Day That Leaks Your Password Hash, Chrome's Eighth Exploited Bug, and Nvidia Without Jensen Huang

    Nov 15, 202621 minAudio

    Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Last week in tech, 7 to 14 November 2026. Microsoft's November Patch Tuesday (10 November) fixes well over a...

    Credit the people on this episode

  4. Chainalysis - From "Non-Sensitive" to "All Users": How a Breach Notice Changed in Five Days

    Nov 12, 202619 minAudio

    Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Chainalysis disclosed on 30 October 2026 that an external actor using "offensive agentic techniques" accessed...

    Credit the people on this episode

  5. NSW Health - A Dental Voucher Website, Four Gigabytes Taken, and the Providers Whose Details Were Exposed

    Nov 10, 202623 minAudio

    Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! NSW Health reported unauthorised access to its Oral Health Fee For Service Scheme website on 29 October 2026;...

    Credit the people on this episode