dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 22 Jan 2024. Known ransomware use
Connect SecureApplication · Ivanti

CVE-2023-46805

HIGH · 8.2 CVSS v3.1 Published 2024-01-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit Remotely reachable No privileges 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 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.

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

This is an authentication bypass vulnerability in the web component of Ivanti ICS versions 9.x and 22.x, as well as Ivanti Policy Secure. The flaw allows remote attackers to bypass control checks and access restricted resources without proper authentication.

MitigationApply the vendor-supplied patches or upgrade to the fixed versions of Ivanti ICS and Policy Secure as specified in the Ivanti security advisory. As a temporary mitigation, restrict network access to the web management interface to trusted IPs only.

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
Connect SecureApplication
Affected:= 9.0= 9.1= 22.1= 22.2= 22.3= 22.4= 22.5= 22.6
Policy SecureApplication
Affected:= 9.0= 9.1= 22.1= 22.2= 22.3= 22.4= 22.5= 22.6

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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. Identify installed Ivanti product and version
    Access the admin console login page or check system information within the appliance. The version is typically displayed on the login page footer or in System > Management > System Overview. Alternatively, check the installed package version via CLI using 'dpkg -l' or 'rpm -q' depending on the underlying OS.
    Affected if The installed version matches 9.0, 9.1, 22.1, 22.2, 22.3, 22.4, 22.5, or 22.6 of Ivanti Connect Secure or Ivanti Policy Secure.
  2. Confirm web management interface is accessible
    Attempt to reach the Ivanti web interface over HTTPS (port 443) from a network location. Verify whether the /admin, /dana, or / endpoint responds with the login page.
    Affected if The web management interface is exposed and reachable over the network.
  3. Review authentication logs for bypass attempts
    Examine the Ivanti system logs, specifically Authentication logs and Admin Access logs, for entries showing successful authentication without corresponding login page requests, or for repeated requests to protected URIs from unauthenticated sources.
    Affected if Logs contain authentication events from unfamiliar IP addresses, entries showing access to restricted endpoints without proper authentication records, or patterns of authentication bypass.
  4. Check for unauthorized admin sessions
    Navigate to Administration > Administrators or System > Sessions in the admin console. Review active sessions and recent admin login history for unknown accounts or sessions originating from unexpected IP addresses.
    Affected if Unexpected administrator accounts exist, or admin sessions are active from IP addresses not recognized as legitimate administrator locations.
  5. Inspect web server configuration for anomalies
    Review the web server or proxy configuration files (typically found in /opt or /var directories depending on installation) for unauthorized URL rewrite rules, new endpoints, or modified access control lists that could indicate exploitation.
    Affected if Configuration files contain unexpected rules, new endpoints, or modifications that bypass authentication controls.

You are affected if you are running Ivanti Connect Secure or Ivanti Policy Secure versions 9.0, 9.1, 22.1, 22.2, 22.3, 22.4, 22.5, or 22.6 with the web management interface exposed, or if logs show evidence of unauthorized access attempts.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patches or upgrade to the fixed versions of Ivanti ICS and Policy Secure as specified in the Ivanti security advisory. As a temporary mitigation, restrict network access to the web management interface to trusted IPs only.

Recommended fix Moderate confidence

Latest available Ivanti Connect Secure / Policy Secure release (beyond 22.2)

  1. 1. Check current Ivanti Connect Secure or Policy Secure version via admin console or CLI
  2. 2. Confirm the version is one of the affected releases: 9.0, 9.1, 22.1, or 22.2
  3. 3. Upgrade to the latest available Ivanti Connect Secure or Policy Secure release that includes the security fix for CVE-2023-46805
  4. 4. After upgrade, verify the web component authentication controls are functioning correctly
  5. 5. Review access logs for any indicators of exploitation attempts prior to patching
Caveat Review Ivanti release notes for upgrade path considerations, as major version jumps may require specific migration procedures

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Connect Secure Exploited in the wild — priority engagement
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA6.0 h
40.0 hours of engineering $6,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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