We have not been able to test, simulate or build datasets for it, use at your own risk!

Try in Splunk Security Cloud


This search looks for specific GET or HEAD requests to web servers that are indicative of reconnaissance attempts to identify vulnerable JBoss servers. JexBoss is described as the exploit tool of choice for this malicious activity.

  • Type: TTP
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
  • Datamodel: Web
  • Last Updated: 2017-09-23
  • Author: Bhavin Patel, Splunk
  • ID: 104658f4-afdc-499e-9719-17243f982681


ID Technique Tactic
T1082 System Information Discovery Discovery

| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime from datamodel=Web where (Web.http_method="GET" OR Web.http_method="HEAD") AND (Web.url="*/web-console/ServerInfo.jsp*" OR Web.url="*web-console*" OR Web.url="*jmx-console*" OR Web.url = "*invoker*") by Web.http_method, Web.url, Web.src, Web.dest 
| `drop_dm_object_name("Web")` 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `detect_attackers_scanning_for_vulnerable_jboss_servers_filter`

Associated Analytic Story

How To Implement

You must be ingesting data from the web server or network traffic that contains web specific information, and populating the Web data model.

Required field

  • _time
  • Web.http_method
  • Web.url
  • Web.src
  • Web.dest

Kill Chain Phase

  • Reconnaissance

Known False Positives

It's possible for legitimate HTTP requests to be made to URLs containing the suspicious paths.


Test Dataset

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

source | version: 1