CVE-2024-7593
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.
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. Authentication bypass is a flaw in the application's logic. The attack requests look like normal traffic, so a WAF has nothing to match on.
Also consider: patch · add auth middleware
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-7593 being exploited?
Yes. CVE-2024-7593 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-7593?
CVE-2024-7593 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-7593?
Yes. A fix has been recorded for CVE-2024-7593. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-7593 affect?
CVE-2024-7593 affects ivanti:virtual_traffic_manager. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
public exploits
Unvetted proof-of-concept code on GitHub: 1 Metasploit module · 3 GitHub proofs of concept · 1 Nuclei template
- auxiliary/admin/http/ivanti_vtm_admin · auxiliary · normal
- Ivanti vTM - Authentication Bypass · detection template · critical
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 24 Sept 2024 (SSVC 2.0.3).
timeline
- 13 Aug 2024Published
- 28 Aug 2024First proof-of-concept repository on GitHub (unvetted) · 14 days later
- 24 Sept 2024Added to CISA KEV (exploited in the wild) · 27 days later
- 24 Sept 2024CISA SSVC assessment: exploitation active · 1 day later
- 15 Oct 2024CISA remediation due date (US federal agencies) · 20 days later
- 21 Oct 2025CVE record last updated · 372 days (about 1 year) later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
- Linkforums.ivanti.com /s/article/Security-Advisory-Ivanti-Virtual-Traffic-Manager-vTM-CVE-2024-7593
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-7593
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Metasploit Framework: exploit and scanner modules
- Nuclei templates: detection templates
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.