CYBERSECURITYTRACKER
Permanent story citation

Detecting Exploitation of CVE-2021-44228 (Log4j2) with Elastic Security

This page keeps the story as Cybersecurity Tracker first published it. If the tracker later corrects it, the correction appears below the original and never replaces it.

Back to newsStory 5191

As cited

Copy frozen at (site build).

vulnerabilities

Detecting Exploitation of CVE-2021-44228 (Log4j2) with Elastic Security

No summary had been written when this copy was frozen.

First seen by Cybersecurity Tracker

Source attribution

Correction

Correction recorded as of .

vulnerabilities

Detecting Exploitation of CVE-2021-44228 (Log4j2) with Elastic Security

Elastic Security released detection rules and hunting queries to identify active exploitation of CVE-2021-44228 (Log4Shell), a critical remote code execution vulnerability in the Log4j2 logging framework affecting versions 2.0-beta9 through 2.14.1. The detections focus on identifying suspicious sequences of Java processes making outbound connections to LDAP, RMI, or DNS ports followed by shell command execution, as well as indicators of post-exploitation activity such as cryptocurrency mining and file downloads.

Why it matters: Organizations running Java applications with vulnerable Log4j2 versions need to deploy these detection rules immediately to identify active compromise in their environment before attackers establish persistence or exfiltrate data.

Source published
First seen by Cybersecurity Tracker

Source attribution

Correction

Correction recorded as of .

vulnerabilities

Detecting Exploitation of CVE-2021-44228 (Log4j2) with Elastic Security

Elastic Security released detection rules and hunting queries to identify active exploitation of CVE-2021-44228 (Log4Shell), a critical remote code execution vulnerability in the Log4j2 logging framework affecting versions 2.0-beta9 through 2.14.1. The detections focus on identifying suspicious sequences of Java processes making outbound connections to LDAP, RMI, or DNS ports followed by shell command execution, as well as indicators of post-exploitation activity such as cryptocurrency mining and file downloads.

Why it matters: Organizations running Java applications with vulnerable Log4j2 versions need to deploy these detection rules immediately to identify active compromise in their environment before attackers establish persistence or exfiltrate data.

VendorsMicrosoftAppleOracleGitHubCrowdStrikeElastic
Source published
First seen by Cybersecurity Tracker

Source attribution

Glossary