
Summary
This anomaly rule detects HTTP traffic that contains a malformed, padded Base64 sequence, which is a pattern associated with attempts to trigger a vulnerable Java Base64 decoder (Java4Shell). The rule parses Zeek HTTP logs (headers, POST body, and URI) to extract the potential request value and then applies a regex to identify a 64-character Base64 block followed by a short padding fragment (e.g., =, ==). If a match is found and the data is not truncated, it records metadata (source, destination, port, method, and the malformed payload) and aggregates findings by src/dest/dest_port/method. It references CVE-2026-114938 and MITRE technique T1190, situating the activity as a potential exploit against exposed services. The rule notes that presence of such data alone does not prove decoding occurred, and highlights the possibility of false positives from legitimate or unrelated encoded data. An intermediate finding format is included to help correlate occurrences to specific traffic paths. The analytic storyline ties to Java4Shell activity observed in HTTP traffic and is aligned with network-focused detections.
Categories
- Network
Data Sources
- Service
- Service
- Service
ATT&CK Techniques
- T1190
Created: 2026-11-19