Log4j Scanner detected in user agent or referrer

Classification:

attack

Tactic:

TA0043-reconnaissance

Technique:

T1595-active-scanning

Esta página aún no está disponible en español. Estamos trabajando en su traducción.
Si tienes alguna pregunta o comentario sobre nuestro actual proyecto de traducción, no dudes en ponerte en contacto con nosotros.

Goal

This rule detects if your Apache or NGINX web servers are being scanned for the log4j vulnerability. The initial vulnerability was identified as CVE-2021-44228.

Strategy

This signal evaluated that jndi:(ldap OR rmi OR dns) has been detected in the HTTP header fields user agent and referrer or referer.

Triage and response

  1. Ensure you servers have the most recent version of log4j installed.
  2. Check if the Base64 was detected in an http.user_agent or http.referrer rule was also triggered and follow the Triage and response steps in that rule.

Note: Datadog’s The Monitor blog has an article published about “The Log4j Logshell vulnerability: Overview, detection, and remediation”.