Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
16 detections
Filters
Last updated
All Time
Detection languages
12
2
1
1
Contributors
5
4
2
2
1
Categories
5
5
5
3
3
Platforms
13
11
4
Products / Services
6
6
1
1
MITRE Techniques
6
5
5
4
4
CVEs
71
71
64
58
49
16
KQL Query from file: Java4Shell Hunting
Detects servers running vulnerable Java versions (JDK/JRE) with indicators of internet exposure, inbound connections, or active scanning, prioritizing risk levels for potential Java4Shell exploitation.
Detects a Java process on Linux spawning a shell with inline download, reverse-shell or decoding commands, or spawning curl, wget, nc, ncat or socat directly. Java4Shell (CVE-2026-114938) is a memory corruption in the OpenJDK AVX-512 Base64 decoder that Calif weaponized into pre-auth and post-auth RCE in Keycloak, Jira, Confluence, Artifactory, Jenkins, PingFederate, Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. The product-specific exploit chains are withheld, so this rule keys on the post-exploitation behaviour (a JVM child process) and not on the trigger. It is generic and will also fire on any other JVM RCE.
Detects java.exe or javaw.exe on Windows spawning a script host or download LOLBin directly, or spawning cmd.exe with download or discovery commands. Java4Shell (CVE-2026-114938) gives an unauthenticated remote attacker heap corruption in the OpenJDK AVX-512 Base64 decoder and Calif reached RCE in widely deployed Java products. Weaponized chains are not public, so this rule keys on the post-exploitation child process. Windows hosts need an AVX-512 VBMI CPU (Intel Ice Lake or newer, AMD Zen 4 or newer) and an affected OpenJDK build to be exposed.
Detects Java processes spawning shells (sh, bash, cmd, powershell) or reconnaissance utilities (whoami, id, curl, wget), commonly associated with exploitation (such as Java4Shell / CVE-2026-114938), excluding known build tooling and routine host activity.
hunt: JVM crash logs from failed heap grooming, which is Upwind's published indicator. The query returns any JVM that crashed two or more times, and any crash of a product Calif showed was exploitable pre-auth.
Identifies servers running vulnerable or unknown versions of Java (JDK/JRE) with evidence of internet exposure, such as inbound public connections or internet scanning indicators, to prioritize patching for CVE-2026-114938.
A JVM directly runs a command with reverse-shell, download and execute, base64 to shell or encoded PowerShell syntax. This catches RCE that succeeds on the first attempt, without a crash.
Detects a Java service that is repeatedly relaunched on a host (consistent with JVM crashes from failed Java4Shell heap-corruption attempts), followed by the java process spawning a shell child, indicating successful pre-auth remote code execution.
This rule performs a hunting query for Java4Shell (CVE-2026-114938) by triaging Java versions from binary install paths and checking command-line flags for mitigation (such as -XX:-UseBASE64Intrinsics or -XX:UseAVX=2). It targets server and domain controller roles on Windows and Linux platforms.
Detection rule that sweeps across Microsoft Defender XDR sources (including TVM software inventory, vulnerabilities, process events, file events, image loads, and registry entries) to identify potentially vulnerable Java installations associated with CVE-2026-114938.
Detects potential post-exploitation or escalation activity (such as Java4Shell CVE-2026-114938) where a Java Virtual Machine (JVM) crash artifact (hs_err_pid) is generated, followed closely by the same Java process or process tree spawning a shell or interpreter.
Hunt: A JVM writes a JSP file (web shell) or writes to SSH, cron, systemd, ld.so.preload, rc.local, profile.d or the Windows Startup folder.
Detects potential exploitation attempts related to Java4Shell (CVE-2026-114938) by identifying processes querying /proc/cpuinfo for AVX-512 flags in conjunction with the execution of an unmitigated Java process lacking specific base64 or AVX mitigations within a specified time window.
Lists processes a JVM started on any host where a JVM crashed, from the first crash until 6 hours after the last one. This matches the crash-and-retry pattern before RCE succeeds. Shells are listed only when they run an inline or interactive command, so CI build steps that run script files are excluded.
Detects a burst of JVM crash logs (hs_err_pid) associated with Java processes on a host within a short window, compared against the host's 14-day historical baseline, which may indicate exploitation attempts or instability.