dbcve.org
Connect SecureApplication · Ivanti

CVE-2024-47906

HIGH · 7.8 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 9.1 / 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
Excessive binary privileges in Ivanti Connect Secure before version 22.7R2.3 (Not Applicable to 9.1Rx) and Ivanti Policy Secure before version 22.7R1.2 (Not Applicable to 9.1Rx) allows a local authenticated attacker to escalate 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 Connect Secure and Policy Secure contain binaries with excessive privileges, allowing a local authenticated attacker to escalate their privileges to higher levels. This is a local privilege escalation vulnerability affecting specific versions prior to 22.7R2.3 (Connect Secure) and 22.7R1.2 (Policy Secure).

MitigationUpgrade Ivanti Connect Secure to version 22.7R2.3 or later, and Ivanti Policy Secure to version 22.7R1.2 or later. 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> 9.1, < 22.7= 22.7
Policy SecureApplication
Affected:< 9.1> 9.1, < 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. Identify the installed Ivanti product
    Run 'show system information' 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 in the affected ranges
  2. Determine the installed version number
    Run 'show version' or check the admin console under System > Status to obtain the exact firmware version (e.g., 22.7, 22.7R1, 22.7R2.2, 9.1R1, etc.)
    Affected if The version number is revealed and can be compared to the affected ranges
  3. Compare against affected version ranges for Connect Secure
    If the product is Connect Secure, verify the version is < 9.1, OR > 9.1 AND < 22.7, OR exactly 22.7. Note that 9.1Rx versions are NOT affected.
    Affected if The version is < 9.1, or > 9.1 and < 22.7, or exactly 22.7 for Connect Secure
  4. Compare against affected version ranges for Policy Secure
    If the product is Policy Secure, verify the version is < 9.1, OR > 9.1 AND < 22.7, OR exactly 22.7. Note that 9.1Rx versions are NOT affected.
    Affected if The version is < 9.1, or > 9.1 and < 22.7, or exactly 22.7 for Policy Secure

You are affected if you are running Connect Secure versions before 22.7R2.3 (excluding 9.1Rx) or Policy Secure versions before 22.7R1.2 (excluding 9.1Rx), specifically any version < 9.1, between 9.1 and 22.7, or exactly 22.7.

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

Upgrade Ivanti Connect Secure to version 22.7R2.3 or later, and Ivanti Policy Secure to version 22.7R1.2 or later. Versions 9.1Rx are not affected.

Recommended fix High confidence

Connect Secure: 22.7R2.3 or later; Policy Secure: 22.7R1.2 or later

  1. 1. Identify which Ivanti product is deployed: Connect Secure or Policy Secure
  2. 2. Check the current installed version of the product
  3. 3. For Ivanti Connect Secure: Upgrade to version 22.7R2.3 or later
  4. 4. For Ivanti Policy Secure: Upgrade to version 22.7R1.2 or later
  5. 5. After upgrade, verify the new version is correctly installed
  6. 6. Test that normal authentication and authorization functions operate correctly
  7. 7. Note: Version 9.1Rx is NOT affected by this vulnerability, so no action needed for 9.1Rx deployments
Caveat Review Ivanti release notes for upgrade prerequisites and any configuration changes required for the target version

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
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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