dbcve.org
Connect SecureApplication · Ivanti

CVE-2024-39709

HIGH · 7.8 CVSS v3.1 Published 2024-11-13
Fix available
A fix is available. Upgrade to 9.1 / 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
Incorrect file permissions in Ivanti Connect Secure before version 22.6R2 (Not Applicable to 9.1Rx) and Ivanti Policy Secure before version 22.7R1 (Not Applicable to 9.1Rx) allow 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 · moderate confidence

This vulnerability in Ivanti Connect Secure and Policy Secure involves incorrect file permissions that allow a local authenticated attacker to escalate their privileges to a higher level. The issue stems from improperly secured files that can be manipulated by users who already have local access to the system.

MitigationUpgrade Ivanti Connect Secure to version 22.6R2 or later, and Ivanti Policy Secure to version 22.7R1 or later. Note that versions 9.1Rx are not affected.

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>= 21.9, < 22.6= 9.1= 22.6
Policy SecureApplication
Affected:< 9.1>= 22.1, < 22.7= 9.1= 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. Identify the installed Ivanti product
    Run 'show system' or check the admin console to determine if the device is running Ivanti Connect Secure or Ivanti Policy Secure
    Affected if The product is Connect Secure or Policy Secure and the version falls within the affected ranges
  2. Determine the installed version of Ivanti Connect Secure
    Run 'show version' or access the admin console System > Status page to obtain the exact version number (e.g., 22.5, 21.9, 9.1)
    Affected if The version is < 9.1, = 9.1, >= 21.9 and < 22.6, or = 22.6 (note: 9.1Rx versions are not affected)
  3. Determine the installed version of Ivanti Policy Secure
    Run 'show version' or access the admin console System > Status page to obtain the exact version number
    Affected if The version is < 9.1, = 9.1, >= 22.1 and < 22.7, or = 22.7 (note: 9.1Rx versions are not affected)
  4. Verify if the system has local authenticated user accounts
    Check the local user database through the admin console under User Authentication > Local Users or review /etc/passwd (or equivalent) for non-administrative local accounts
    Affected if Local authenticated users exist on the system, which is required to exploit this privilege escalation vulnerability

You are affected if you are running Ivanti Connect Secure (versions < 9.1, 9.1, >= 21.9 to 22.5, or 22.6) or Ivanti Policy Secure (versions < 9.1, 9.1, >= 22.1 to 22.6, or 22.7) and have local authenticated users on the system.

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

Upgrade Ivanti Connect Secure to version 22.6R2 or later, and Ivanti Policy Secure to version 22.7R1 or later. Note that versions 9.1Rx are not affected.

Recommended fix High confidence

Ivanti Connect Secure: upgrade to 22.6R2 or later | Ivanti Policy Secure: upgrade to 22.7R1 or later

  1. 1. Identify the currently installed Ivanti Connect Secure or Policy Secure version by checking the system administration console or running 'show version' command
  2. 2. For Ivanti Connect Secure: Upgrade to version 22.6R2 or later to resolve the file permissions vulnerability
  3. 3. For Ivanti Policy Secure: Upgrade to version 22.7R1 or later to resolve the file permissions vulnerability
  4. 4. Note: Version 9.1Rx is NOT affected by this vulnerability per the advisory
  5. 5. Before upgrading, backup the current system configuration
  6. 6. Perform the upgrade following Ivanti's standard upgrade procedures documented in the product admin guide
  7. 7. After upgrade, verify the new version is installed correctly
  8. 8. Confirm file permissions have been corrected by reviewing system files post-upgrade

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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
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,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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