Log4Shell exposes a library embedded almost everywhere
Large-scale supply chain: flaw in a shared component10 December 2021
A critical flaw in Apache Log4j, a Java logging library inside countless products, let attackers run code by getting a crafted string logged. Many organizations did not know they used it.
- Position
- An open-source library embedded deep in commercial and open-source software
- Reach
- Countless products; the US Cyber Safety Review Board called it an endemic vulnerability
What happened
On 10 December 2021 Apache disclosed CVE-2021-44228 in Log4j 2, a Java logging library: lookups in logged text let an attacker trigger remote code execution by getting a crafted string written to a log. The library sat inside a vast number of products, often several layers down, so many organizations did not know whether they were exposed. CISA set up a dedicated guidance page and a list of affected vendors. In July 2022 the US Cyber Safety Review Board called Log4j an endemic vulnerability that would remain in systems for years.
The ATG nexus
Log4Shell was a flaw, not a supply-chain compromise, and no one held the position maliciously. It belongs here because it measured the same thing a compromise exploits: free code underneath everything, maintained by a few people, invisible to the organizations that run it. When a patch exists, finding every copy is the hard part. For ATG there is no patch to find.
Limits of the comparison
This was a server-side vulnerability with a fix. The library is not part of what renders on the screen.
On this site
- Whitepaper, Chapter 9: Open Source and the Path to the Client Runtime
- Whitepaper, Chapter 14: Existing Defenses
- Concept: The Open-Source Open Door
- Concept: The Endemic Flaw
- Concept: The Cost of Free