By Gregory Hale
Operational technology (OT) will feel the effects of the Apache Log4j Zero Day vulnerability, but in this era of needing to know everything all at once, how much it will affect the industry and for how long, it may be too early to tell.
There is no doubt the 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 because, quite simply, it is easy to exploit.
There is a fix available by upgrading to Apache Log4j 2.15.0 – and now Log4j 2.16.0. However, like what all companies in all industries went through back in the EternalBlue days when a patch was available to ward off attacks, converting that update to a working patch is not always easy to pull off.
EternalBlue was an exploit developed by the United States’ National Security Agency (NSA) for older Windows systems. Shadow Brokers got in and stole the code and leaked it and organizations that did not patch the exploit fell victim to attacks.
While this is inherent in the codes’ initial design, attackers are already starting to take advantage of opportunities.
Utility’s Duties
“Log4j’s job is to log things – a totally normal, and indeed necessary, task in any software system,” according to an advisory from aDolus. “And sensible developers the world over included Log4j in their software rather than recreating the wheel with a bespoke logging system. Its very utility is the reason Log4j is so widespread. Unfortunately, this vulnerability allows attackers to write malicious “messages” into a log that could then be used to actually execute code loaded from compromised LDAP servers.
“In a nutshell, 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,” the advisory said.
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 the payload.
Update the Update
While not as major as CVE-2021-44228, on Monday Apache released Log4j version 2.16.0 in a security update to address the CVE-2021-45046 vulnerability where a remote attacker can exploit this second Log4j vulnerability to cause a denial-of-service (DoS) condition in certain non-default configurations. Affected organizations that have already upgraded to Log4j 2.15.0 will need to upgrade to Log4j 2.16.0 to end up protected against CVE-2021-44228 and CVE-2021-45046.
Attacks are starting to take off and to help in that regard, the Cybersecurity and Infrastructure Security Agency (CISA), through the Joint Cyber Defense Collaborative, are tracking and responding to active, widespread exploitation of the critical remote code execution vulnerability. An unauthenticated remote actor could exploit this vulnerability to take control of an affected system.
In response, CISA has created a webpage, Apache Log4j Vulnerability Guidance and will actively maintain a community-sourced GitHub repository of publicly available information and vendor-supplied advisories regarding the Log4j vulnerability. CISA will continually update the webpage and the GitHub repository.
“One of the great things about having SBoMs (software bill of materials) for 40 million files is we can quickly search for Log4j in OT products,” said Eric Byres chief technology officer at software bill of materials provider aDolus Technology Inc. “And we are finding lots of Log4j in OT software (wherever we see Java) – some OEMs only have a few affected products, and some have a lot. Because of the way Log4j is compiled into shipping products, this will be a real challenge for asset owners to address and will likely affect OT for years.”
“One of the problems with this vulnerability is that Log4j is a library that is used in numerous software applications, not a ‘stand-alone’ application,” said Mark Carrigan, senior vice president at Hexagon PPM. “This means that we cannot rely upon a typical inventory or discovery technology to determine if the vulnerability exists on an OT network. The library could be referenced in a vendor’s compiled code – we will have to wait for the vendors to publish any instances where the library is used within one or more of their products, then go determine if those products are on the OT network. Cisco has already reported this vulnerability on some of their assets and I expect many more to be reported soon.
“Probably the biggest concern is that some automation vendors use java extensively, which means that Log4j could be within their systems. We will have to wait until they start reporting to see if it is an issue. (Siemens issued an Apache update earlier this week as did Schneider Electric.)
“There is talk within the industry to start reporting a software manifest or software bill of materials (SBoM) that would contain the sub-components embedded within their applications. Until such reporting becomes uniform, we will have to wait on vendors to research and report when a library vulnerability is reported.
“Ultimately this is further evidence that supply chain remains a key cyber risk and the industry has a lot of work ahead to address this issue,” Carrigan said.
Need to Take Action
“Just as we warned, Log4Shell is unleashing holy hell on businesses everywhere. And the worst is yet to come if organizations don’t take immediate action,” said Amit Yoran, chairman and chief executive at Tenable.
“Researchers are already observing ransomware activities as cybercriminals begin utilizing Log4Shell in their playbooks. Let me be clear, these ransomware activities are not going to go away – they will only increase like wildfire thanks in part to this new, perfect payload in the form of Log4Shell. Organizations need to take swift and decisive action as Log4Shell can and will completely undermine your security program.
“No vendor’s product is a silver bullet to solve this problem. Eliminating the threat posed by Log4Shell requires hard work and time to understand this vulnerability and how it will morph and evolve over time to bypass protective measures,” Yoran said.
“Log4Shell, a critical vulnerability in Apache Log4j, shines a bright light on the risky practice of relying on open-source code libraries to build enterprise-scale applications,” said Glen Pendley, deputy CTO at Tenable. “Many organizations around the world rely on open-source libraries as a key element in their ability to bring applications to market quickly. Yet, these libraries often stop short of a security-first approach. This dependence on what is effectively a wild, wild west of code libraries will continue to leave organizations vulnerable until time and resources are invested to make them more secure.”
The idea if “my organization is vulnerable” does appear to be floating around the industry these days.
Hunting for Vulnerabilities
“Right now, every IT person in the world is trying to identify if their machines have vulnerable Log4j packages,” said Mike Wiacek, founder and chief executive of Stairwell. “Attackers are winning because combatting unexpected major vulnerabilities like Log4j takes an incredible amount of time – and time-to-patch – particularly in large enterprises. And time is often the determining factor for the amount of damage from a breach.
“To guard against Log4j, IT teams need to assess where they need to look for vulnerabilities, what machines need to be patched, and what software needs to be updated to protect against attackers. To minimize further damage while large-scale patching efforts are being made, we advise security organizations to explore platforms that allow them to rapidly search their enterprise assets for software that may include the vulnerable Log4j packages.
“One approach could include searching across file metadata such as file paths and file names or hashes. Another approach could include scanning enterprise file content with customized YARA rules to identify files and artifacts associated with log4j components. These types of searches can accelerate otherwise slow and laborious defensive processes and further help organizations assess where related software exists, where it is out of date, where it is vulnerable, and where to look for post-exploit activity should an attacker make a move before patching can occur,” Wiacek said.
Actions CISA urges critical infrastructure leaders to take include:
- Increase organizational vigilance by ensuring there are no gaps in Information Technology (IT)/Operational Technology (OT) security personnel coverage and staff provides continual monitoring for all types of anomalous behavior. Security coverage is particularly important during the winter holiday season when organizations typically have lower staffing.
- Prepare your organization for rapid response by adopting a state of heightened awareness.
- Ensure network defenders implement cybersecurity best practices. Enforce multi-factor authentication and strong passwords, install software updates (prioritizing known exploited vulnerabilities), and secure accounts and credentials.
- Stay informed about current cybersecurity threats and malicious techniques.

