Automating Asset Scanning in MaxPatrol VM via API: Part 4 on Authentication
A new technical guide from the Gazprom CPS blog details how to automate asset scanning in MaxPatrol VM through its API, beginning with the essential step of authentication.
The author notes that previous parts covered scanning of main asset types and that official documentation already addresses network equipment and virtualization. The focus now shifts to large-scale automation via API with practical Python examples.
Authorization Methods
API authorization in MaxPatrol VM supports three approaches: local account login and password, domain account login and password, and reference tokens for either local or domain accounts. The provided code examples use a local account because vendor documentation for versions newer than 2.7 was removed.
Required privileges are determined through testing. In the Management Console the minimum role is Management and Configuration: User to obtain the Bearer token. In MaxPatrol 10 a custom role must grant permissions for Assets (Vulnerabilities, Create/View/Modify/Delete, View), Extended permissions for report export, Tasks (Create/View/Modify/Delete, View), Profiles (View), and Infrastructure scope retrieval.
Obtaining the Bearer Token
All API requests require a Bearer token acquired via a POST request to the Core role endpoint. Credentials and the installation-specific ClientSecret are loaded from a non-committed .env file. The request uses grant_type password and scope mpx.api.
The response returns an access_token valid for 86400 seconds (24 hours), token_type Bearer, and the granted scopes. Once obtained, the token is placed into standard headers used for every subsequent call.
The author credits Alexey Leonov whose public GitHub script first demonstrated practical JSON export from MaxPatrol VM. Additional resources listed include a vendor webinar, SDK, CLI tool, Jira integration example, and Postman collection.
Related articles
Security Week 2644: Active Exploitation of PHP2Shell Vulnerabilities Confirmed
PHP developers released patches for two critical vulnerabilities collectively known as PHP2Shell on October 20, affecting PHP 8.2 through 8.5 as well as older branches. The flaws allow unauthenticated remote code execution on affected servers, which power approximately 70 percent of websites. Despite expectations of immediate exploitation, confirmed attacks with working exploits only began on October 25. CrowdStrike noted technical difficulties in weaponizing the issues in real-world environments. Only one-fifth of top Russian websites had applied the fixes by October 25. Additional incidents included compromised eMudhra certificates, a critical GitLab flaw, and a 16-year-old Broadcom router vulnerability.
Positive Technologies Offers Up to 500,000 Rubles for Bypassing PT Application Firewall
Positive Technologies has expanded its Standoff Bug Bounty program to include rewards for bypassing its web application firewalls. Researchers can earn between 150,000 and 500,000 rubles for demonstrating practical bypasses against PT Application Firewall PRO and PT Application Firewall Cloud. The program targets the core protective mechanisms, including traffic filtering, attack detection rules, and the management layer used by administrators. Submissions must include reproducible attack scenarios that show how malicious requests can pass through undetected, rather than relying on scanner reports or theoretical findings. Reward amounts vary by severity and confirmed business impact, with critical issues in the PRO version paying up to 500,000 rubles. The company plans to use validated findings to strengthen detection rules and improve overall product resilience.
Tailscale SSH Vulnerability Allows Root Access via Unix Socket Redirection
A researcher identified flaws in Tailscale that let an attacker with existing SSH access on one node escalate to root privileges and move laterally across the network. Erica Windisch of Cyberdione Labs demonstrated the issues in lab conditions against Tailscale 1.104.2 and Headscale 0.29.5. The core problem stems from privileged operations performed by the tailscaled process when handling Unix socket redirection, granting an ordinary SSH session access to root-only resources. The researcher used the technique to interact with Docker and run elevated commands, and showed that broad access policies allow automated lateral movement in under a second. Additional issues include denial-of-service conditions and bypasses of certain restrictions. Recommendations include reviewing SSH policies and disabling unnecessary socket redirection, noting that Headscale 0.29.5 lacks an independent way to turn the feature off.
Critical CVE-2026-111497 Out-of-Bounds Write Flaw in Google Brotli Decoder Impacts Broad Range of Environments
A severe vulnerability has been identified in the Google-developed Brotli decoder used for decompressing data in web communications and other applications. The flaw, tracked as CVE-2026-111497, allows out-of-bounds writes when processing specially crafted compressed data, potentially enabling arbitrary code execution, information disclosure, or denial of service. It carries a CVSS v4.0 base score of 9.2 and is rated Critical. Google has released patched versions 1.2.1, 1.1.1, and 1.0.10 of the library. Node.js incorporated the fix in its updates, while Microsoft issued an out-of-band patch for .NET on October 25, 2026, to address the issue. The vulnerability affects any environment relying on the Brotli C implementation for data decompression.