1200kmSECURITY RESEARCH

1200KM / sigma-rule

Potential JNDI Injection Exploitation In JVM Based Application — Sigma Rule

Sigma rule bb0e9cec-d4da-46f5-997f-22efc59f3dca. Potential JNDI Injection Exploitation In JVM Based Application — Sigma Rule. Detects potential JNDI Injection exploitation. Often coupled with Log4Shell exploitation.

Rule metadata and linked tags

Author: Moti Harmats. Source status: test; severity: high. Source dates: 2023-02-11 / not supplied.

{
  "category": "application",
  "product": "jvm",
  "definition": "Requirements: application error logs must be collected (with LOG_LEVEL=ERROR and above)"
}

Pinned original Sigma rule · Detection Rule License 1.1

Source SHA-256: 2822600226dd20ad88d70b2f5f579dbf3bc10e52af475da944cebc864b727ba5

Detection logic

Original source YAML. Source-tag agreement is not proof of complete semantic coverage. This rule has not been compiled for a SIEM backend or validated against live telemetry here.

title: Potential JNDI Injection Exploitation In JVM Based Application
id: bb0e9cec-d4da-46f5-997f-22efc59f3dca
status: test
description: Detects potential JNDI Injection exploitation. Often coupled with Log4Shell exploitation.
references:
    - https://www.wix.engineering/post/threat-and-vulnerability-hunting-with-application-server-error-logs
    - https://secariolabs.com/research/analysing-and-reproducing-poc-for-log4j-2-15-0
author: Moti Harmats
date: 2023-02-11
tags:
    - attack.initial-access
    - attack.t1190
logsource:
    category: application
    product: jvm
    definition: 'Requirements: application error logs must be collected (with LOG_LEVEL=ERROR and above)'
detection:
    keywords:
        - 'com.sun.jndi.ldap.'
        - 'org.apache.logging.log4j.core.net.JndiManager'
    condition: keywords
falsepositives:
    - Application bugs
level: high

Original YAML and metadata in JSON

False positives

  • Application bugs

Source references

Connected ecosystem references

Exact source-tagged techniques

Telemetry review

Read the original logsource above, then inspect the linked detection workspaces for technique-level sensor context. No per-rule telemetry equivalence is inferred.

Pinned research references. No browser attack runner, live simulation result or validated detector is asserted. Source mappings and validation limits are preserved. ATT&CK / Atomic provenance · Detection provenance.