By Gregory Hale
When a vulnerability ends up released it is usually a simple thing of here is the issue and here is what product it is in. But when it comes to the Apache Log4j, you are talking about how many hundreds if not thousands of products this code is within – and that includes operational technology (OT) along with information technology.
“Everyone is learning that is a more serious issue for OT than initially thought, especially if you are a supplier or user of ICS equipment,” said Eric Byres, chief technical officer at software bill of materials (SBoM) provider aDolus. “There is probably not a single OT vendor that doesn’t have Log4j software somewhere in their product line. Plus, this can be a trivial exploit, so the hackers are loving it.”
Apache Log4j software library versions 2.0-beta9 to 2.14.1 Zero Day is a critical vulnerability affecting a wide range of systems and users. There was a fix available by upgrading to Apache Log4j 2.15.0 – and now there is another upgrade, Log4j 2.16.0.
The Log4j vulnerability (called Log4Shell which is CVE-2021-44228) is a result of overly provisioned features that were enabled by default, an insecure default configuration, and the implicit trust of messages. Log4j utility had message lookup substitution enabled by default. As a result, attackers can craft a special request that could make the utility remotely download and execute a payload.
Before anyone overreacts, all is not lost.
“On the other hand, just because Log4j exists in a product doesn’t mean the product is exploitable,” Byres said, who added some typical reasons for that include:
- The software includes Log4j but not the vulnerable version 2
- The software does not allow any exploiter input to be included in logs (e.g.Log4j is just used for installation with all installation input from developer-created files.
- The software “sanitizes” all input before it is provided to log4j
“Exploitability matters. As Patrick Coyle noted today, ‘if you have taken the system down to ‘fix’ a device that was not really affected by Log4Shell, the cost would have come without any benefit.’ Considering just how widespread Log4j is, this could result in hundreds of millions of dollars of wasted effort and industrial downtime across the world,” Byres said.
Byres feels there is an answer to issues such as this.
“I think the Vulnerability Exploitability eXchange (VEX) standard is so critical. It lets OT suppliers inform their end-users of what is exploitable (or not) so the end-users can focus on what really matters, namely reducing risk to their operations.”
Now that Log4j has been out for a while, industry watchers want to know if this is similar to any other incidents or attacks in the past. But Byres said this is unique unto itself.
“Some people have been comparing Log4j to SolarWinds, but the two events are not really comparable. SolarWinds was an extremely deliberate and sophisticated attack, while Log4j is an extremely widespread vulnerability.
“Now, they may be compatible when we consider long-term impact. The Log4j issue is far less sophisticated and is more of a commodity attack opportunity, which is good because it’s not as stealthy (i.e. it wasn’t hidden into a vendor’s legitimate product pipeline). The bad news is Log4j exploit is easy to execute, so many more threat actors will take advantage of it. The other bad news is the Log4j exploit will invisibly live on within many OT products and many of those products will go without fixes until they are retired.”
While a fix is available, Byres said a patch can’t undo an already compromised host.
“Patches to software containing Log4j don’t completely address the risk. They may remove the attack vector, provided that a company hasn’t already been compromised, but many companies are not in a position to know if they were compromised.
“Log4j vulnerability highlights the challenge of third-party risk management that the industry is facing today,” Byres said. “Asset owners and governments will certainly demand more visibility into what exactly they are buying when they purchase a software or hardware ‘solution.’ Suppliers will be scrambling to provide this information.”

