dbcve.org
Connect SecureApplication · Ivanti

CVE-2022-35254

HIGH · 7.5 CVSS v3.1 Published 2022-12-05
Fix available
A fix is available. Upgrade to 9.1 or later.
See remediation →
84/100
Remediation priority · High
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 unauthenticated attacker can cause a denial-of-service to the following products: Ivanti Connect Secure (ICS) in versions prior to 9.1R14.3, 9.1R15.2, 9.1R16.2, and 22.2R4, Ivanti Policy Secure (IPS) in versions prior to 9.1R17 and 22.3R1, and Ivanti Neurons for Zero-Trust Access in versions prior to 22.3R1.

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 unauthenticated attacker can cause denial-of-service to Ivanti Connect Secure (ICS), Ivanti Policy Secure (IPS), and Ivanti Neurons for Zero-Trust Access by sending specially crafted requests. This is a pre-authentication vulnerability affecting specific versions of all three products.

MitigationUpgrade to the fixed versions: ICS to 9.1R14.3, 9.1R15.2, 9.1R16.2, or 22.2R4; IPS to 9.1R17 or 22.3R1; Neurons to 22.3R1.

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.1= 9.1= 21.9= 21.12= 22.1= 22.2
Neurons For Zero Trust AccessApplication
Affected:= 22.2
Policy SecureApplication
Affected:< 9.1= 9.1= 22.1= 22.2

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
None
Integrity
None
Availability
High

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

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 the Ivanti product installed
    Access the admin interface or check system documentation to determine if Ivanti Connect Secure (ICS), Ivanti Policy Secure (IPS), or Ivanti Neurons for Zero-Trust Access is deployed
    Affected if Any of these three products are in use
  2. Check Ivanti Connect Secure version
    Log into the admin console and navigate to System > Administration > System Summary, or use the CLI command 'show version' to obtain the ICS version number
    Affected if The installed version is 9.1, 21.9, 21.12, 22.1, 22.2, or any version less than 9.1
  3. Check Ivanti Policy Secure version
    Log into the admin console and navigate to System > Administration > System Summary, or use the CLI command 'show version' to obtain the IPS version number
    Affected if The installed version is 9.1, 22.1, 22.2, or any version less than 9.1
  4. Check Ivanti Neurons for Zero-Trust Access version
    Access the Neurons admin portal or check the deployment configuration to identify the version number
    Affected if The installed version is exactly 22.2

If the product is any of the three affected products and the version matches one listed in the affected ranges, the environment is vulnerable to pre-authentication DoS attacks.

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 9.1 or later
Fixed in 9.1
Interim mitigation

Upgrade to the fixed versions: ICS to 9.1R14.3, 9.1R15.2, 9.1R16.2, or 22.2R4; IPS to 9.1R17 or 22.3R1; Neurons to 22.3R1.

Recommended fix High confidence

Connect Secure: 9.1R14.3/9.1R15.2/9.1R16.2/22.2R4 or later; Policy Secure: 9.1R17/22.3R1 or later; Neurons for Zero-Trust Access: 22.3R1 or later

  1. 1. Identify the currently deployed Ivanti product (Connect Secure, Policy Secure, or Neurons for Zero-Trust Access) and its exact version
  2. 2. For Ivanti Connect Secure: upgrade to version 9.1R14.3, 9.1R15.2, 9.1R16.2, or 22.2R4 (or later)
  3. 3. For Ivanti Policy Secure: upgrade to version 9.1R17 or 22.3R1 (or later)
  4. 4. For Ivanti Neurons for Zero-Trust Access: upgrade to version 22.3R1 (or later)
  5. 5. Download the appropriate upgrade package from the official Ivanti support portal at kb.pulsesecure.net
  6. 6. Follow the standard Ivanti upgrade procedure: backup current configuration, apply the upgrade, verify the new version is running
  7. 7. After upgrade, verify the service is functioning correctly and the vulnerability is resolved
Caveat Standard upgrade risks apply - ensure configuration backup before proceeding and test in non-production environment first

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

Fix this in Connect Secure Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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