CVE Tools

CVE-2024-21887

Exploited in the wild. In CISA KEV since 2024‑01‑10. A vendor fix is available.

Published Updated Sources: CVE.org, NVD, BDU

What to do

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

Steps

Written by AI from the record
  1. If you run Ivanti Connect Secure (9.x, 22.x) or Ivanti Policy Secure (9.x, 22.x), prioritize updating those appliances to the vendor-fixed versions as your top task today. 2) Confirm all admin accounts and access paths are tightly controlled (review who has administrator access and whether any accounts may be compromised). 3) If you can’t patch immediately, ask your IT/security person for an emergency mitigation plan to restrict or disable risky web access paths and reduce admin exposure while you patch.

What it is

From the CVE record

A command injection vulnerability in web components of Ivanti Connect Secure (9.x, 22.x) and Ivanti Policy Secure (9.x, 22.x) allows an authenticated administrator to send specially crafted requests and execute arbitrary commands on the appliance.

In plain language

Written by AI from the record

CVE-2024-21887 is a critical command-injection flaw in Ivanti Connect Secure and Ivanti Policy Secure that lets an authenticated administrator run arbitrary commands on the appliance—this is a high-priority emergency if your business uses these systems, because exploitation is known and public tools exist.

Exploitation

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

EPSS99th
Public exploit
CISA KEV
CISA KEV

Listed as exploited in the wild since 2024-01-10.

US federal agencies must remediate by 2024-01-22.

Known use in ransomware campaigns.

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Public exploits

1 source with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

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

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

Lifecycle

The patch came 126 days before any public exploit.

  1. Patch availablerecord updated
  2. Analysis publishedPatch the few that matter — and prove you were right to defer the rest
  3. Analysis publishedI gave cve.tools my software inventory. Here's exactly what it does with it.
  4. OpenVAS check added
  5. Public exploit / PoCsource: packetstormnuclei check added
  6. Patch availablerecord updated

Affected products

Technical detail

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

Scored 9.1 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 ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

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

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

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 Connect Secure, not every advisory. This one: actively exploited.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store