Anti-tampering bypass via incorrect DLP registry permissions
Published Oct 10, 2022 · Updated Aug 3, 2024
Incorrect registry permissions in Trend Micro Apex One 2019 and SaaS DLP allow local users with administrative credentials to bypass anti-tampering controls. Trend Micro identifies the locus as DLP-related Windows registry permissions but does not disclose the affected keys or access-control entries. Administrative access to an affected Windows host is required, and successful exploitation defeats only unspecified elements of product self-protection.
Summary
What happened
Incorrect registry permissions in Trend Micro Apex One 2019 and SaaS DLP allow local users with administrative credentials to bypass anti-tampering controls. Trend Micro identifies the locus as DLP-related Windows registry permissions but does not disclose the affected keys or access-control entries. Administrative access to an affected Windows host is required, and successful exploitation defeats only unspecified elements of product self-protection.
The record
- CVE
- CVE-2022-41748
- Published
- Oct 10, 2022
- Updated
- Aug 3, 2024
- Vendor
- Trend Micro
- Product
- Trend Micro Apex One
- Classifications
- CWE-276, T1562.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Oct 10, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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 (on-prem) and SaaS
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