Latest / Decrypted: The UK Cyber Briefing / A Zammad zero-day chain let an AI agent breach the people who find zero-days
Transcript
- 0:03This is Decrypted. Thursday, the first of October.
- 0:06A Zammad zero-day chain let an AI agent breach the people who find zero-days.
- 0:13The organisation that finds other people's security holes has been breached through two of them.
- 0:19The Dutch Institute for Vulnerability Disclosure, D I V D, said this week that attackers got into its network
- 0:27through two previously unknown flaws in Zammad, an open-source helpdesk system.
- 0:33And the way the intruder worked points to an agentic AI at the controls.
- 0:38For UK organisations, the lesson isn't the AI.
- 0:43It's how much a helpdesk server was trusted.
- 0:46Next.
- 0:56D I V D spotted it the next day.
- 1:00It disconnected its datacentre systems and brought in Merlon Security for forensics.
- 1:06It reported the flaws to Zammad on 24 September, and began warning other users from 26 September.
- 1:13The two bugs chain together.
- 1:15The first, C V E twenty twenty-six, one zero two four eight nine, is a session hijacking flaw.
- 1:23It gives remote code execution as the low-privilege zammad user.
- 1:28D I V D lists it as affecting versions 6.
- 1:323.0 through 6.5.4, with limited exploitability in 7.
- 1:380.0 to 7.1.3.
- 1:50ome root. D I V D lists it as affecting every version from 1.
- 1:555.0 to 7.1.0-alpha. BleepingComputer reports the pair let the attacker climb from nothing to root in seconds.
- 2:05And also.
- 2:09Think of a hotel. The first flaw is a stolen staff lanyard.
- 2:14It gets you into the building as a cleaner.
- 2:17The second is a master key left in the cleaners' cupboard.
- 2:20Together, they open every room.
- 2:23And an automated guest can try every door faster than any night porter can react.
- 2:28And also.
- 2:33D I V D's case file describes the breach as a hack through AI agents.
- 2:39That's D I V D's assessment, based on the behaviour it saw.
- 2:42The investigation is still open.
- 2:45BleepingComputer reports that the agent recorded its own reasoning, which let D I V D reconstruct what it did
- 2:52.
- 2:55A human intruder pauses, makes mistakes and keeps office hours.
- 3:00Software that chains a session bug into root and starts reading files doesn't.
- 3:05So the gap between first access and data leaving can shrink to minutes.
- 3:10What helped D I V D was ordinary design.
- 3:13Network segmentation, BleepingComputer reports, stopped deeper lateral movement.
- 3:19And D I V D noticed the activity the next day.
- 3:22It has also made its case file public, and kept it updated.
- 3:27And finally.
- 3:31Three decisions would have limited this.
- 3:33First, a service account that can't become root.
- 3:37C V E twenty twenty-six, one zero two four nine zero is a local privilege escalation.
- 3:43So running the application in a locked-down container turns a root compromise into a contained one.
- 3:50Second, segmentation that assumes the helpdesk will fall.
- 3:54The agent reached other services and files.
- 3:57Segmentation is the control that decides how far a bad day spreads.
- 4:02Third, a patch plan for tools nobody calls critical.
- 4:06BleepingComputer says Zammad has more than 2,000 customers.
- 4:11D I V D's advice is blunt.
- 4:14Upgrade to version 7 or take the instance offline.
- 4:18Then run its verification script against your logs.
- 4:20The cost is modest. List your self-hosted helpdesk, wiki and ticketing systems.
- 4:26Ask who can reach them from the internet.
- 4:29And ask what a root user on that box could read next.
- 4:32Opinion, not advice: if the honest answer is everything, the segmentation is the project, not the patch.
- 4:39That was Decrypted. The written version and every source are linked in the show notes.
- 4:45Thanks for listening.