dbcve.org
Apex OneApplication · Trendmicro

CVE-2022-30700

HIGH · 7.8 CVSS v3.1 Published 2022-05-27
Fix available
A fix is available. Upgrade to 14.0.10349 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An incorrect permission assignment vulnerability in Trend Micro Apex One and Apex One as a Service could allow a local attacker to load a DLL with escalated privileges on affected installations. Please note: an attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a local privilege escalation vulnerability in Trend Micro Apex One where incorrect permission assignments allow an attacker with low-privileged code execution to load a malicious DLL with elevated privileges. The vulnerability stems from improper ACL configuration on the Apex One installation that permits unprivileged users to influence which DLLs the service loads.

MitigationApply the vendor-supplied security patch for CVE-2022-30700 from Trend Micro. As a compensating control, review and restrict file system permissions on Apex One installation directories to prevent unauthorized DLL placement by low-privileged users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Apex OneApplication
Affected:< 14.0.10349= 2019

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apex One installation path and version
    Locate the Apex One installation directory (commonly C:\Program Files\Trend Micro\Apex One) and check the version. Open the file 'ofcversion.ini' or right-click 'Apex One' in Programs and Features to view the version number.
    Affected if Installed version is older than 14.0.10349, or the version shows 2019 (builds prior to patch 10349).
  2. Verify ACL permissions on the Apex One installation folder
    Right-click the Apex One installation folder, go to Properties > Security > Advanced. Inspect the permission entries for users with limited privileges (e.g., Users, Authenticated Users, or specific low-privileged accounts).
    Affected if Low-privileged users or groups have Write, Modify, or Full Control permissions on the installation directory, allowing them to replace or add DLL files.
  3. Check permissions on the 'PccNTMon' or service executable subfolder
    Navigate to the subfolder containing the service executable (commonly in the 'PccNTMon' or 'SAV' subdirectory within the Apex One folder). Review ACLs on this folder and its contents.
    Affected if Unprivileged users have Write or Modify permissions on folders from which the service loads DLLs.
  4. Inspect ACL inheritance and ownership on DLL load locations
    Use 'icacls.exe' from an elevated command prompt on the Apex One folder and subfolders (e.g., icacls 'C:\Program Files\Trend Micro\Apex One\*') to list explicit permission entries. Look for entries granting 'Everyone', 'Users', or similar groups Write access.
    Affected if Inherited or explicit permissions allow non-admin users to write DLL files to directories from which the Apex One service loads libraries.

A user is affected if Apex One version is below 14.0.10349 (or is the 2019 release) AND low-privileged accounts have write/modify permissions on the Apex One installation directories where the service loads DLLs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 14.0.10349 or later
Fixed in 14.0.10349
Interim mitigation

Apply the vendor-supplied security patch for CVE-2022-30700 from Trend Micro. As a compensating control, review and restrict file system permissions on Apex One installation directories to prevent unauthorized DLL placement by low-privileged users.

Recommended fix High confidence

Apex One version 14.0.10349 or later

  1. 1. Identify the current installed version of Trend Micro Apex One or Apex One as a Service
  2. 2. Navigate to the Trend Micro Apex One management console
  3. 3. Verify that the current version is below 14.0.10349
  4. 4. Download the latest version of Apex One from the Trend Micro download center or access the hotfix package from Trend Micro Support
  5. 5. Apply the upgrade to version 14.0.10349 or later following the standard upgrade procedure in the Trend Micro Apex One documentation
  6. 6. Verify the installation was successful and the version is now 14.0.10349 or higher
Caveat Ensure to review upgrade requirements and backup the database before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Apex One Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30700 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-30700 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data