Secure Access ClientApplication · Ivanti

CVE-2023-38043

HIGH · 7.8 CVSS v3.1 Published 2023-11-15
Fix available
A fix is available. Upgrade to 22.6 or later.
See remediation →
80/100
Remediation priority · High
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
A vulnerability exists on all versions of the Ivanti Secure Access Client below 22.6R1.1, which could allow a locally authenticated attacker to exploit a vulnerable configuration, potentially leading to a denial of service (DoS) condition on the user machine and, in some cases, resulting in a full compromise of the system.

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 confidence

Ivanti Secure Access Client versions prior to 22.6R1.1 contain a vulnerability that allows a locally authenticated attacker to exploit a vulnerable configuration, potentially causing denial of service and possibly achieving full system compromise.

MitigationUpgrade Ivanti Secure Access Client to version 22.6R1.1 or later to remediate this vulnerability.

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
Secure Access ClientApplication
Affected:< 22.6= 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Ivanti Secure Access Client is installed
    Locate the Ivanti Secure Access Client installation on the system using standard software inventory tools or by searching for the application in the system
    Affected if Ivanti Secure Access Client is present on the system
  2. Determine installed version
    Check the installed version of Ivanti Secure Access Client through the application's About dialog, version information in its executable, or system registry if available
    Affected if The version number cannot be determined or the application is present but version info is unavailable
  3. Compare version against affected ranges
    Compare the installed version to the affected ranges: versions less than 22.6 and version 22.6 are vulnerable
    Affected if Installed version is 22.6 or any version below 22.6 (for example, 22.5, 22.4, earlier releases)
  4. Verify client is configured and active
    Confirm the Ivanti Secure Access Client is configured with a vulnerable configuration that allows local authenticated access - review client settings and active connections
    Affected if Client is configured and running with settings that permit local authenticated attacker access

The system is affected if Ivanti Secure Access Client version 22.6 or any version below 22.6 is installed and the client is configured to allow the described vulnerable configuration.

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

Upgrade Ivanti Secure Access Client to version 22.6R1.1 or later to remediate this vulnerability.

Recommended fix Moderate confidence

22.6R1.1 or later

  1. Identify the current installed version of Ivanti Secure Access Client
  2. Download Ivanti Secure Access Client version 22.6R1.1 or later from the official vendor portal
  3. Stop the Ivanti Secure Access Client service if running
  4. Install the updated version following standard installation procedures
  5. Restart the system or the Ivanti Secure Access Client service
  6. Verify the installed version is 22.6R1.1 or later

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

Fix this in Secure Access Client Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-38043 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