dbcve.org
Secure Access ClientApplication · Ivanti

CVE-2024-7571

HIGH · 7.8 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 22.7 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
Incorrect permissions in Ivanti Secure Access Client before 22.7R4 allows a local authenticated attacker to escalate their privileges.

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

Ivanti Secure Access Client before version 22.7R4 contains a permission misconfiguration that allows a local authenticated user to elevate their privileges to higher permission levels, likely through improper file or service permissions.

MitigationUpgrade Ivanti Secure Access Client to version 22.7R4 or later to resolve the permission misconfiguration.

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.7= 22.7

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. Check if Ivanti Secure Access Client is installed
    Look for the product in the system program files, check Windows Services for 'Ivanti Secure Access Client' service, or search for isaCtl.exe or similar executable files in Program Files directories
    Affected if The product is found installed on the system
  2. Identify the installed version
    Right-click on the Ivanti Secure Access Client executable (isaCtl.exe or the client application) and select Properties, then check the Details tab for version information. Alternatively, run 'wmic product where "name like '%Ivanti%'" get version, name' or check Add/Remove Programs
    Affected if The version displayed is lower than 22.7R4, or shows 22.7 (including 22.7.0, 22.7.1, etc.)
  3. Examine file permissions on Ivanti program directory
    Right-click the Ivanti Secure Access Client installation folder (typically in Program Files or Program Files x86), select Properties, go to Security tab, and check if standard users have Write or Modify permissions to executable files or DLLs
    Affected if Authenticated users or non-admin users have Write, Modify, or Full Control permissions to program executables or configuration files in the installation directory
  4. Examine service permissions for Ivanti services
    Open Services (services.msc), find Ivanti-related services, right-click and select Properties, then check the Security tab. Use 'sc qc' or 'sc sdshow' commands in Command Prompt to query service configuration and access control lists
    Affected if The service allows non-privileged users to modify the service binary path or configuration, or if service ACLs permit low-privilege users to stop/start or reconfigure the service

A system is affected if Ivanti Secure Access Client version 22.7 or any version below 22.7R4 is installed AND the program files or service permissions allow authenticated local users to modify executables or service 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.7 or later
Fixed in 22.7
Interim mitigation

Upgrade Ivanti Secure Access Client to version 22.7R4 or later to resolve the permission misconfiguration.

Recommended fix High confidence

22.7R4 or later

  1. Check the current version of Ivanti Secure Access Client installed on the system
  2. Download Ivanti Secure Access Client version 22.7R4 (or a later stable release) from the official Ivanti support portal or authorized distribution channel
  3. Close or terminate any running instances of Ivanti Secure Access Client before upgrading
  4. Run the installer for version 22.7R4 with appropriate administrative privileges
  5. Follow the on-screen prompts to complete the upgrade installation
  6. Restart the system if prompted by the installer
  7. Verify the installed version shows 22.7R4 or later after upgrade completes
Caveat Review Ivanti release notes for any configuration or compatibility changes before upgrading in production environments

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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