Skip to main content

ASUSTOR ABP/AES CVE-2026-18759

| EUVDEUVD-2026-52640 HIGH
Improper Authentication (CWE-287)
2026-08-04 ASUSTOR1 GHSA-2p27-7hcf-mpp3
8.5
CVSS 4.0 · Vendor: ASUSTOR1
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Authenticate as low-privileged local user
  2. Delivery
    Read world-accessible IPC key file
  3. Exploit
    Decrypt key via Windows DPAPI
  4. Install
    Craft AES-encrypted IPC request with traversal path
  5. C2
    Submit forged request to SYSTEM-running service
  6. Execute
    Service bypasses substring path check
  7. Impact
    Arbitrary file read/write executed as NT AUTHORITY\SYSTEM

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication mechanism validation
MITRE ATT&CK

2 techniques across 2 tactics: Defense Evasion, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated local or domain user account with an interactive or remote desktop session on the Windows host where ASUSTOR ABP or AES is installed and the background service is actively running. The attacker must be able to read the IPC key file - which is accessible to standard users by default filesystem ACL - and call the Windows DPAPI CryptUnprotectData function within their own user session context to unwrap the key; both are available to any authenticated local user without elevated rights. No special group membership (e.g., local Administrators, Backup Operators), non-default product configuration, or specific OS version beyond a standard Windows install is required. Exploitation is strictly local (AV:L): remote unauthenticated attackers cannot reach the file-based IPC channel over the network. No privileged user interaction is needed. Exploitation is bounded to systems where ABP or AES is installed; systems not running these ASUSTOR products are unaffected.

Impact

The CVSS 4.0 score of 8.5 with vector AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N accurately represents the threat profile. Attack complexity is genuinely low - no race conditions, no heap grooming, no special timing required; only reading a file and invoking a standard Windows API. The PR:L metric reflects that a local authenticated account is the sole prerequisite. The full C/H/I:H triad means an attacker achieves complete control of the local filesystem as SYSTEM, enabling credential theft, backdoor installation, or security tool tampering. This CVE does not appear in the CISA KEV catalog, and no public POC has been disclosed, keeping immediate widespread risk lower. However, the attack path is straightforward enough that a motivated insider or malware process with local user-level access could exploit it with minimal tooling. Risk is highest on shared Windows hosts - backup servers, endpoint management systems, or NAS-adjacent workstations - where ASUSTOR agents are deployed alongside untrusted local user accounts. No EPSS data was available in the provided intelligence; the absence of KEV listing and POC suggests targeted rather than widespread exploitation is the current threat model.

Exploit ScenarioDerived

A low-privileged domain or local user logged into a Windows workstation with ASUSTOR ABP or AES installed calls the Windows DPAPI to decrypt the IPC encryption key stored in a standard-user-readable file, then constructs a forged AES-encrypted IPC request embedding a directory traversal payload such as '..\..\Windows\System32\config\SAM' as the destination path. The background service, running as NT AUTHORITY\SYSTEM, processes the request without checking the caller's identity, reads or writes the targeted file at SYSTEM privilege, and the attacker extracts the SAM database or drops a new SYSTEM-owned binary, achieving full local privilege escalation. No public POC has been identified, but the exploit path requires only standard Windows API calls and file I/O.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 04, 2026

ASUSTOR Backup Plan (ABP) and EZSync (AES) background services run as NT AUTHORITY\SYSTEM and expose a file-based IPC channel whose AES encryption key is readable by standard users and recoverable via Windows DPAPI, allowing any authenticated local account to forge valid service requests. The services further fail to verify the identity of the requesting process and validate filesystem paths using an insufficient substring check, enabling directory traversal sequences to bypass path restrictions. A local attacker can chain these weaknesses to perform arbitrary file reads and writes as SYSTEM, achieving full local privilege escalation. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.

RemediationAI

