Habr•July 28, 2026•🇷🇺Translated from Russian

SOC Incident Analysis Exposes Active Exploitation of CVE-2025-53770 SharePoint ToolShell Auth Bypass and RCE

SOC analysts have published a detailed incident report on Letsdefend SOC342, covering the exploitation of CVE-2025-53770 — a critical SharePoint ToolShell authentication bypass and remote code execution vulnerability.

The alert was generated by the rule “CVE-2025-53770 SharePoint ToolShell Auth Bypass and RCE” after detecting a suspicious unauthenticated POST request to ToolPane.aspx with an abnormally large Content-Length and a spoofed referer pointing to /layouts/SignOut.aspx. The request was allowed by the security control, indicating the payload reached the server.

Initial Triage and Vulnerability Confirmation

Analysts confirmed the server was likely vulnerable because the observed behavior matched public exploitation indicators published by CISA. The source IP 107.191.58.76 was already listed in the CISA advisory and scored malicious on VirusTotal (10/92 vendors).

Network logs showed the POST request successfully reached the SharePoint server. Subsequent process telemetry revealed w3wp.exe (the IIS worker process) spawning PowerShell with the flags -nop -w hidden -e, followed by Base64-decoded commands that dumped ASP.NET machine keys.

Post-Exploitation Activity

The extracted keys would allow an attacker to forge and sign ViewState payloads, achieving unauthenticated remote code execution. The same w3wp.exe process later launched csc.exe to compile C# source code dropped in C:\Windows\Temp\payload.cs.

Attackers also created a malicious file at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\TEMPLATE\LAYOUTS\spinstall0.aspx that used an ActiveX object (CLSID ADB880A6-D8FF-11CF-9377-00AA003B7A11) to execute or download additional payloads when a user visited the page.

  • Network IOC: 107.191.58.76 (C2 and payload hosting)
  • File hashes (SHA-256): 10e01ce96889c7b4366cfa1e7d99759e4e2b6e5dfe378087d9e836b7278abfb6 (machinekey.aspx), 92bb4ddb98eeaf11fc15bb32e71d0a63256a0ed826a03ba293ce3a8bf057a514 (spinstall0.aspx)
  • Process chain: w3wp.exe → powershell.exe → csc.exe → cmd.exe → powershell.exe

Containment Actions

After confirming compromise, the server was isolated. Recommended remediation steps include blocking the malicious IP, deleting the dropped files, adding the observed hashes to blocklists, patching SharePoint to a safe version, and rotating all ASP.NET cryptographic keys.

Related articles

Habr•Vulnerabilities & Exploits

Automating Asset Scanning in MaxPatrol VM via API: Part 4 on Authentication

A detailed technical guide explains how to build asset scanning automation in MaxPatrol VM using its API, starting with authentication methods. The author covers three authorization options including local account login-password, domain account credentials, and reference tokens, providing working Python examples for local accounts. Code reads secrets from an .env file and obtains a Bearer token valid for 24 hours from the Core role instance. The post details required privileges in both the Management Console and MaxPatrol 10 for tasks such as vulnerability exports, dynamic asset group management, scan task creation, and report exporting. It credits Alexey Leonov for an early GitHub script that enabled practical API usage and lists additional resources including webinars, SDK, CLI, Jira integration, and a Postman collection. All subsequent API calls rely on the generated headers containing the Bearer token.

Habr•Vulnerabilities & Exploits

Securing Hadoop Clusters: Removing Passwords from XML Configs with Credential Provider API and JCEKS

Hadoop configurations frequently expose sensitive credentials such as database passwords and cloud access keys in plain text within files like hive-site.xml and core-site.xml. The Credential Provider API, introduced in Hadoop 2.6, allows applications to retrieve secrets from an external JCEKS keystore instead of embedding them directly in XML. This mechanism uses conf.getPassword() to fetch decrypted values from the keystore when hadoop.security.credential.provider.path is configured. JCEKS relies on the outdated PBEWithMD5AndTripleDES algorithm, which remains vulnerable to Sweet32 attacks in theory though practical risk for small keystore files is low. Master password protection for the keystore itself is the weakest link, with options including environment variables, protected password files, or HDFS Transparent Data Encryption. Arenadata has automated credential encryption management in its ADH platform through ADCM to handle keystore creation, permission setting, and rotation across cluster nodes.

Security NEXT•Vulnerabilities & Exploits

CISA Adds Five Exploited Vulnerabilities to KEV Catalog Including AhsayCBS Authentication and Command Injection Flaws

The US Cybersecurity and Infrastructure Security Agency (CISA) has added five vulnerabilities to its Known Exploited Vulnerabilities catalog after confirming active exploitation in the wild. Four vulnerabilities were registered on October 14, 2026, and one additional entry followed on October 15. Among the newly listed issues are two critical flaws affecting the AhsayCBS backup management server: CVE-2026-105133, an authentication bypass in the API, and CVE-2026-105134, a command injection vulnerability in the replication feature. When chained together, the pair allows unauthenticated remote attackers to execute arbitrary operating system commands. Vendor Ahsay has released hotfixes in versions 10.3.4.45 and 9.15.2.70 because standard patches cannot fully address the issues. The advisory also references vulnerabilities in Atlassian products and multiple network security solutions from other vendors.

Security NEXT•Vulnerabilities & Exploits

Google Issues Chrome Security Update Fixing Critical Vulnerability Two Days After Previous Patch

Google has released a new set of security updates for its Chrome browser that address ten vulnerabilities, including one rated critical. The update arrives just two days after a larger patch that fixed 37 issues on October 13. The most severe flaw, tracked as CVE-2026-110922, is a use-after-free vulnerability in the Prerender feature that could allow remote code execution. The company released Chrome 155.0.8059.85 and 155.0.8059.84 for Windows and macOS, along with Chrome 155.0.8059.84 for Linux on October 15. The critical issue was reported by an external researcher on October 2. Deployment will occur gradually over the next several days to weeks.