Latest / Decrypted: The UK Cyber Briefing / SolarWinds fixes a hard-coded key in its access rights tool
Transcript
- 0:03This is Decrypted. Monday, the twenty-first of September.
- 0:06SolarWinds fixes a hard-coded key in its access rights tool.
- 0:11On Thursday SolarWinds published a fix for a flaw in Access Rights Manager.
- 0:18That's its product for managing access rights across a company's systems.
- 0:22The flaw is a hard-coded static key, and it lets an unauthenticated attacker run code remotely.
- 0:30SolarWinds doesn't mention any exploitation, and I won't claim any.
- 0:35But a secret baked into software is one of the oldest design mistakes there is.
- 0:40And this one sits in a tool whose entire job is knowing where your permissions live.
- 0:45Next. What SolarWinds has said.
- 0:49The advisory covers C V E twenty twenty-six, two eight three two six.
- 0:56It's scored 8.8, High, on the C V S S scale.
- 1:01It affects Access Rights Manager 2026.
- 1:052 and every earlier release, and it's fixed in 2026.
- 1:102.1. The weakness is classed as C W E-321, use of a hard-coded cryptographic key.
- 1:19SolarWinds credited Kai Huang of Armadin with reporting it.
- 1:24The Hacker News covered it on Saturday, and notes that the advisory says nothing about attacks in the wild.
- 1:31SolarWinds hasn't published how the key is used.
- 1:35So I won't guess at the exact route to code execution.
- 1:38What matters is the shape of the mistake.
- 1:41And also. One key for every door.
- 1:44Imagine a hotel chain that cuts a single master key, builds it into the lock design, and ships identical loc
- 1:52ks to every branch. Nobody needs to pick anything.
- 1:56Anyone who gets hold of one lock, or its drawings, holds the key to all the others.
- 2:02A hard-coded key works the same way.
- 2:05It's the same secret inside every installation.
- 2:08So it stays secret only until someone takes one copy of the software apart.
- 2:13After that, it belongs to whoever looked.
- 2:16The customer has no obvious way to change it, which is presumably why SolarWinds' fix is a new version rather
- 2:23than a setting.
- 2:25What a defender can do.
- 2:31So there's no run of failed passwords to alert on.
- 2:34What you can control is knowing where the product is, and who can reach it.
- 2:39As the name suggests, Access Rights Manager is built to manage access rights.
- 2:45So my inference is that a server running it is well connected to the systems whose permissions it tracks.
- 2:51That makes it a poor place to be surprised.
- 2:54First, find every installation, including forgotten test ones, and upgrade to 2026.
- 3:012.1.
- 3:09y need it.
- 3:15And finally. The Secure by Design lesson.
- 3:18The N C S C's Software Security Code of Practice implementation guidance is blunt.
- 3:24"You should avoid hard-coded credentials in your software.
- 3:28" It also asks vendors to identify every credential that would cause harm in the wrong hands, naming passwords
- 3:35, certificates and A P I keys.
- 3:38The Code, produced by D S I T and the N C S C, is voluntary.
- 3:43The design decision that prevents this flaw is dull.
- 3:46Generate a unique secret when each installation is set up, or keep it in a proper secret store, instead of co
- 3:53mpiling one into the product.
- 3:54The cost is some engineering work for the vendor, once.
- 3:58The cost of skipping it is paid by every customer at the same moment, the day someone extracts the key.
- 4:04For UK buyers, that turns into a procurement question rather than a technical one.
- 4:09Ask suppliers, especially those whose tools hold privileged access to your directories, to show how they meet
- 4:17the Code and how their product handles keys.
- 4:20A vendor that can't answer in a paragraph has told you something useful.
- 4:24Buying software that manages access to everything else means your control over your own systems depends on de
- 4:31cisions made in someone else's build process.
- 4:34You're entitled to ask to see them.
- 4:36That was Decrypted. The written version and every source are linked in the show notes.
- 4:42Thanks for listening.