Upgrade ASUSTOR Backup Plan (ABP) beyond version 2.0.7.10171 and ASUSTOR EZSync (AES) beyond version 1.1.1.3113 by consulting the vendor advisory at https://www.asustor.com/security/security_advisory_detail?id=70 for the specific fixed release numbers, which are not independently confirmed from available data. Where immediate patching is not feasible, restrict the set of local user accounts on systems running ABP or AES to only those strictly required, reducing the attack surface by limiting who can attempt key recovery. Disabling the ABP or AES background service entirely on hosts where backup or sync functionality is unnecessary is an effective compensating control, with the trade-off of losing that product's functionality. Hardening the filesystem ACLs on the IPC encryption key file to deny read access to standard user accounts would raise the exploitation barrier, though the exact file path must be sourced from the vendor or reverse engineering, and this approach may break legitimate product functionality.

Affected VersionsENISA

ABP and AES AES 1.0 ≤1.1.1.3113
ABP and AES ABP 2.0 ≤2.0.7.10171

Affected Packages

euvd abp_and_aes_abp no fix
euvd abp_and_aes_aes no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Both affected products - ASUSTOR Backup Plan (ABP) 2.0.7.10171 and earlier, and ASUSTOR EZSync (AES) 1.1.1.3113 and earlier, identified under CPE cpe:2.3:a:asustor_inc.:abp_and_aes - operate Windows background services under the NT AUTHORITY\SYSTEM account and communicate with other processes through a file-based IPC mechanism. The IPC channel is encrypted with AES, but the encryption key material is stored in a file with ACLs permitting read access by standard users. That key file is additionally protected by Windows DPAPI (Data Protection API), which binds the secret to the current user session - meaning any local authenticated user can call the DPAPI to unwrap the key in their own context. CWE-287 (Improper Authentication) captures the root cause: the service authenticates the message (via the shared AES key) but not the caller, so possession of the key is the sole gatekeeper. A second weakness compounds this: path validation for destination files uses a substring check rather than canonicalized path comparison, making it bypassable with directory traversal sequences (e.g., '../../') that satisfy the substring filter while escaping the intended directory.

Know when Abp And Aes gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (ASUSTOR1) PRIMARY 8.5 HIGH
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 7.8 HIGH

Local attack requiring only a standard authenticated account (PR:L); no scope change since SYSTEM-level impact is confined to the local host.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (ASUSTOR1).

CVSS VectorVendor: ASUSTOR1

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

The background service of ABP or AES runs as NT AUTHORITY\SYSTEM and implements a file-based inter-process communication (IPC) mechanism protected by AES encryption. Because the encryption key file is readable by standard users and protected using DPAPI. Any authenticated local user can recover the key and forge valid IPC requests. Furthermore, the service does not check the identity of the requesting process and validates destination paths using an insufficient substring check. A local attacker can submit crafted encrypted requests containing directory traversal sequences to perform arbitrary file reads and arbitrary file writes as NT AUTHORITY\SYSTEM, leading to full local privilege escalation. Affected products and versions include: ABP (ASUSTOR Backup Plan) 2.0.7.10171 and earlier as well as AES (ASUSTOR EZSync) 1.1.1.3113 and earlier.

Executive ViewAI

Why It Matters

ASUSTOR Backup Plan and EZSync services are vulnerable to local privilege escalation, enabling any user with local system access to execute arbitrary operations with SYSTEM-level permissions. Organizations using these ASUSTOR products must immediately assess exposure and restrict local access, as internal users or attackers who gain initial local access could escalate privileges and compromise critical backup infrastructure.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Restrict local logon access via Group Policy (apply Deny Log On Locally policy to standard user groups), disable ASUSTOR services if operationally feasible, implement application whitelisting on affected systems to prevent child process execution, enable Windows audit logging for privilege escalation, and isolate affected systems from sensitive infrastructure using network segmentation.

Threat Intelligence Overview

EPSS Score
0.1%
Top 98% exploitable
Prevalence
Low
niche NAS vendor backup/sync agents, limited enterprise footprint
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy