Latest / Decrypted: The UK Cyber Briefing / The PaperCut zero-day that skipped the login screen entirely
Transcript
- 0:03This is Decrypted. Friday, the twenty-eighth of August.
- 0:07The PaperCut zero-day that skipped the login screen entirely.
- 0:13PaperCut, the print management software that sits behind quota systems and shared printers in thousands of U
- 0:21K schools, universities, N H S trusts and councils, spent the last two days pushing emergency patches for a ze
- 0:29ro-day already being used against its customers.
- 0:32Two flaws, chained together, let an attacker with no credentials at all reach an administrative function and
- 0:41then hand the server code to run.
- 0:43PaperCut confirmed customer incidents, Huntress logged live intrusions within hours, and by the following day
- 0:51the vendor had shipped a second, hardened patch because the first one was not enough.
- 0:56If your organisation runs PaperCut N G or M F and exposes it to the internet, this is not a bulletin to file
- 1:05for Monday.
- 1:11The vulnerability that got attackers in is C V E twenty twenty-six, eight one five seven eight, an access co
- 1:21ntrol flaw in PaperCut's web management interface.
- 1:24According to Huntress's analysis, the flaw works by asking the server to render one page while quietly execut
- 1:33ing an action through a different, less-guarded component: think of it as showing a receptionist a visitor's b
- 1:40adge for the lobby while actually walking through the door marked "staff only", because the same badge check n
- 1:47ever runs on that door. No login required.
- 1:50Once inside, the second flaw, C V E twenty twenty-six, eight two zero seven eight, does the damage.
- 2:00It is an unsafe dynamic class loading bug in PaperCut's database connection utilities, which in plain terms m
- 2:08eans the server will take a piece of Java code handed to it and run it.
- 2:13Huntress's incident write-up shows attackers doing exactly that: reconnaissance commands such as whoami and t
- 2:21asklist, then hex-encoded Java classes dropped into PaperCut's own library folders, then logs quietly deleted
- 2:29to cover the tracks.
- 2:3810am A E S T on 28 August, then a "Release 2" the same day with extra hardening after working with Huntress an
- 2:47d watchTowr, and is telling customers to install it even if they already patched once.
- 2:52Anyone on an older, unsupported branch has no fix coming and should pull public internet access to the manage
- 3:00ment interface now.
- 3:03The Secure by Design lesson.
- 3:06The design failure here is a familiar one: an administrative interface that was reachable from the network a
- 3:13t all. Secure by Design does not mean "patch the access control bug quickly", it means the admin console shoul
- 3:21d never have been answering requests from an unauthenticated visitor in the first place, whatever the intended
- 3:27check was supposed to do. PaperCut's own guidance, to restrict the web interface to trusted I P addresses, is
- 3:35the right instinct, but it is also an admission that the product shipped without that boundary built in.
- 3:40For UK organisations, particularly the schools, universities and N H S trusts that make up a large share of
- 3:49PaperCut's customer base, the practical lesson is to stop treating print management as boring infrastructure t
- 3:56hat does not need the same network segmentation as anything else holding credentials and access to internal sy
- 4:02stems. An unauthenticated path to code execution on a server that talks to Active Directory is not a print pro
- 4:10blem, it is a domain problem.
- 4:12That was Decrypted. The written version and every source are linked in the show notes.
- 4:18Thanks for listening.