heroui logo

Java Base64 Decoder Argument Exceptions

Splunk Security Content

View Source
Summary
An anomaly detection rule that correlates Java HotSpot log activity to identify potential Base64 decoder usage paired with argument exceptions within the same JVM process over a one-minute window. It ingests two data sources (Java HotSpot Exceptions and Java HotSpot JIT) and extracts per-event context (time, process ID, and message). The rule flags events containing Base64 decoder references (e.g., java.util.Base64, Base64$Decoder) and events containing argument-related errors (e.g., IllegalArgumentException, "Input byte array has wrong"). If both evidence types occur within the same JVM and within a one-minute span, the rule emits a finding with a reason such as “Base64 decoder reference,” “Argument exception,” or “JIT activity.” The JIT context is optional but can add corroborating detail when present. Importantly, logs indicating these patterns do not prove native overwriting or code execution; the rule is an anomaly signal intended to prompt deeper investigation, particularly in the context of Java4Shell-like activity (CVE-2026-114938). The detection is scoped to endpoint-hosted JVM processes and correlates data to a single host and process_id, providing first/last event times and the associated messages for investigation.
Categories
  • Endpoint
Data Sources
  • Windows Registry
  • Script
  • Image
  • Process
  • File
  • Logon Session
  • Application Log
  • Service
  • Driver
  • Kernel
ATT&CK Techniques
  • T1190
Created: 2026-11-19