Detectionhightest

Potential JNDI Injection Exploitation In JVM Based Application

Detects potential JNDI Injection exploitation. Often coupled with Log4Shell exploitation.

Convert In Phoenix Studio

Open this Sigma rule in the converter with the YAML preloaded and ready for backend selection.

Launch
Moti HarmatsCreated Sat Feb 11bb0e9cec-d4da-46f5-997f-22efc59f3dcaapplication
Log Source
jvmapplication
Productjvm← raw: jvm
Categoryapplication← raw: application

Definition

Requirements: application error logs must be collected (with LOG_LEVEL=ERROR and above)

Detection Logic
Detection Logic1 selector
detection:
    keywords:
        - 'com.sun.jndi.ldap.'
        - 'org.apache.logging.log4j.core.net.JndiManager'
    condition: keywords
False Positives

Application bugs

Rule Metadata
Rule ID
bb0e9cec-d4da-46f5-997f-22efc59f3dca
Status
test
Level
high
Type
Detection
Created
Sat Feb 11
Path
rules/application/jvm/java_jndi_injection_exploitation_attempt.yml
Raw Tags
attack.initial-accessattack.t1190
View on GitHub