CVE-2025-12480 Google Chronicle · YARA-L

Detect Gladinet Triofox Improper Access Control Exploitation Detected in Google Chronicle

Detects exploitation attempts targeting CVE-2025-12480, an improper access control vulnerability (CWE-284) in Gladinet Triofox. This vulnerability allows attackers to bypass access controls, potentially gaining unauthorized access to file storage and collaboration resources. Listed as a CISA Known Exploited Vulnerability, active exploitation has been observed in the wild.

MITRE ATT&CK

Tactic
Initial Access Persistence Credential Access

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule CVE_2025_12480_Triofox_Access_Control_Bypass {
  meta:
    author = "Detection Engineering"
    description = "Detects CVE-2025-12480 exploitation targeting Gladinet Triofox improper access control"
    severity = "CRITICAL"
    priority = "HIGH"
    cve = "CVE-2025-12480"
    reference = "https://nvd.nist.gov/vuln/detail/CVE-2025-12480"

  events:
    $http.metadata.event_type = "NETWORK_HTTP"
    $http.principal.ip = $src_ip
    (
      re.regex($http.target.url, `(?i)(/api/|/admin|/user/login|/token|/share|/fileupload|/download)`) or
      re.regex($http.target.application, `(?i)(triofox|centrestack|gladinet)`)
    )
    $http.network.http.response_code in (200, 201, 403)

  match:
    $src_ip over 5m

  condition:
    #http > 20 or
    (
      re.regex($http.target.url, `(?i)/admin`) and
      $http.network.http.response_code = 200
    )

  outcome:
    $risk_score = max(if(#http > 100, 95, if(#http > 50, 75, 55)))
    $event_count = count_distinct($http.metadata.id)
}
critical severity medium confidence

Chronicle YARA-L 2.0 rule detecting CVE-2025-12480 exploitation by identifying high-frequency HTTP requests or successful responses to Triofox administrative endpoints from individual source IPs within a 5-minute window.

Data Sources

Chronicle UDMGoogle Cloud ArmorWeb Application Firewall Logs

Required Tables

network_httpudm_events

False Positives & Tuning

  • Triofox desktop sync clients generating high request volumes during initial large sync operations
  • Authorized API integrations accessing Triofox admin endpoints from known service IPs
  • Security scanning tools performing authorized assessments of Triofox infrastructure
  • CDN or reverse proxy health checks accessing Triofox backend endpoints

Other platforms for CVE-2025-12480


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.

  1. Test 1Triofox Unauthenticated Admin Endpoint Probe

    Expected signal: IIS access log entries showing GET requests to /api/user/list, /admin/dashboard, /admin/users, /token, /api/settings from the test machine IP without authentication headers. Windows Security Event ID 4625 may appear if the application logs failed authentication attempts.

  2. Test 2Triofox Token Endpoint Brute Force Simulation

    Expected signal: IIS log entries showing 30 POST requests to /token from the test IP within seconds, with HTTP 401 or 200 response codes. Application-level Triofox logs may record authentication attempts.

  3. Test 3Triofox File Access Path Traversal Probe

    Expected signal: Windows Security event logs and IIS access logs recording HTTP GET requests to file-related Triofox endpoints without valid session tokens. Network telemetry in CrowdStrike or EDR showing outbound HTTP connections from the test machine to the Triofox server.

Unlock Pro Content

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

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections