CVE Tools

CVE-2023-46805

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.

  • Ivanti ICSAffected: ≥ 9.1R18, ≤ 9.1R18Upgrade to: after 9.1R18Affected: ≥ 22.6R2, ≤ 22.6R2Upgrade to: after 22.6R2Stated by: CVE record
  • Ivanti IPSAffected: ≥ 9.1R18, ≤ 9.1R18Upgrade to: after 9.1R18Affected: ≥ 22.6R1, ≤ 22.6R1Upgrade to: after 22.6R1Stated by: CVE record
  • Ivanti Connect SecureAffected: 9.0Upgrade to: not statedStated by: BDU
  • Ivanti Policy SecureAffected: 9.0Upgrade to: not statedStated by: BDU

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

Steps

Written by AI from the record
  1. Update the affected Ivanti products (Ivanti ICS 9.x/22.x, Ivanti IPS, Ivanti Policy Secure, and Ivanti Connect Secure) to the vendor’s fixed versions as soon as possible.
  2. If you can’t patch immediately, restrict access so the Ivanti web components are not reachable from the internet (allow only trusted IPs/VPN).
  3. Ask your IT/security person to check whether these systems are currently exposed and whether indicators of compromise or unusual access to restricted pages have occurred.

Coverage timeline

1 publisher
  1. Advisory coverage

    ·BleepingComputer summary
  2. Added to CISA KEV catalog

    ·CISA KEV

Sourced from public security reporting — each date is when it was published, not when it happened. 5 further articles named this CVE in wider roundups without reporting it as a distinct event.

What it is

From the CVE record

An authentication bypass vulnerability in the web component of Ivanti ICS 9.x, 22.x and Ivanti Policy Secure allows a remote attacker to access restricted resources by bypassing control checks.

In plain language

Written by AI from the record

CVE-2023-46805 is a serious Ivanti product flaw that can let an outside attacker skip login checks and view restricted pages; if you use Ivanti ICS/IPS or Ivanti Policy Secure/ Ivanti Connect Secure, you should act now because it’s already been used in ransomware and public exploits 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 availablepatch available, record updated, record updated
  2. Patch availablerecord updated
  3. OpenVAS check added
  4. Public exploit / PoCsource: packetstormnuclei check added
  5. Patch availablerecord updated
  6. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

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

Scored 8.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 NoneNo authentication required — anyone can exploit this
  • 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 LowData modification is possible but limited in scope or consequence
  • Availability NoneNo availability impact

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.