dbcve.org
Apex OneApplication · Trendmicro

CVE-2022-44654

HIGH · 7.5 CVSS v3.1 Published 2022-12-12
Fix available
A fix is available. Upgrade to 14.0.11789 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Affected builds of Trend Micro Apex One and Apex One as a Service contain a monitor engine component that is complied without the /SAFESEH memory protection mechanism which helps to monitor for malicious payloads. The affected component's memory protection mechanism has been updated to enhance product security.

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 · moderate confidence

Trend Micro Apex One and Apex One as a Service contain a monitor engine component that was compiled without the /SAFESEH compiler flag, which provides Structured Exception Handling (SEH) overwrite protection. This memory protection mechanism helps detect and block malicious payloads that attempt to exploit buffer overflows by overwriting exception handlers. The vendor has addressed this by updating the affected component with proper memory protection.

MitigationApply the vendor security update for Apex One to ensure the monitor engine component is compiled with /SAFESEH protection enabled. Organizations should verify their installations are running the patched version.

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.11789= 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Locate Apex One installation and version
    Open the Apex One web console or check the product icon in the system tray for the version number. Alternatively, check the Windows Registry at HKLM\SOFTWARE\TrendMicro\Apex One\CurrentVersion or look for version info in the installation directory.
    Affected if The displayed version is lower than 14.0.11789, or shows as version 2019.
  2. Verify the exact version build number
    In the Apex One web console, navigate to Help > About or similar to view the full build number. Compare this numeric build against 11789.
    Affected if The build number is less than 11789 (for major version 14.x) or indicates release year 2019.
  3. Confirm monitor engine component presence
    Check if the Apex One monitor engine service is running. Look for processes such as TmCCnf.dll or check the "Monitor" component in the Apex One console under Server > Agent Management.
    Affected if The monitor engine component is present and the version falls within the affected range.
  4. Cross-check version via Windows Registry
    Open regedit and navigate to HKLM\SOFTWARE\TrendMicro\Apex One\CurrentVersion. Check the "Version" or "AgentVersion" value displayed.
    Affected if The registry version string shows a version lower than 14.0.11789 or shows 2019.

You are affected if your Apex One installation shows a version lower than 14.0.11789 or displays as version 2019, and the monitor engine component is active.

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.11789 or later
Fixed in 14.0.11789
Interim mitigation

Apply the vendor security update for Apex One to ensure the monitor engine component is compiled with /SAFESEH protection enabled. Organizations should verify their installations are running the patched version.

Recommended fix High confidence

Apex One version 14.0.11789 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 Download Center or access the console to obtain the update
  3. 3. Download Apex One version 14.0.11789 or later (or the latest available patch for Apex One 2019)
  4. 4. Apply the update following Trend Micro's standard upgrade procedures
  5. 5. Verify the version after installation to confirm the patch was applied successfully

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

Fix this in Apex One Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-44654 — 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-44654 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