CVE-2025-58360 Google Chronicle · YARA-L

Detect OSGeo GeoServer XXE Injection Exploitation Attempt in Google Chronicle

Detects exploitation attempts targeting CVE-2025-58360, an Improper Restriction of XML External Entity (XXE) Reference vulnerability in OSGeo GeoServer. Attackers can submit malicious XML payloads to GeoServer endpoints to perform server-side request forgery, read local files, or exfiltrate data via out-of-band DNS/HTTP channels. This CVE is listed on CISA's Known Exploited Vulnerabilities catalog.

MITRE ATT&CK

Tactic
Initial Access Credential Access Collection

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule geoserver_xxe_injection_cve_2025_58360 {
  meta:
    author = "df00tech"
    description = "Detects XXE injection attempts against OSGeo GeoServer endpoints (CVE-2025-58360)"
    severity = "CRITICAL"
    priority = "HIGH"
    reference = "https://github.com/geoserver/geoserver/security/advisories/GHSA-fjf5-xgmq-5525"
    mitre_attack = "T1190, T1083, T1048"

  events:
    $http.metadata.event_type = "NETWORK_HTTP"
    $http.network.http.method = /POST|PUT/
    $http.network.http.url = /\/geoserver\/(wfs|wcs|wms|ows|web)/
    (
      $http.network.http.request_body = /<!ENTITY/
      or $http.network.http.request_body = /SYSTEM\s+["']/
      or $http.network.http.request_body = /<!DOCTYPE/
      or $http.network.http.request_body = /file:\/\//
      or $http.network.http.request_body = /jar:\/\//
      or $http.network.http.request_body = /netdoc:\/\//
      or $http.network.http.request_body = /gopher:\/\//
    )

  condition:
    $http
}
critical severity high confidence

Chronicle YARA-L rule detecting HTTP POST/PUT requests to GeoServer OGC service paths containing XXE injection markers in the request body.

Data Sources

Chronicle UDM HTTP EventsWeb Proxy Logs ingested to ChronicleWAF Events

Required Tables

network.http

False Positives & Tuning

  • GeoServer clients using WFS-T that include XML declarations for namespace or schema references
  • Authorized GIS platform integrations that submit complex XML payloads with entity references
  • Security scanning tools performing authorized assessments of GeoServer deployments

Other platforms for CVE-2025-58360


Testing Methodology

Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1GeoServer XXE File Disclosure via WFS Request

    Expected signal: Web server access log entry showing POST to /geoserver/wfs with 400/500 HTTP response status; GeoServer application log entry with SAXParseException or EntityException referencing file:///etc/passwd; network packet capture showing the XML payload in request body.

  2. Test 2GeoServer XXE SSRF to Cloud Metadata Endpoint

    Expected signal: Outbound HTTP GET request from the GeoServer host to 169.254.169.254 visible in network flow logs or host-based network monitoring; web server log showing POST to /geoserver/wcs with the XXE payload.

  3. Test 3GeoServer Blind XXE Out-of-Band DNS Exfiltration

    Expected signal: Outbound DNS resolution and HTTP GET request from GeoServer host to ATTACKER_DOMAIN visible in DNS logs and network flow telemetry; GeoServer application log may show entity resolution attempts or DTD fetch errors.

  4. Test 4GeoServer XXE via WMS GetMap Request with Malicious SLD

    Expected signal: Web server access log showing GET to /geoserver/wms with SLD_BODY parameter containing DOCTYPE and ENTITY declarations; GeoServer log showing SLD parsing error with reference to file:///etc/hostname.

Unlock Pro Content

Get the full detection package for CVE-2025-58360 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections