Latest / Decrypted: The UK Cyber Briefing / Zyxel's June patch did not stop the switch attacks, because the flaw was a different one
Transcript
- 0:03Good evening, and welcome to Decrypted.
- 0:05I'm Belinder. It's Thursday, the fifth of November, twenty twenty-six, and this is the evening edition.
- 0:11Zyxel's June patch did not stop the switch attacks, because the flaw was a different one.
- 0:18The patch that was meant to close the hole didn't close it.
- 0:22Zyxel has now fixed a zero-day, a flaw attackers used before any fix existed, in its gee ess nineteen hundred
- 0:29small network switches. Nearly 1,000 of them were compromised in attacks blamed on a different bug, one patched
- 0:36in June. Switches are unglamorous kit, which is rather the point.
- 0:41So, what actually happened?
- 0:44The attacks began around 17 August.
- 0:47GreyNoise, a threat monitoring firm, counted 996 compromised devices across 48 countries.
- 0:54On 21 September it blamed C V E twenty twenty-six, seven two seven three, the public reference number for a flaw
- 1:01Zyxel patched in June. Then Binarly, a firmware security company, took the attackers' script apart.
- 1:08It found the script still worked against all ten firmware releases carrying the June fix.
- 1:13Zyxel confirmed a new flaw, C V E twenty twenty-six, one zero seven four four one, on 11 October.
- 1:21It published its advisory on 3 November, according to bleeping computer.
- 1:25So how does the trick work?
- 1:28Think of a bouncer who checks the guest list by reading the tally at the top of the clipboard.
- 1:33The June patch added that check.
- 1:35The attackers altered the tally first, so the check passed and the crowd walked in.
- 1:40Technically, the switch's web management page copies a request into a fixed-size space.
- 1:45Attackers corrupted the parameter counter the new checks relied on before it was validated.
- 1:50An unauthenticated attacker sending crafted web requests can then run operating system commands.
- 1:56SecurityWeek gives it a severity score of 8.
- 1:598 out of 10. Zyxel's advisory puts the attacker on the lan, the local area network inside one building.
- 2:06bleeping computer says only network access.
- 2:10And what would a defender actually see?
- 2:13Very little. A switch runs no security agent and rarely logs usefully.
- 2:18The recovered script collected configurations, hashed root credentials and network information.
- 2:23That's a map of your estate, and a head start on guessing passwords elsewhere.
- 2:28GreyNoise suspects a Chinese-speaking actor.
- 2:31That's its attribution, not proven fact.
- 2:33bleeping computer says it remains unclear whether the exploit was built to defeat the June fix or abused a related
- 2:40flaw that fix missed. Zyxel's advisory doesn't say whether it saw exploitation.
- 2:45That claim comes from Binarly, as SecurityWeek reports.
- 2:49So what's the Secure by Design lesson here?
- 2:52The June fix treated a symptom.
- 2:55The flaw class is trusting numbers that arrive with a request, such as lengths and counts.
- 3:00Secure by Design means validating each one at the boundary, in one place, rather than patching overflows one
- 3:07by one. A management page should also never be reachable from ordinary user networks.
- 3:12Put switch administration on its own small network, open to a few named machines, and this flaw becomes far harder
- 3:19to use. It's an afternoon's work for most sites.
- 3:22Check your models against Zyxel's advisory.
- 3:25Builds ending.2)C0 and earlier are vulnerable, and the fix ends.
- 3:303)C0. Either way, first attack to public advisory took about eleven weeks.
- 3:37As always, this is opinion, not advice.
- 3:41That was Decrypted, with me, Belinder.
- 3:45The written version and every source are linked in the show notes.
- 3:48Thanks for listening. Stay patched, and stay sceptical.