dbcve.org
Connect SecureApplication · Ivanti

CVE-2024-11004

MEDIUM · 6.1 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 22.7 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Reflected XSS in Ivanti Connect Secure before version 22.7R2.1 and Ivanti Policy Secure before version 22.7R1.1 allows a remote unauthenticated attacker to obtain admin privileges. User interaction is required.

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

A reflected XSS vulnerability exists in the web interface of Ivanti Connect Secure (before 22.7R2.1) and Ivanti Policy Secure (before 22.7R1.1). An unauthenticated attacker can craft malicious URLs that, when clicked by an authenticated administrator, execute arbitrary JavaScript in the admin session context, enabling privilege escalation to full admin access.

MitigationUpgrade Ivanti Connect Secure to version 22.7R2.1 or later, and Ivanti Policy Secure to version 22.7R1.1 or later. Additionally, educate admin users to avoid clicking untrusted links.

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:< 22.7= 22.7
Policy SecureApplication
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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 Ivanti product
    Log into the admin web interface and locate the product name, typically shown on the login page or in the header/sidebar. Alternatively, access the CLI and run a version or system info command.
    Affected if The product is either Ivanti Connect Secure or Ivanti Policy Secure.
  2. Locate the version number in the admin interface
    In the web admin console, navigate to System Configuration, System Management, or Device Details (path varies by version). Look for a field labeled Version, Firmware Version, or Build Number.
    Affected if Any version is displayed.
  3. Compare your version against the affected ranges
    Note the exact version number displayed (e.g., 22.7, 22.6, 9.x). For Connect Secure, you are affected if the version is 22.7 or lower. For Policy Secure, you are affected if the version is 22.7 or lower.
    Affected if The installed version is 22.7 or any version below 22.7 for either product.
  4. Confirm the build or patch level (if visible)
    Check if the version includes additional build identifiers such as R2.1 or R1.1. These appear after the base version number in the admin interface.
    Affected if The version shows 22.7R2.0 or earlier for Connect Secure, or 22.7R1.0 or earlier for Policy Secure.

You are affected if your Ivanti Connect Secure is version 22.7R2.0 or earlier, or your Ivanti Policy Secure is version 22.7R1.0 or earlier.

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 Connect Secure to version 22.7R2.1 or later, and Ivanti Policy Secure to version 22.7R1.1 or later. Additionally, educate admin users to avoid clicking untrusted links.

Recommended fix High confidence

Connect Secure 22.7R2.1; Policy Secure 22.7R1.1

  1. 1. Identify the current version of Ivanti Connect Secure or Policy Secure by accessing the admin console and checking System > Status or using the CLI command 'show version'.
  2. 2. For Connect Secure: Plan upgrade to version 22.7R2.1 or later.
  3. 3. For Policy Secure: Plan upgrade to version 22.7R1.1 or later.
  4. 4. Review Ivanti's upgrade documentation and release notes for your specific product to understand prerequisites and upgrade procedure.
  5. 5. Before upgrading, perform a complete configuration backup of the current device.
  6. 6. Download the appropriate signed upgrade package from the Ivanti Support Portal or authorized distribution channel.
  7. 7. Follow Ivanti's standard upgrade procedure: upload the upgrade package via the admin console (System > Maintenance > Upgrade > Upload), then initiate the upgrade.
  8. 8. After upgrade completes, verify the new version is installed and the admin console is accessible.
Caveat Review release notes for any configuration or feature changes between your current version and the fixed release; minor version upgrades typically have minimal breaking changes but always verify before proceeding.

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-11004 — 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-11004 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