The boss asked: "Are we affected?" The answer took three weeks.
How one flaw in a shared encryption library left companies unable to answer the simplest question, and what the CRA now asks of every manufacturer.
The facts
What happened
A flaw in OpenSSL, the encryption library inside a huge share of servers and devices, was disclosed as CVE-2014-0160. It let attackers read memory from affected systems, potentially including private keys and passwords.
What it caused
Companies spent weeks working out which of their own products contained the affected OpenSSL versions, while customers waited for an answer to one simple question: are we affected?
What the CRA now asks
Identify and document components, including a software bill of materials (Annex I, Part II (1)); remediate vulnerabilities without delay (Annex I, Part II (2)); no known exploitable vulnerabilities when placed on the market (Annex I, Part I (2)(a)).
Source: NIST National Vulnerability Database, CVE-2014-0160
The story
Mette had promised her daughter she would be at the school play that Thursday. The ticket was already in her coat pocket when a colleague sent her a link with no message, just "??". Someone had found a hidden weakness in a piece of free software that a huge share of the world's websites and gadgets use to keep information secret. It was like discovering that millions of sealed envelopes had a crack in them: anyone who knew where to look could read passwords and secret keys.
Then Henrik, the boss, appeared in her doorway with his jacket still on. "Are we in this?" Mette opened her mouth to say no, and then she closed it, because the honest answer was that she did not know. Their products were built from hundreds of ready-made parts, and nobody had ever written down which ones. So she started searching: old folders, old notes, an email to a former colleague who never replied. The phones rang. Customers wanted answers. And somewhere out there, people who had read the same news were already prying at the cracked envelopes, and they did not need weeks.
Mette missed the play. The weakness was not her fault, but not knowing was a choice her company had made years earlier without ever noticing. The Cyber Resilience Act takes that choice away. Every product must come with a list of what is inside it, like the ingredients label on a food packet, and a computer checks that list against the news every day. Henrik gets his answer in minutes. Mette makes the play.
The people and scenes are illustrative. The incident and its facts are real.
The system that would have caught it
1. Know what's inside
A list of every software part inside your product, made automatically each time you build a new version. It is called an SBOM (software bill of materials).
How the system worksCould you do this today?
Can anyone list what is in your latest release within an hour, without asking a developer?
If it applies, how ready are we?
Six yes-or-no questions, two minutes. Your no's come back in the order to fix them.
Not sure the CRA applies to your product? Check that first