HIGH 7.2

CVE-2026-9777: ATEN Unizon Directory Traversal RCE Vulnerability Analysis

ATEN Unizon contains a directory traversal vulnerability in its restoreDB functionality that allows authenticated users to bypass normal file access restrictions and execute arbitrary code with SYSTEM-level privileges. An attacker with valid credentials can craft a malicious file path that traverses the directory structure, allowing them to place and execute code outside of intended boundaries. This is a post-authentication attack, meaning the attacker must already have login access to the system.

Source data · NVD / CISA · public domain

CVSS
3.0 · 7.2 HIGH · CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Weaknesses (CWE)
CWE-22
Affected products
1 configuration(s)
Published / Modified
2026-06-24 / 2026-06-27

NVD description (verbatim)

ATEN Unizon restoreDB Directory Traversal Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of ATEN Unizon. Authentication is required to exploit this vulnerability. The specific flaw exists within the restoreDB method. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-28578.

2 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-9777 is a CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) vulnerability affecting ATEN Unizon. The restoreDB method fails to properly validate user-supplied file paths before using them in file operations, enabling directory traversal attacks. An authenticated attacker can exploit this to write arbitrary files to unintended locations and achieve remote code execution in the SYSTEM security context. The vulnerability has a CVSS 3.0 score of 7.2 (HIGH) with a vector of CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, reflecting network accessibility, low attack complexity, high privileges required, and full impact on confidentiality, integrity, and availability.

Business impact

Compromise of ATEN Unizon installations could allow an insider or an attacker who has obtained administrative credentials to gain complete system control. Since exploitation runs code as SYSTEM, the attacker gains the highest privilege level on Windows systems, potentially enabling lateral movement, data exfiltration, persistent backdoor installation, and denial of service. Organizations using Unizon for device management or control across their infrastructure face significant operational and security risk, particularly if the system manages critical hardware.

Affected systems

ATEN Unizon installations are affected. Verify the specific version scope against ATEN's official advisory. Unizon is commonly deployed for centralized management of ATEN devices such as KVMs, PDUs, and environmental controls in data centers and enterprise facilities.

Exploitability

Exploitation requires valid authentication credentials, which elevates the practical barrier compared to unauthenticated attacks. However, the attack chain is straightforward once authenticated: an attacker supplies a path containing directory traversal sequences (e.g., "../../") to the restoreDB method, and the lack of path validation allows the traversal to succeed. No user interaction is needed. An insider threat or credential compromise significantly increases risk. The vulnerability has not been assigned to the CISA Known Exploited Vulnerabilities (KEV) catalog as of the last update.

Remediation

Apply patches from ATEN as soon as they become available. Until patching is possible, restrict administrative access to ATEN Unizon to only trusted personnel, enforce strong authentication (consider multi-factor authentication if supported), disable remote access if operationally feasible, and monitor authentication logs for suspicious activity. Network segmentation can limit the blast radius if a compromise occurs.

Patch guidance

Consult ATEN's official security advisory for affected versions and corresponding patch releases. Apply patches to all Unizon instances in your environment. Verify patch deployment across all systems and confirm the restoreDB function no longer accepts unvalidated path traversal sequences. Test restoreDB functionality post-patching to ensure normal operations are not disrupted.

Detection guidance

Monitor ATEN Unizon audit logs for unusual restoreDB calls, particularly those containing path traversal patterns ("../", "..\\", encoded variants). Review file system access logs for unexpected file writes outside normal Unizon directories. Alert on failed authentication attempts followed by successful logins from the same source. If available, enable verbose logging on the restoreDB method and examine process execution logs for child processes spawned by the Unizon service with SYSTEM privileges.

Why prioritize this

Although authentication is required, SYSTEM-level code execution makes this a critical risk for any organization running Unizon. The combination of high impact and low attack complexity (once authenticated) justifies rapid remediation. Internal threats and credential compromise scenarios are common; assume that plausible access paths exist. Organizations should prioritize patching alongside credential hygiene reviews.

Risk score, explained

The CVSS 3.0 score of 7.2 reflects the severity of uncontrolled code execution at the system privilege level, balanced against the requirement for high-level authentication. The vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) indicates network reachability, no special conditions needed post-authentication, and complete compromise of confidentiality, integrity, and availability. The score places this in the HIGH range, appropriate for a privileged insider threat or post-compromise lateral escalation scenario.

Frequently asked questions

Does this vulnerability require network access, or only local access?

The vulnerability is remotely exploitable (AV:N in the CVSS vector), so an attacker can reach the Unizon interface over the network. However, they must still authenticate with valid credentials before they can leverage the directory traversal flaw.

What is the difference between directory traversal and remote code execution in this case?

Directory traversal is the technique—it allows the attacker to access files outside the intended directory. Remote code execution is the outcome—once the attacker can write to unintended locations, they can place executable files and trigger their execution, gaining code control at SYSTEM privilege level.

Should we isolate Unizon systems until we can patch?

Complete isolation may not be practical if Unizon is critical to your operations. Instead, tighten access controls (restrict administrative accounts, enforce strong passwords, implement MFA if available), segment Unizon systems behind a firewall, and increase monitoring. Prioritize patching based on your deployment scope and criticality.

Is multi-factor authentication a sufficient mitigation?

MFA significantly raises the barrier to exploitation by making credential compromise harder, but it is not a substitute for patching. Use MFA as a defense-in-depth layer while you plan and execute your patch deployment.

This analysis is provided for informational purposes and reflects the state of public vulnerability data as of the publication date. Patch version numbers, affected product versions, and remediation timelines must be verified against official ATEN security advisories before taking action. SEC.co does not guarantee the completeness or timeliness of vendor patch releases. Organizations should conduct their own risk assessment based on their specific Unizon deployment, network configuration, and threat model. Test all patches in a non-production environment before broad deployment. Source: NVD (public-domain), retrieved 2026-08-02. Analysis generated by SEC.co (claude-haiku-4-5).