dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Oct 2024.
Virtual Traffic ManagerApplication · Ivanti

CVE-2024-7593

CRITICAL · 9.8 CVSS v3.1 Published 2024-08-13
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click Patch available

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 implementation of an authentication algorithm in Ivanti vTM other than versions 22.2R1 or 22.7R2 allows a remote unauthenticated attacker to bypass authentication of the admin panel.

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 vTM contains an authentication bypass vulnerability in versions prior to 22.2R1 or 22.7R2. The flaw stems from an incorrectly implemented authentication algorithm that allows remote unauthenticated attackers to bypass login controls and access the admin panel without valid credentials.

MitigationUpgrade Ivanti vTM to version 22.2R1 or 22.7R2. Until patched, restrict network access to the admin interface from untrusted sources using firewall rules or VPN access controls.

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
Virtual Traffic ManagerApplication
Affected:= 22.2= 22.3= 22.5= 22.6= 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 vTM is installed
    Check for the Ivanti vTM service or process running on the system. On Linux, look for processes named 'vtm' or check /opt/vtm/ directory. On Windows, check Services for 'Ivanti Virtual Traffic Manager'.
    Affected if The product is present on the system
  2. Identify installed version
    Check the version of Ivanti vTM. On Linux, run /opt/vtm/bin/vtm --version or inspect /opt/vtm/VERSION file. On Windows, check the installed version via the Windows Programs feature or the service properties.
    Affected if The installed version matches 22.2, 22.3, 22.5, 22.6, or 22.7 exactly
  3. Verify admin panel is network accessible
    Check if port 9080 (HTTP) or 9443 (HTTPS) admin interface is listening and exposed. Use netstat -an | grep -E '9080|9443' or nmap -p 9080,9443 <your-ip> to determine if admin ports are listening.
    Affected if The admin panel ports (9080 or 9443) are open and reachable from the network
  4. Test admin panel authentication bypass
    Attempt to access the admin panel endpoints without credentials. Send an HTTP request to https://<host>:9443/ or http://<host>:9080/ and observe if administrative access is granted without providing valid credentials.
    Affected if Administrative functions are accessible without authentication credentials being supplied

A user is affected if Ivanti vTM version 22.2, 22.3, 22.5, 22.6, or 22.7 is installed and its admin panel is network-accessible, allowing unauthenticated administrative access.

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
Patch available Apply the vendor patch
Vendor patch forums.ivanti.com →
Interim mitigation

Upgrade Ivanti vTM to version 22.2R1 or 22.7R2. Until patched, restrict network access to the admin interface from untrusted sources using firewall rules or VPN access controls.

Recommended fix High confidence

22.7R2 (or 22.2R1 if staying on the 22.2 branch)

  1. 1. Back up the current Ivanti Virtual Traffic Manager configuration
  2. 2. Download Ivanti Virtual Traffic Manager version 22.7R2 from the official Ivanti support portal
  3. 3. Upgrade the Virtual Traffic Manager instance to version 22.7R2
  4. 4. Verify the upgrade was successful and the admin panel is accessible
  5. 5. Confirm authentication is working correctly by logging into the admin panel
  6. 6. Validate that the existing configuration has been preserved after upgrade
Caveat Review release notes for any breaking changes between your current version and 22.7R2

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

Fix this in Virtual Traffic Manager Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get it fixed fast

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