CVE-2023-41719
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 · uneditedA vulnerability exists on all versions of Ivanti Connect Secure below 22.6R2 where an attacker impersonating an administrator may craft a specific web request which may lead to remote code execution.
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 · moderate confidenceIvanti Connect Secure versions prior to 22.6R2 contain an RCE vulnerability that can be exploited by an attacker impersonating an administrator through a specifically crafted web request. The attack leverages the admin interface to achieve remote code execution on the affected appliance.
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= 21.9= 21.12= 22.1= 22.2= 22.3= 22.4= 22.5= 22.6= 9.1CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 Connect Secure versionLog into the admin UI and navigate to System > Status > System Overview, or check the version via the system information page in the admin interfaceAffected if The displayed version matches any of these: 21.9, 21.12, 22.1, 22.2, 22.3, 22.4, 22.5, 22.6, or 9.1
-
Verify admin interface network accessibilityCheck if the admin web interface (typically port 443 or 8443) is accessible from untrusted networks by reviewing firewall rules or network configurationAffected if The admin interface is reachable from networks outside your trusted IP range or the internet
-
Review admin access logs for suspicious requestsExamine the admin interface audit logs for failed or successful authentication attempts from unusual IP addresses, especially those followed by administrative actionsAffected if There are admin authentication attempts or administrative actions from unknown IP addresses, particularly in rapid succession or outside normal administrative hours
-
Check for unauthorized admin accounts or configurationsNavigate to Users > Administrators in the admin UI and review the list of configured administrator accounts for any unfamiliar entriesAffected if New or unrecognized administrator accounts exist in the system
You are affected if your Ivanti Connect Secure version is 21.9, 21.12, 22.1, 22.2, 22.3, 22.4, 22.5, 22.6, or 9.1 AND the admin interface is accessible from untrusted networks or you detect suspicious admin activity in logs.
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 · scopedUpgrade Ivanti Connect Secure to version 22.6R2 or later to remediate this vulnerability. If immediate patching is not feasible, restrict administrative access to trusted IP addresses and monitor for suspicious admin-level requests.
22.6R2 or later
- Download Ivanti Connect Secure version 22.6R2 or later from the official Ivanti download portal
- Review the upgrade documentation and release notes for Ivanti Connect Secure 22.6R2
- Schedule a maintenance window as upgrades require downtime
- Backup the current appliance configuration
- Perform the upgrade following Ivanti's standard upgrade procedure
- Verify the upgrade completed successfully
- Confirm the new version is 22.6R2 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41719 — 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-2023-41719 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