heroui logo

Java HotSpot Fatal Error Log Created

Elastic Detection Rules

View Source
Summary
This rule detects the creation of HotSpot fatal error logs (hs_err_pid*.log) generated by a Java Virtual Machine after a fatal error (e.g., segmentation fault, access violation, or unrecoverable native-code failure). Such logs commonly record signals, problematic frames, JVM/OS versions, command lines, loaded native libraries, thread state, and memory details. In the context of Java4Shell (CVE-2026-114938), heap grooming or memory-corruption attempts could crash the JVM prior to remote code execution, so this artifact may indicate an exploit attempt rather than confirmed exploitation. The rule focuses on ECS-compatible file creation events tied to Java processes to signal a potential crash and possible exploitation activity, not proof of successful compromise. Triage and analysis guidance (high level): inspect the target process and file metadata (path, name, process name, PID, user/host), preserve the complete hs_err_pid*.log, and extract relevant details (signal/exception, problematic frame, loaded native libraries, VM flags, and stack). correlate the crash with the responsible Java application and its exposure to untrusted data. for potential Java4Shell activity, verify OpenJDK runtimes on x86-64 with AVX-512 and review for signs of repeated decoder warm-up, malformed Base64 data, or unusual request patterns preceding the crash. review pre-crash network and proxy telemetry, and search for additional hs_err_pid*.log files across hosts to identify crash patterns that may indicate exploitation attempts. False positives may arise from benign JVM defects, incompatible JNI libraries, Java agents or profilers, faulty native modules, hardware issues, or resource exhaustion. Avoid treating any single hs_err_pid*.log occurrence as definitive exploitation. Remediation and response: preserve relevant logs and telemetry, isolate the host if exploitation cannot be ruled out, and upgrade affected Java runtimes per vendor guidance. Mitigations for Java4Shell include disabling BASE64 intrinsics or restricting AVX usage where appropriate. extend this search to peer systems to identify similar crashes and potential follow-on activity (shells, outbound connections, payloads, credential access).
Categories
  • Endpoint
  • Windows
  • Linux
  • macOS
Data Sources
  • File
  • Process
ATT&CK Techniques
  • T1190
  • T1203
  • T1499
  • T1499.004
Created: 2026-11-18