Detect Gladinet CentreStack and Triofox Hard-Coded Cryptographic Key Exploitation in Microsoft Sentinel
Detects exploitation of CVE-2025-14611, a hard-coded cryptographic key vulnerability (CWE-798) in Gladinet CentreStack and Triofox. Attackers who obtain the static machineKey or cryptographic seed can forge ASP.NET ViewState tokens or authentication artifacts, enabling remote code execution via deserialization attacks without valid credentials. This vulnerability is actively exploited and listed on CISA KEV.
MITRE ATT&CK
- Tactic
- Initial Access Execution Persistence
KQL Detection Query
let GladinetPaths = dynamic(['/portal/', '/api/', '/fileserver/', '/triofox/', '/centrestack/']);
let SuspiciousPostPatterns = dynamic(['__VIEWSTATE', 'ScriptManager', 'ToolkitScriptManager']);
let timeWindow = 1h;
union DeviceNetworkEvents, W3CIISLog
| where TimeGenerated > ago(timeWindow)
| where RequestMethod =~ 'POST'
| where csUriStem has_any (GladinetPaths)
| extend RequestBodyIndicator = extract(@'(__VIEWSTATE|ScriptManager)=[A-Za-z0-9+/]{200,}={0,2}', 0, csUriQuery)
| where isnotempty(RequestBodyIndicator) or sc_status in (500, 200)
| project TimeGenerated, ComputerName, cIP, csUriStem, csMethod = RequestMethod, sc_status, cs_User_Agent = UserAgent, RequestBodyIndicator
| join kind=leftouter (
SecurityEvent
| where TimeGenerated > ago(timeWindow)
| where EventID in (4688, 4624)
| where ProcessName has_any ('w3wp', 'IIS', 'cmd', 'powershell', 'wscript')
| project TimeGenerated, Computer, Account, ProcessName, CommandLine
) on $left.ComputerName == $right.Computer
| where isnotempty(ProcessName) or sc_status == 500
| summarize count(), make_set(cIP), make_set(csUriStem), make_set(ProcessName) by bin(TimeGenerated, 5m), ComputerName
| where count_ > 2Detects suspicious POST requests to Gladinet CentreStack or Triofox endpoints involving large ViewState payloads, combined with IIS worker process anomalies indicative of ViewState deserialization exploitation leveraging a hard-coded machineKey.
Data Sources
Required Tables
False Positives & Tuning
- Legitimate large file upload operations through the CentreStack portal generating oversized POST bodies
- Automated backup or sync agents making frequent POST requests to the file server API
- Vulnerability scanners or penetration testing tools probing the web application endpoints
- Load balancer health checks generating repeated requests to portal paths
Other platforms for CVE-2025-14611
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.
- Test 1Simulate Forged ASP.NET ViewState Payload Submission to CentreStack Endpoint
Expected signal: IIS access log entry showing POST to /portal/default.aspx with large cs-uri-query value; HTTP response code 500 if payload is malformed, 200 if bypassed; network events capturing the inbound connection
- Test 2IIS Worker Process Child Shell Spawn Simulation (Lab)
Expected signal: Windows Security Event ID 4688 for cmd.exe process creation; EDR process telemetry showing PowerShell spawning cmd.exe; file creation event for exploit_sim_output.txt in C:\Temp
- Test 3CentreStack web.config Hard-Coded MachineKey Inspection
Expected signal: File read event on web.config via Sysmon Event ID 11/4663; PowerShell script block logging capturing the content search pattern; output file creation at C:\Temp\machinekey_audit.txt
- Test 4Forged Authentication Token Submission via Hardcoded Key (Lab Only)
Expected signal: IIS access log showing GET request with .ASPXAUTH cookie header; Windows authentication event logs (Event ID 4624/4625) recording the authentication attempt; network events capturing the connection from the test host
Unlock Pro Content
Get the full detection package for CVE-2025-14611 including response playbook, investigation guide, and atomic red team tests.