Configuration Scanners Adding Java Specific Configuration Files, (Mon, Jun 24th)

Category :

SANS Full Feed

Posted On :

Hunting for configuration files is one of the favorite tricks we typically see used against our honeypots. Traditionally, standard and more generic configuration files like “.env” or “.config” are the target, with some cloud-specific configuration files sprinkled in.

Today, I noticed in our “First Seen URL” list a new variation that appears to target Java Spring configuration files. For example, the following files are now being hunted:


One particular active source of these scans is %%ip: This IP address, associated with Tencent’s cloud data centers, started scanning for configuration files a couple of days ago and uses a very exhaustive list. For example, see Sunday’s data:

These lists should be included in vulnerability scanners to proactively scan for any of these URLs in case they are accidentally exposed.

More details about the Spring YAML configuration files can be found here. The file often includes the names of servers in different environments (development vs. production) and may sometimes include usernames and passwords. Oddly, for “application-core.yml”, Google only finds one example exposed. But typically, Google would not find these files as they are not exposed via links. An accidentally exposed directory index is the most likely issue that would expose these files to search engines like Google.

Johannes B. Ullrich, Ph.D. , Dean of Research,

(c) SANS Internet Storm Center. Creative Commons Attribution-Noncommercial 3.0 United States License.