Ghost Assets in Vulnerability Management: How Identification, Merging and Asset History Eliminate Anomalies in MaxPatrol VM
Every asset in an IT infrastructure follows a lifecycle: it appears, operates and is eventually decommissioned. New assets are frequently created from existing templates yet quickly acquire unique characteristics. Constant infrastructure changes generate data anomalies including duplicates, erroneous merges and digital ghosts—assets that no longer exist but remain listed in the vulnerability management system.
To address these issues, Positive Technologies experts Kirill Maslov and Gamzat Shtanchaev describe three non-trivial tasks implemented in MaxPatrol VM: identification that matches data from disparate sources to a specific asset, correct merging of previous and new states, and maintenance of asset history that records the moment an asset disappears.
Assets in MaxPatrol VM are treated as frames on a film reel rather than real-time entities. The first frame records initial discovery via host discovery, hypervisor audit or directory service scan. Subsequent black-box scans reveal operating systems, open ports and services, while white-box audits provide users, groups, installed software and network interfaces. Specialized profiles such as PostgreSQL Audit further enrich data using transports including SSH, WMI and LDAP.
History appears as a timeline in the interface. Between scans, a data-aging mechanism uses policies that define freshness and obsolescence periods. A global 90-day threshold hides inactive assets from lists and vulnerability calculations while preserving them for historical PDQL queries. Assets are never permanently deleted.
Identification relies on type-specific key attributes. Network devices use hostname, IP and system ID; Windows systems add MAC address and FQDN; Linux systems use IP, hostname and MAC. Virtual machines prioritize VM ID. Scans must contain at least one valid key, with stricter requirements for full audits. Failed validation is logged with details of missing attributes.
Merging updates only attributes present in the new scan while leaving absent attributes unchanged. For nested objects the process recurses. An object is removed only when every source that previously supplied it has been executed and returned without it. Partial scanning profiles allow teams to collect vulnerability-relevant classes more frequently while running full audits less often.
Common ghost and duplicate scenarios include cloned machines retaining identical hostnames, virtual-machine clones that alter MAC and VM ID, and partial scans that leave stale collections intact. Recommended actions include enforcing unique hostnames after cloning and adjusting system IDs on virtual machines to prevent incorrect merging.
Related articles
PHP Prepares Critical Patches for All Supported Versions One Month After Emergency Update
The PHP development team announced on November 18 that it will release updates for all supported interpreter versions to address multiple vulnerabilities, including critical ones. The fixes target a use-after-free flaw in file upload progress tracking that can lead to remote code execution when specific session serialization formats are combined. This comes shortly after emergency patches issued on October 21 resolved two remote code execution issues collectively known as PHP2Shell. The new vulnerability, tracked as CVE-2026-115560 with a CVSS score of 9.8, arises when applications switch session formats from php_binary or php_serialize to php after upload tracking has begun. Developers are advised to disable session.upload_progress.enabled until patches are applied and verified. Releases are scheduled for November 19 between 17:00 and 17:30 Moscow time, accompanied by a detailed security bulletin.
WordPress 7.1.5 Released to Patch Multiple Vulnerabilities Including Privilege Escalation
The WordPress development team has issued version 7.1.5 to resolve more than 20 security issues spanning privilege escalation, remote code execution risks, SQL injection, and cross-site scripting flaws. The update specifically addresses an attribute-based vulnerability in the Template Part block that could allow attackers to escalate privileges and potentially execute arbitrary code. A separate flaw in multisite environments enables site administrators to hijack super-admin accounts by abusing the customizer menu preview feature. Two SQL injection vulnerabilities and multiple XSS issues were also corrected, along with information disclosure problems. Sites configured for automatic background updates will receive the patch automatically, while manual updates remain available through the admin dashboard. Backports are being rolled out for branches starting from WordPress 4.7.
CISA Adds Four Actively Exploited Vulnerabilities to KEV Catalog Targeting Apache Axis, REDCap, Synology DSM and LiteLLM
The U.S. Cybersecurity and Infrastructure Security Agency has added four vulnerabilities to its Known Exploited Vulnerabilities catalog after confirming active exploitation in the wild. The flaws affect Apache Axis, REDCap, Synology DSM, and LiteLLM, prompting mandatory remediation for federal agencies. CVE-2026-90436 in Apache Axis allows unauthenticated remote code execution via crafted SOAP fault messages under specific conditions. CVE-2026-90817 in REDCap enables unauthenticated remote code execution through manipulated HTTP requests targeting public survey and data import functions, provided an attacker knows a valid survey hash. The remaining two vulnerabilities in Synology DSM and LiteLLM were also confirmed exploited but lack detailed public descriptions at this time. Organizations are urged to apply patches immediately to prevent further attacks.
NGINX Patches Critical Remote Code Execution Vulnerability Present Since 2015 (CVE-2026-123007)
NGINX has released patches for a critical vulnerability, CVE-2026-123007, that allowed unauthenticated remote code execution on servers with HTTP/2 enabled. The flaw existed in the codebase since version 1.9.5 released in 2015 and was fixed in versions 1.30.7 and 1.31.9 on November 18. Researchers at Wiz discovered that improper handling of HTTP/2 flow control counters leads to memory corruption, enabling code execution that bypasses ASLR and runs with the privileges of the NGINX worker process. The vulnerability affects even servers serving only static files without backend application connections. A second related issue, CVE-2026-123633, involving use-after-free in HTTP/2 handling, was also addressed in the same updates. Administrators are advised to apply the patches immediately or disable HTTP/2 as a temporary mitigation if updates cannot be installed promptly. No in-the-wild exploitation of CVE-2026-123007 had been observed at the time of disclosure.