CriticalCVE-2024-7593

    Ivanti Virtual Traffic Manager Authentication Bypass Vulnerability (CVE-2024-7593)

    Published In CISA KEV since Sources: CVE.org, pwn.watch

    What is affected, what to do

    An authentication bypass vulnerability in Ivanti Virtual Traffic Manager allows a remote, unauthenticated attacker to create an administrator account. This affects all versions except 22.2R1 and 22.7R2. The vulnerability is actively exploited in the wild and is listed in the CISA KEV catalog. Affected organizations should urgently patch to the specified versions to mitigate the risk.

    The vulnerability is being actively exploited; treat it as a priority. Update Ivanti vTM to version 22.2R1. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Ivanti vTM lt *..22.2R1
    Fixed in
    • Ivanti vTM 22.2R1

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    9.8

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: CVE.org, pwn.watch

    —

    EPSS score

    No value is available for this vulnerability.

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    235.02 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    9.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.8
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.99
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-287, CWE-303

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This flaw is exploitable over the network with no authentication and no user interaction, and it hands the attacker full administrative control of a component that sits directly in the traffic path. A working public PoC appeared shortly after disclosure, which puts it among the CVEs most likely to be exploited. Typical victims run vTM as a load balancer or ADC in front of business-critical web applications and have left the admin UI reachable. A compromised vTM enables TLS key theft, traffic redirection and a foothold for lateral movement. CISA does not flag known ransomware use, but treat any instance with an admin UI reachable from untrusted networks as top priority: fix immediately and run a compromise assessment. Where management is strictly isolated, patching remains urgent but can follow your standard emergency patch window.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Inventory: Identify every Ivanti Virtual Traffic Manager (vTM) instance, including hardware, virtual appliances, cloud images and software installs, and confirm the running version. Every version other than 22.2R1 and 22.7R2 is affected, notably the 22.2, 22.3, 22.5, 22.6 and 22.7 trains.
      • Patch: Upgrade to 22.2R1 or 22.7R2. For the 22.3, 22.5 and 22.6 trains, a patch is available from the vendor; look up the exact fixed version in the vendor advisory. If you cannot patch immediately, move to a fixed train or apply the compensating controls below.
      • Lock down the admin interface now: Block access to the admin UI (default TCP 9090; verify against your config) from the internet and from any untrusted network. Bind it to an internal management IP only and restrict it with an access list to named admin hosts. This is Ivanti's own recommended mitigation.
      • Hunt for compromise: Review the vTM audit logs and System > Users for unknown or recently created administrator accounts. Disable rogue accounts immediately, preserve evidence (config backup, logs) and open an incident.
      • Rotate secrets: If compromise is suspected, rotate all local admin passwords, API tokens and cluster secrets, and the TLS private keys stored on the vTM. An attacker with admin rights can export certificates and tamper with TrafficScript rules.
      • Verify configuration integrity: Diff virtual servers, pools, TrafficScript/Java extensions and event handlers against a known-good backup. Look for redirects, credential-harvesting rules and unexpected actions.

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: Place the management interface only in a dedicated admin VLAN or out-of-band network. Firewall rule: permit inbound TCP 9090 only from jump hosts or the PAW subnet; drop and log everything else.
      • Upstream access control: Allow admin access only via MFA-protected VPN or a ZTNA proxy. Prevent direct reachability from data-plane (client traffic) networks.
      • IPS/WAF rule: In front of the admin port, block or alert on requests to /apps/zxtm/wizard.fcgi carrying parameters such as section=Access+Management%3ALocalUsers from non-admin sources. This is the pattern used by the public PoC. Suricata idea: http.uri; content:"/apps/zxtm/wizard.fcgi"; content:"LocalUsers"; nocase;.
      • IAM/least privilege: Minimise local admin accounts and move to central authentication (LDAP/RADIUS/TACACS+) with role-based permissions where possible. Document a baseline of legitimate accounts so deviations stand out quickly.
      • Exposure monitoring: Run external attack-surface scans (Shodan, Censys or your own ASM) for reachable vTM admin UIs, and re-verify after applying the controls.

    3. Runbook step 3

      Detection rules

      • Web/proxy logs: Requests to wizard.fcgi containing error=1 and LocalUsers from unauthorised source IPs. Sigma shape: cs-uri-stem|contains: '/apps/zxtm/wizard.fcgi' AND cs-uri-query|contains: 'LocalUsers', filtered against the admin IP allowlist.
      • vTM audit log (forwarded via syslog): User creation or modification events in the "admin" group outside approved change windows. SPL idea: index=netdev sourcetype=vtm:audit ("user" AND ("add" OR "create")) | stats count by src_ip, user.
      • Network telemetry (Zeek/Suricata/NetFlow): Connections to TCP 9090 on vTM hosts from internet or client networks, especially first-seen sources followed by a successful session. KQL idea: CommonSecurityLog | where DestinationPort == 9090 and not(ipv4_is_in_any_range(SourceIP, AdminRanges)).
      • Login anomalies: Successful admin logins with newly created account names, scripted user agents (python-requests, curl) or at unusual hours.
      • Configuration drift: Unexpected TrafficScript changes, certificate exports or new event actions. Generate config diffs regularly from backups and alert on them.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    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.

    Source: NVD (NIST), cvelistv5, CISA KEV Catalog, CVE.org (MITRE), pwn.watch

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    VendorProductAffected versionsFixed in
    IvantivTM
    • < 22.2R1
    • 22.2R1
    ivantivirtual_traffic_manager
    • 22.2
    • 22.7
    • 22.6
    • 22.5
    • 22.3
    • —
    • —
    • —
    • —
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-287Improper Authentication

      Class

      When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

      Entry at MITRE CWE-287

    • CWE-303Incorrect Implementation of Authentication Algorithm

      Base

      The requirements for the product dictate the use of an established authentication algorithm, but the implementation of the algorithm is incorrect.

      Entry at MITRE CWE-303

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    SourceReferenceMaturityPublished
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    • forums.ivanti.comIvanti advisory: CVE-2024-7593Mitigation, Patch, Vendor advisory, pwn-watch
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2024-7593government-resource, US government resource
    • pwn.watchpwn.watch: Ivanti Virtual Traffic Manager Authentication Bypasspwn-watch
    • NVD (NIST)NVD: CVE-2024-7593pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2024-7593
    <a href="https://intel.neosec.eu/en/cve/CVE-2024-7593"><img src="https://intel.neosec.eu/badge/cve/CVE-2024-7593.svg?lang=en" alt="CVE-2024-7593 – NEOSEC Intel" height="20"></a>