dbcve.org
Apex OneApplication · Trendmicro

CVE-2022-44647

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-44648.

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

An out-of-bounds read vulnerability in Trend Micro Apex One and Apex One as a Service allows a local attacker with low-privileged code execution to read sensitive information from memory due to improper bounds checking.

MitigationApply the vendor-provided security patch for Apex One to address the out-of-bounds read vulnerability.

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 is installed
    Check for the Apex One installation directory at C:\Program Files\Trend Micro\Apex One or look for the 'Apex One' service in Windows Services (services.msc)
    Affected if Apex One is not installed on the system
  2. Locate the installed version
    Check the version information. Common locations: Right-click the file dsAM.dll or scesrv.dll in the Apex One installation folder and view Properties > Details, or check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\Apex One\Version
    Affected if Unable to locate version information for comparison
  3. Compare installed version to affected range
    Match the found version number against '< 14.0.11789' or '= 2019'. For example, versions like 14.0.11700, 14.0.10000, or 2019 would be in the affected range
    Affected if The installed version is lower than 14.0.11789, or exactly matches version 2019, indicating the system is vulnerable to the out-of-bounds read flaw

A system is affected if Apex One is installed and the detected version number is either less than 14.0.11789 or exactly version 2019.

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-provided security patch for Apex One to address the out-of-bounds read vulnerability.

Recommended fix High confidence

Apex One version 14.0.11789 or later

  1. 1. Identify current Apex One version by navigating to the Apex One web console and checking the 'Product Information' or 'About' section.
  2. 2. Download the latest Apex One patch from the Trend Micro Download Center or obtain it through your licensed channel.
  3. 3. Review the patch release notes on success.trendmicro.com for version 14.0.11789 or later to confirm it includes the fix for CVE-2022-44647.
  4. 4. Create a backup of the current Apex One configuration and database before applying the patch.
  5. 5. Apply the patch during a maintenance window following Trend Micro's standard patch deployment procedures.
  6. 6. Verify the patch was applied successfully by checking the product version again and confirming the build number matches 14.0.11789 or later.
  7. 7. Test core functionality (manual scan, real-time protection, update mechanism) to ensure the update did not introduce issues.
Caveat Review release notes for any configuration changes or deprecated features in version 14.0.11789; some older agents may require reinstallation or manual update to be compatible with the new version

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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