CVE Tools
Track your stack

CVE-2022-40139

Exploited in the wild. In CISA KEV since 2022‑09‑15. A vendor fix is available.

CVSS 3.17.2HighEPSS percentile88th3.3% chance in 30 daysCISA KEVListedsince 2022-09-15, due 2022-10-06
No public exploit knownFixVendor fixNo build named by the sources

Published Updated Sources: CVE.org, NVD, BDU

NVD CVE.org

What to do

The vendor has published a fix. Version details are below where the sources state them.

  • Trend Micro Apex OneAffected: 2019 (on-prem) and SaaSUpgrade to: not statedStated by: CVE record
  • Trend Micro Apex OneAffected: On Premise (2019)Upgrade to: not statedStated by: BDU

Versions as the sources state them. Full version matrix after sign-in

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

Coverage timeline

0 publishers

  1. Added to CISA KEV catalog

    ·CISA KEV

Sourced from public security reporting — each date is when it was published, not when it happened.

What it is

From the CVE record

Improper validation of some components used by the rollback mechanism in Trend Micro Apex One and Trend Micro Apex One as a Service clients could allow a Apex One server administrator to instruct affected clients to download an unverified rollback package, which could lead to remote code execution. Please note: an attacker must first obtain Apex One server administration console access in order to exploit this vulnerability.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS88th
CISA KEV
CISA KEV

Listed as exploited in the wild since 2022-09-15.

US federal agencies must remediate by 2022-10-06.

Apply updates per vendor instructions.
Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

3.3% chance of exploitation activity in the next 30 days, which ranks it in the 88th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

7 events over 1379 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. EPSS band changemoderate → low
  3. Patch availablerecord updated
  4. Publishedweakness classified
  5. Added to CISA KEV

Affected products

And 1 more affected product. See all after sign-in

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

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

Scored 7.2 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required HighRequires admin or elevated privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

Sources

References in the record

And 4 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Apex One, not every advisory. This one: actively exploited.