dbcve.org
Apex OneApplication · Trendmicro

CVE-2022-44648

MEDIUM · 5.5 CVSS v3.1 Published 2022-12-12
Fix available
A fix is available. Upgrade to 14.0.11789 or later.
See remediation →
57/100
Remediation priority · Elevated
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 Out-of-bounds read vulnerability in Trend Micro Apex One and Apex One as a Service could allow a local attacker to disclose sensitive information 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. This is similar to, but not the same as CVE-2022-44647.

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

An out-of-bounds read vulnerability in Trend Micro Apex One allows a local attacker with low-privileged code execution to read sensitive information from memory beyond allocated buffer boundaries, potentially exposing credentials or other confidential data.

MitigationApply the vendor-supplied security patch for Apex One. Since exploitation requires low-privileged code execution first, enforce least-privilege principles and restrict local code execution capabilities to limit attack surface.

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

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

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. Verify Apex One installation
    Check if Trend Micro Apex One is installed on the system. Look for the product in Add/Remove Programs (Windows) or check for the Apex One installation directory (commonly in C:\Program Files\Trend Micro\Apex One or C:\Program Files (x86)\Trend Micro\Apex One).
    Affected if Apex One is not found on the system, so the CVE does not apply.
  2. Identify installed Apex One version
    Locate the version information. Check the file properties of the main executable (such as ofcscan.dll, TmCCsf.exe, or the Apex One version file in the installation directory) or use the Trend Micro Apex One console to view the version under 'Updates > Product Information'.
    Affected if The installed version cannot be determined or the product is not Apex One.
  3. Compare version against affected ranges
    Compare the identified version number to the affected ranges: versions lower than 14.0.11789, or version 2019 (which maps to the 2019 release version). Note that versions 14.0.11789 and above are patched.
    Affected if The installed version is below 14.0.11789, or the version is 2019.
  4. Confirm vulnerability context
    This CVE requires the Apex One service or component to be running. Verify that the Apex One real-time protection, OfficeScan service, or related process (such as TmCCsf.exe, ofservice.exe) is active on the endpoint.
    Affected if Apex One is installed in a vulnerable version but the service is completely disabled and not running.

The environment is affected if Trend Micro Apex One is installed with a version lower than 14.0.11789 or equal to the 2019 release, and the Apex One service or component is running on the system.

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-supplied security patch for Apex One. Since exploitation requires low-privileged code execution first, enforce least-privilege principles and restrict local code execution capabilities to limit attack surface.

Recommended fix High confidence

14.0.11789 or later

  1. 1. Back up all Apex One configuration data and database files according to your organization's backup policy.
  2. 2. Ensure the system meets the hardware and software requirements for Apex One version 14.0.11789 or later.
  3. 3. Download the Apex One latest version from the Trend Micro Download Center or your licensed portal.
  4. 4. Run the installation program with appropriate administrative privileges.
  5. 5. Follow the on-screen installation wizard to complete the upgrade.
  6. 6. After upgrade, verify that the Apex One services are running correctly.
  7. 7. Confirm the installed version is 14.0.11789 or later using the Apex One console or version check tool.

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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