Skip to content
BENIBIX Learn

Log4Shell

Development🔐 SecuritySecurity Basics

Also known as CVE-2021-44228, Log4j Vulnerability, Log4j RCE

A 2021 hole in Log4j, a Java tool for logs. One line of text could run code.

Think of it like

Think of it like a note pad that does what any note on it says.

Example

Jack's app logs each search. Under Log4Shell, one odd search string could have made his server fetch and run outside code. He updates Log4j to a fixed version that day.

Why it matters

One small tool, deep inside other software, put whole firms at risk at once.

Definition

Log4Shell was a hole in Log4j, a popular Java tool for writing logs. It became public in December 2021. If an app logged text a user sent, a special string in that text could make the server fetch and run code from far away. It scored 10 out of 10, the top score. The fix was simple: update Log4j. The hard part was finding every place it hid.
The first point is where Log4Shell sat for years, before anyone knew.

Common mistake

Checking only your own code. Log4j was often pulled in by another package, so teams had to scan every package they used.

Key takeaways

  1. 1
    Logs were the door. Logged text could start remote code.
  2. 2
    Top score. It scored 10 out of 10.
  3. 3
    Hidden deep. Often inside other packages, never chosen directly.