Detect Gogs Path Traversal Vulnerability (CVE-2025-8110) in CrowdStrike LogScale
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
LogScale Detection Query
#event_simpleName=NetworkReceiveAccept OR #event_simpleName=NetworkConnectIP4
| ImageFileName=/gogs/i OR LocalPort IN (3000, 80, 443)
| join {
#event_simpleName=ProcessRollup2
| ImageFileName=/gogs/i
| fields aid, ContextProcessId, ImageFileName, CommandLine
} [aid, ContextProcessId]
| in(field="CommandLine", values=[".*/.*\\.\\./.*", ".*%2e%2e%2f.*", ".*%252e%252e.*"])
| stats count() AS connection_count, values(RemoteAddressIP4) AS remote_ips BY aid, ImageFileName, CommandLine
| where connection_count >= 1
| eval alert="Gogs Path Traversal Attempt CVE-2025-8110"CrowdStrike Falcon query correlating network connection events with Gogs process activity to detect path traversal exploitation at the endpoint level, focusing on Gogs server processes receiving connections with traversal patterns in associated command line context.
Data Sources
Required Tables
False Positives & Tuning
- Gogs processes handling legitimate repository paths that contain URL-encoded characters
- CrowdStrike sensor telemetry gaps causing partial event correlation mismatches
- Development or test Gogs instances accessed by automated integration testing frameworks
- Gogs administrative scripts that use path parameters containing dots in automation workflows
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.