Detect Gogs Path Traversal Vulnerability (CVE-2025-8110) in Sumo Logic CSE
Detects exploitation attempts targeting CVE-2025-8110, a path traversal vulnerability (CWE-22) in Gogs self-hosted Git service. Attackers can craft malicious HTTP requests containing directory traversal sequences to read arbitrary files outside the intended web root, potentially exposing sensitive configuration files, SSH keys, or repository data. This vulnerability is listed in the CISA KEV catalog indicating active exploitation in the wild.
MITRE ATT&CK
Sumo Detection Query
_sourceCategory=web* OR _sourceCategory=proxy* OR _sourceCategory=nginx* OR _sourceCategory=apache*
| parse regex "(?<src_ip>\\d{1,3}\\.\\d{1,3}\\.\\d{1,3}\\.\\d{1,3}).*?\"(?<http_method>\\w+) (?<request_uri>\\S+)"
| where request_uri matches /(\.\.\/|%2e%2e%2f|%2e%2e\/|\.%2e\/|%252e%252e|%2e%2e%5c)/
| where request_uri matches /(app\.ini|\/etc\/passwd|\/etc\/shadow|id_rsa|\.ssh\/|conf\/app\.ini)/
| urldecode request_uri as decoded_uri
| count as request_count by src_ip, request_uri, decoded_uri, http_method
| where request_count >= 1
| sort by request_count desc
| fields src_ip, request_uri, decoded_uri, http_method, request_countSumo Logic query parsing web access logs for path traversal sequences in HTTP request URIs with targeting indicators specific to Gogs sensitive files, with URL decoding to expose obfuscated payloads.
Data Sources
Required Tables
False Positives & Tuning
- Penetration testing tools performing automated path traversal checks against Gogs
- Monitoring agents that use URL-encoded paths when querying Gogs API endpoints
- Third-party integrations with non-standard path encoding behaviors
- Sumo Logic source category mismatches causing unrelated log data to be parsed
Other platforms for CVE-2025-8110
Testing Methodology
Validate this detection against 3 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.
- Test 1Basic Gogs Path Traversal - Read app.ini
Expected signal: HTTP GET requests to Gogs port (3000) with ../ and %2e%2e sequences in URI visible in access logs; 200 response with app.ini content if vulnerable, 400/403/404 if patched or WAF blocks
- Test 2Gogs Path Traversal - SSH Key Extraction
Expected signal: HTTP requests with mixed encoding traversal patterns (%2f for /) targeting .ssh and id_rsa paths; response codes and body sizes indicate exploitation success or failure
- Test 3Automated Gogs Traversal Scan with Multiple Encoding Variants
Expected signal: Burst of HTTP requests from single source IP within seconds, each containing different encoding variants of traversal sequences; some requests may return 200 with file content if instance is vulnerable
Unlock Pro Content
Get the full detection package for CVE-2025-8110 including response playbook, investigation guide, and atomic red team tests.