CVE-2022-35258
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 · uneditedAn 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 confidenceAn unauthenticated attacker can cause a denial-of-service (DoS) condition in Ivanti Connect Secure (ICS), Ivanti Policy Secure (IPS), and Ivanti Neurons for Zero-Trust Access by exploiting this vulnerability. The attack can be launched remotely without authentication, resulting in service disruption.
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< 9.1= 9.1= 21.9= 21.12= 22.1= 22.2= 22.2< 9.1= 9.1= 22.1= 22.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Ivanti productAccess the admin console login page or check system documentation to determine if the device is Ivanti Connect Secure, Ivanti Policy Secure, or Ivanti Neurons for Zero-Trust Access. The product name is typically displayed on the login page or in the system header.Affected if The product is Connect Secure, Policy Secure, or Neurons for Zero-Trust Access and the version matches affected ranges
-
Determine the installed version numberLog into the admin console and navigate to System > Overview or Help > About to view the firmware/software version. Alternatively, check the login page footer which often displays the version.Affected if The version cannot be determined or is listed in the affected version ranges
-
Compare version against affected ranges for Connect SecureIf the product is Connect Secure, check if the version is: < 9.1, 9.1, 21.9, 21.12, 22.1, or 22.2. These specific versions are vulnerable.Affected if The installed Connect Secure version matches any of these: < 9.1, 9.1, 21.9, 21.12, 22.1, or 22.2
-
Compare version against affected ranges for Policy SecureIf the product is Policy Secure, check if the version is: < 9.1, 9.1, 22.1, or 22.2. These specific versions are vulnerable.Affected if The installed Policy Secure version matches any of these: < 9.1, 9.1, 22.1, or 22.2
-
Compare version against affected ranges for Neurons for Zero-Trust AccessIf the product is Neurons for Zero-Trust Access, check if the version is exactly 22.2. This specific version is vulnerable.Affected if The installed Neurons for Zero-Trust Access version is exactly 22.2
The environment is affected if any Ivanti Connect Secure, Policy Secure, or Neurons for Zero-Trust Access instance is running a version that matches the specific affected version numbers listed in the CVE (9.1, 21.9, 21.12, 22.1, 22.2, or versions prior to 9.1).
Generated from the published advisory. Verify against your own configuration.
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 · scoped9.1
Upgrade to the patched versions: Ivanti Connect Secure to 9.1R14.3, 9.1R15.2, 9.1R16.2, or 22.2R4; Ivanti Policy Secure to 9.1R17 or 22.3R1; Ivanti Neurons for Zero-Trust Access to 22.3R1 or later.
22.3R1 for Policy Secure and Neurons ZTA; 22.2R4 for Connect Secure
- 1. Identify the exact currently installed version of Ivanti Connect Secure, Policy Secure, or Neurons for Zero-Trust Access
- 2. Determine which product family your installation falls under (Connect Secure, Policy Secure, or Neurons for ZTA)
- 3. For Connect Secure: upgrade to version 9.1R14.3, 9.1R15.2, 9.1R16.2, or 22.2R4 (recommended: 22.2R4)
- 4. For Policy Secure: upgrade to version 9.1R17 or 22.3R1 (recommended: 22.3R1)
- 5. For Neurons for Zero-Trust Access: upgrade to version 22.3R1
- 6. Verify upgrade was successful by confirming the new version in the admin console
- 7. Test that the service is functioning normally and the DoS vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35258 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-35258 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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