SYSTEM code execution via junction-based file creation
Published Mar 7, 2023 · Updated Mar 5, 2025
Link following in Trend Micro Apex One before 14.0.0.11564 allows local users to execute arbitrary code as SYSTEM through a crafted junction. The Apex One NT RealTime Scan service follows an attacker-created junction while creating a quarantined replacement file, causing a privileged file write at an arbitrary location. Exploitation requires low-privileged code execution on a Windows endpoint and can turn that file write into full SYSTEM-level code execution.
Summary
What happened
Link following in Trend Micro Apex One before 14.0.0.11564 allows local users to execute arbitrary code as SYSTEM through a crafted junction. The Apex One NT RealTime Scan service follows an attacker-created junction while creating a quarantined replacement file, causing a privileged file write at an arbitrary location. Exploitation requires low-privileged code execution on a Windows endpoint and can turn that file write into full SYSTEM-level code execution.
The record
- CVE
- CVE-2023-25146
- Published
- Mar 7, 2023
- Updated
- Mar 5, 2025
- Vendor
- Trend Micro
- Product
- Trend Micro Apex One
- Classifications
- CWE-59, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 7, 2023CVE publishedPublication date reported by the CVE source.
- Mar 5, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2019 (14.0) <14.0.0.11564
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo